Not sure where to begin. However I was surprised to see many thousands of testsuite failures with 2.8.2 on the following system : vanth $ uname -a Linux vanth 3.2.0-4-powerpc64 #1 SMP Debian 3.2.51-1 ppc64 GNU/Linux vanth $ cat /proc/cpuinfo processor : 0 cpu : PPC970MP, altivec supported clock : 2500.000000MHz revision : 1.1 (pvr 0044 0101) processor : 1 cpu : PPC970MP, altivec supported clock : 2500.000000MHz revision : 1.1 (pvr 0044 0101) processor : 2 cpu : PPC970MP, altivec supported clock : 2500.000000MHz revision : 1.1 (pvr 0044 0101) processor : 3 cpu : PPC970MP, altivec supported clock : 2500.000000MHz revision : 1.1 (pvr 0044 0101) timebase : 33333333 platform : PowerMac model : PowerMac11,2 machine : PowerMac11,2 motherboard : PowerMac11,2 MacRISC4 Power Macintosh detected as : 337 (PowerMac G5 Dual Core) pmac flags : 00000000 L2 cache : 1024K unified pmac-generation : NewWorld vanth $ The build environment is similar to what I used on Red Hat Entrprise Linux on x86_64 as well as on Debian Linux wheezy on x86_64 where I was able to get good results. Configure looked like so : vanth $ ../gcc-4.8.2/configure --prefix=/usr/local/gcc4 --with-gnu-as \ > --with-gnu-ld --with-ld=/usr/bin/ld --with-libiconv-prefix=/usr/local \ > --enable-nls --enable-lto --enable-threads=posix --enable-shared \ > --libdir=/usr/local/gcc4/lib --libexecdir=/usr/local/gcc4/lib \ > --enable-languages=c,c++,objc,fortran,java,lto,go,ada \ > --enable-__cxa_atexit --with-as=/usr/bin/as --enable-bootstrap checking build system type... powerpc64-unknown-linux-gnu checking host system type... powerpc64-unknown-linux-gnu checking target system type... powerpc64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for a sed that does not truncate output... /usr/local/bin/sed checking for gawk... /usr/local/bin/gawk checking for libatomic support... yes checking for libitm support... yes checking for libsanitizer support... yes checking for gcc... /usr/local/gcc4/bin/gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/local/gcc4/bin/gcc accepts -g... yes checking for /usr/local/gcc4/bin/gcc option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether /usr/local/gcc4/bin/g++ accepts -g... yes checking whether g++ accepts -static-libstdc++ -static-libgcc... yes checking for gnatbind... gnatbind checking for gnatmake... gnatmake checking whether compiler driver understands Ada... yes checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 checking for objdir... .libs checking for version 0.10 of ISL... no checking for version 0.11 of ISL... no checking for version 0.12 of ISL... no 'c++' language required by 'go' in stage 1; enabling The following languages will be built: c,ada,c++,fortran,go,java,lto,objc checking for default BUILD_CONFIG... bootstrap-debug checking for bison... bison -y checking for bison... bison checking for gm4... /usr/local/bin/gm4 checking for flex... no checking for lex... no checking for flex... no checking for makeinfo... makeinfo checking for expect... expect checking for runtest... runtest checking for ar... ar checking for as... as checking for dlltool... no checking for ld... (cached) /usr/bin/ld checking for lipo... no checking for nm... nm checking for ranlib... ranlib checking for strip... strip checking for windres... no checking for windmc... no checking for objcopy... objcopy checking for objdump... objdump checking for readelf... readelf checking for cc... cc checking for c++... c++ checking for gcc... gcc checking for gcj... gcj checking for gfortran... gfortran checking for gccgo... gccgo checking for ar... no checking for ar... ar checking for as... no checking for as... as checking for dlltool... no checking for dlltool... no checking for ld... no checking for ld... ld checking for lipo... no checking for lipo... no checking for nm... no checking for nm... nm checking for objdump... no checking for objdump... objdump checking for ranlib... no checking for ranlib... ranlib checking for readelf... no checking for readelf... readelf checking for strip... no checking for strip... strip checking for windres... no checking for windres... no checking for windmc... no checking for windmc... no checking where to find the target ar... host tool checking where to find the target as... host tool checking where to find the target cc... just compiled checking where to find the target c++... just compiled checking where to find the target c++ for libstdc++... just compiled checking where to find the target dlltool... host tool checking where to find the target gcc... just compiled checking where to find the target gcj... just compiled checking where to find the target gfortran... just compiled checking where to find the target gccgo... just compiled checking where to find the target ld... host tool checking where to find the target lipo... host tool checking where to find the target nm... host tool checking where to find the target objdump... host tool checking where to find the target ranlib... host tool checking where to find the target readelf... host tool checking where to find the target strip... host tool checking where to find the target windres... host tool checking where to find the target windmc... host tool checking whether to enable maintainer-specific portions of Makefiles... no configure: creating ./config.status config.status: creating Makefile I am seeing many many thousands of testsuite failures like so : === g++ tests === Running target unix FAIL: c-c++-common/asan/clone-test-1.c -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: c-c++-common/asan/clone-test-1.c -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: c-c++-common/asan/clone-test-1.c -O2 -flto (test for excess errors) UNRESOLVED: c-c++-common/asan/clone-test-1.c -O2 -flto compilation failed to produce executable FAIL: c-c++-common/asan/global-overflow-1.c -O0 output pattern test, is ========================================================== ======= FAIL: c-c++-common/asan/global-overflow-1.c -O1 output pattern test, is ========================================================== ======= FAIL: c-c++-common/asan/global-overflow-1.c -O2 output pattern test, is ========================================================== ======= FAIL: c-c++-common/asan/global-overflow-1.c -O3 -fomit-frame-pointer output pattern test, is ===================================== ============================ FAIL: c-c++-common/asan/global-overflow-1.c -O3 -g output pattern test, is ======================================================= ========== FAIL: c-c++-common/asan/global-overflow-1.c -Os output pattern test, is ========================================================== ======= FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: c-c++-common/asan/global-overflow-1.c -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: c-c++-common/asan/global-overflow-1.c -O2 -flto (test for excess errors) UNRESOLVED: c-c++-common/asan/global-overflow-1.c -O2 -flto compilation failed to produce executable FAIL: c-c++-common/asan/heap-overflow-1.c -O0 output pattern test, is ============================================================ ===== FAIL: c-c++-common/asan/heap-overflow-1.c -O1 output pattern test, is ============================================================ ===== FAIL: c-c++-common/asan/heap-overflow-1.c -O2 output pattern test, is ============================================================ ===== FAIL: c-c++-common/asan/heap-overflow-1.c -O3 -fomit-frame-pointer output pattern test, is ======================================= ========================== FAIL: c-c++-common/asan/heap-overflow-1.c -O3 -g output pattern test, is ========================================================= ======== FAIL: c-c++-common/asan/heap-overflow-1.c -Os output pattern test, is ============================================================ ===== FAIL: c-c++-common/asan/heap-overflow-1.c -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: c-c++-common/asan/heap-overflow-1.c -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: c-c++-common/asan/heap-overflow-1.c -O2 -flto (test for excess errors) UNRESOLVED: c-c++-common/asan/heap-overflow-1.c -O2 -flto compilation failed to produce executable etc etc FAIL: g++.dg/torture/stackalign/throw-3.C -O2 -flto -flto-partition=none -fpic (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-3.C -O2 -flto -flto-partition=none -fpic compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-3.C -O2 -flto (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-3.C -O2 -flto compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-3.C -O2 -flto -fpic (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-3.C -O2 -flto -fpic compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-4.C -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-4.C -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-4.C -O2 -flto -flto-partition=none -fpic (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-4.C -O2 -flto -flto-partition=none -fpic compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-4.C -O2 -flto (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-4.C -O2 -flto compilation failed to produce executable FAIL: g++.dg/torture/stackalign/throw-4.C -O2 -flto -fpic (test for excess errors) UNRESOLVED: g++.dg/torture/stackalign/throw-4.C -O2 -flto -fpic compilation failed to produce executable === g++ Summary === # of expected passes 51754 # of unexpected failures 599 # of expected failures 290 # of unresolved testcases 521 # of unsupported tests 1032 /usr/local/build/gcc-4.8.2_3.2.0-4-powerpc64_unknown_003/gcc/testsuite/g++/../../xg++ version 4.8.2 (Blastwave.org Inc. Tue Oct 29 21:50:30 UTC 2013) also with thousands of lines like : === gcc tests === Running target unix FAIL: gcc.c-torture/execute/builtins/20010124-1.c compilation, -O2 -flto -flto-partition=none UNRESOLVED: gcc.c-torture/execute/builtins/20010124-1.c execution, -O2 -flto -flto-partition=none FAIL: gcc.c-torture/execute/builtins/20010124-1.c compilation, -O2 -flto UNRESOLVED: gcc.c-torture/execute/builtins/20010124-1.c execution, -O2 -flto FAIL: gcc.c-torture/execute/builtins/abs-1.c compilation, -O2 -flto -flto-partition=none UNRESOLVED: gcc.c-torture/execute/builtins/abs-1.c execution, -O2 -flto -flto-partition=none FAIL: gcc.c-torture/execute/builtins/abs-1.c compilation, -O2 -flto UNRESOLVED: gcc.c-torture/execute/builtins/abs-1.c execution, -O2 -flto FAIL: gcc.c-torture/execute/builtins/abs-2.c compilation, -O2 -flto -flto-partition=none UNRESOLVED: gcc.c-torture/execute/builtins/abs-2.c execution, -O2 -flto -flto-partition=none FAIL: gcc.c-torture/execute/builtins/abs-2.c compilation, -O2 -flto UNRESOLVED: gcc.c-torture/execute/builtins/abs-2.c execution, -O2 -flto FAIL: gcc.c-torture/execute/builtins/abs-3.c compilation, -O2 -flto -flto-partition=none UNRESOLVED: gcc.c-torture/execute/builtins/abs-3.c execution, -O2 -flto -flto-partition=none FAIL: gcc.c-torture/execute/builtins/abs-3.c compilation, -O2 -flto UNRESOLVED: gcc.c-torture/execute/builtins/abs-3.c execution, -O2 -flto FAIL: gcc.c-torture/execute/builtins/complex-1.c compilation, -O2 -flto -flto-partition=none UNRESOLVED: gcc.c-torture/execute/builtins/complex-1.c execution, -O2 -flto -flto-partition=none FAIL: gcc.c-torture/execute/builtins/complex-1.c compilation, -O2 -flto UNRESOLVED: gcc.c-torture/execute/builtins/complex-1.c execution, -O2 -flto . . . FAIL: gcc.dg/vmx/yousufi-1.c -O2 -flto (test for excess errors) UNRESOLVED: gcc.dg/vmx/yousufi-1.c -O2 -flto compilation failed to produce executable FAIL: gcc.dg/vmx/zero-1.c -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: gcc.dg/vmx/zero-1.c -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: gcc.dg/vmx/zero-1.c -O2 -flto (test for excess errors) UNRESOLVED: gcc.dg/vmx/zero-1.c -O2 -flto compilation failed to produce executable FAIL: gcc.dg/vmx/zero.c -O2 -flto -flto-partition=none (test for excess errors) UNRESOLVED: gcc.dg/vmx/zero.c -O2 -flto -flto-partition=none compilation failed to produce executable FAIL: gcc.dg/vmx/zero.c -O2 -flto (test for excess errors) UNRESOLVED: gcc.dg/vmx/zero.c -O2 -flto compilation failed to produce executable FAIL: gcc.target/powerpc/ppc-fpconv-9.c scan-assembler-not stw FAIL: gcc.target/powerpc/ppc-round.c scan-assembler-not stw FAIL: gcc.target/powerpc/ppc-vector-memcpy.c scan-assembler lvx FAIL: gcc.target/powerpc/pr48857.c scan-assembler-not stw === gcc Summary === # of expected passes 80570 # of unexpected failures 4369 # of expected failures 240 # of unresolved testcases 4207 # of unsupported tests 1442 /usr/local/build/gcc-4.8.2_3.2.0-4-powerpc64_unknown_003/gcc/xgcc version 4.8.2 (Blastwave.org Inc. Tue Oct 29 21:50:30 UTC 2013) Truely the worst results I have seen in years. This would indicate that there is a serious issue somewhere but not sure if there is something obvious at work here? Any hints? Dennis ps: I used the Debian supplied gcc to bootstrap with : vanth $ which gcc /usr/bin/gcc vanth $ gcc --version gcc (Debian 4.6.3-14) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
