ARM bare-metal programming in D (cont) - volatile

[eles]

On Monday, 28 October 2013 at 16:06:48 UTC, Walter Bright wrote:
> On 10/28/2013 2:33 AM, eles wrote:
> That overlooks what happens if another thread changes the 
> memory in between the read and the write. Hence the issues of 
> memory barriers, lock prefixes, etc.

Synchronizing the access to the resource is the job of the 
programmer. He will take a mutex for it.

You do that inside the kernel space, not in the user space. There 
is just one kernel, and it is able to synchronize with itself.

Put this into perspective.

> Pull requests are welcome!

You pre-approve?