Subj : Re: Memory Barriers, Compiler Optimizations, etc.
To   : comp.programming.threads
From : Alexander Terekhov
Date : Thu Feb 03 2005 12:41 am


SenderX wrote:
[...]
> op(X).release
> mf
> op(Y).acquire
> 
> should prevent op(Y) affects on shared memory from becoming visible before
> op(x)?

Yes. BTW, revised Java volatiles and JSR-166 atomics are required to 
do that. ("Java memory model traded performance for simplicity in a 
few cases".)

regards,
alexander.

.