-fno-tree-cselim not working?
Ian Lance Taylor
iant@google.com
Fri Oct 26 20:29:00 GMT 2007
Andi Kleen <andi@firstfloor.org> writes:
> Ian Lance Taylor <iant@google.com> writes:
> >
> > This code isn't going to be a problem, because spin_unlock presumably
> > includes a memory barrier.
>
> At least in the Linux kernel and also in glibc for mutexes locks are just plain
> function calls, which are not necessarily full memory barriers.
True, and problematic in some cases--but a function call which gcc
can't see is a memory barrier for all addressable memory.
Ian
More information about the Gcc
mailing list