DMD 1.029 and 2.013 releases

[Jarrett Billingsley]

"Walter Bright" <newshound1 at digitalmars.com> wrote in message 
news:fuqed8$18bm$2 at digitalmars.com...
> Steven Schveighoffer wrote:
>> You can sort of work around it by wrapping the previously volatile 
>> statement in a function, but it seems like having volatile doesn't really 
>> hurt anything.  I'm curious to know why it was so bad that it was worth 
>> removing...
>
> Because after listening in while experts debated how to do write 
> multithreaded code safely, it became pretty clear that the chances of 
> using volatile statements correctly is very small, even for experts. It's 
> the wrong approach.

But what about things like accessing memory-mapped registers?  That is, as a 
hint to the compiler to say "don't inline this; don't cache results in 
registers"?