Date: Sun, 24 Nov 2024 11:46:29 -0800
On Sunday 24 November 2024 09:52:23 Pacific Standard Time Nate Eldredge via
Std-Discussion wrote:
> However, for memory-mapped I/O, you almost never want to define an actual
> object of `volatile`-qualified type. You would work through pointers to
> such types, but the pointers themselves would not be `volatile`.
As an implementation extension, one can define the address of a global variable
to be some region of memory-mapped memory. How this is achieved is between you
and your vendor, but it makes sense to allow global volatiles in the standard.
Std-Discussion wrote:
> However, for memory-mapped I/O, you almost never want to define an actual
> object of `volatile`-qualified type. You would work through pointers to
> such types, but the pointers themselves would not be `volatile`.
As an implementation extension, one can define the address of a global variable
to be some region of memory-mapped memory. How this is achieved is between you
and your vendor, but it makes sense to allow global volatiles in the standard.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Platform & System Engineering
Received on 2024-11-24 19:46:39