Hi,
On Wed, 25 May 2011, Richard Guenther wrote:
> >> asm volatile ("" : : : "memory") in fact will work as a full memory
> >> barrier
> >
> > How? You surely need MFENCE or somesuch, unless all you care about is
> > a compiler barrier. That's what I think needs to be clarified.
>
> Well, yes, I'm talking about the compiler memory barrier.
Something that we conventionally call "optimization barrier" :) memory
barrier has a fixed meaning which we shouldn't use in this case, it's
confusing.
Ciao,
Michael.
