http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46914
--- Comment #11 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-01-28 09:43:44 UTC --- Ok, with --with-arch-32=i486 in the configure options and -m32 on the command line the problem can be reproduced. Frankly, I don't understand what is going on: in that case, by default, everything should remain consistent and the _GLIBCXX_ATOMIC_BUILTINS_* used when building atomic.cc should be still the correct ones for user code too (if some different -march were used on the command line, then I could see possible troubles, again, because the atomic headers don't use macros sensitive to the actual command line options).
