Subj : Re: Memory Barriers, Compiler Optimizations, etc.
To   : comp.programming.threads
From : SenderX
Date : Wed Feb 02 2005 03:07 pm

> That's because (think of op(X) as "store" and op(Y) as "load" to/from
> different locations)
>
>    op(X).release
>    op(Y).acquire
>
> doesn't prevent
>
>    op(Y).acquire
>    op(X).release
>
> reordering.


op(X).release
mf
op(Y).acquire


should prevent op(Y) affects on shared memory from becoming visible before 
op(x)?


>
> In the case lock operations (now think IA64), reordering must not
> induce deadlocks (lock operation must not "suspend" preceding
> releases) but critical regions can "overlap" for better performance.

I see.

.