https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53579
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ramana at gcc dot gnu.org --- Comment #2 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- This is not just the atomicity tests that are affected. Now that we've switched to C++ in the main compiler, folks (especially in the business of building cross-compilers) just set CXXFLAGS in the environment and assume that this implies that the compiler built is built with the appropriate CXXFLAGS. So, it's very easy to build a libstdc++ with the value of CXXFLAGS set to something that wasn't expected. The build system appears to honour the difference between CFLAGS and CFLAGS_FOR_TARGET, so it is natural that folks expect that CXXFLAGS to behave in the same fashion.