http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50976
--- Comment #4 from Ed Smith-Rowland <3dw4rd at verizon dot net> 2011-11-03 12:47:41 UTC --- I wonder if the testsuite was run when the gcc was built. It should have raised a boatload of flags there. Your test case runs like a charm on x86_64-unknown-linux-gnu. ------------------------------------------------------------------------------ ed@bad-horse:~/udlit_debug$ ../bin/bin/g++ -v Using built-in specs. COLLECT_GCC=../bin/bin/g++ COLLECT_LTO_WRAPPER=/home/ed/bin/libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc/configure --prefix=/home/ed/bin --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local --with-ppl=/usr/local --with-cloog=/usr/local --enable-cloog-backend=isl --enable-lto --enable-languages=c,c++,fortran,go,lto,objc,obj-c++ Thread model: posix gcc version 4.7.0 20111031 (experimental) (GCC) ed@bad-horse:~/udlit_debug$ ../bin/bin/g++ -std=c++0x -c main.cpp ed@bad-horse:~/udlit_debug$ ------------------------------------------------------------------------------ I can't imagine how this could be target dependent though. I wonder if build logs could be found.
