volatile asm

[Sean Kelly]

Jason House wrote:
> I was just looking at Atomic.d in the D2 port of tango and I see that all the volatile keywords are commented out.  My understanding is that the ordering of the assembly in those blocks is incredibly important to preserve as-is.  What is the way to ensure that in D2?

Walter has said that compilers should not optimize across asm blocks, 
and so a correct D compiler will not do so, and therefore the volatile 
label should be unnecessary.  But I hope that this will be revisited 
once multiprogramming in D is a bit more fleshed out.


Sean