Call for compiler help/advice: atomic builtins for v3

[Paolo Carlini]

Richard Guenther wrote:

>You are screwed, because if you pass a std::vector (assuming it needs
>locking) to kdelibs to mungle with and in a separate thread mungle with
>it in the -march=i686 application you're using two different types of locking
>which surely won't play well with each other.  A smart libgcc cannot fix
>any inlined locking primitives.
>
locking is not inlined.

Paolo.