A few broken spots in the testsuite ... # gcc/xgcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: /root/downloads/gcc-4_3-trunk/configure --verbose --enable-languages=c,ada,c++,fortran,java,objc,obj-c++ --with-tune=athlon-xp --prefix=/usr --enable-objc-gc --enable-concept-checks --disable-multilib --with-gxx-include-dir=/usr/include/c++/4.3 --enable-libstdcxx-debug --enable-static --enable-shared --enable-initfini-array --enable-__cxa_atexit --enable-threads=posix --enable-version-specific-runtime-libs --enable-libssp --enable-libmudflap --enable-libgomp --disable-werror --enable-nls --with-included-gettext --enable-decimal-float --with-long-double-128 --enable-debug --enable-java-gc=boehm --with-x --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib --enable-java-awt=gtk,xlib --enable-gtk-cairo --enable-qt-peer --enable-xmlj --enable-gconf-peer --enable-tool-wrappers --enable-portable-native-sync --enable-libgcj-multifile --with-stabs --enable-hash-synchronization --enable-gc-debug --enable-interpreter --with-system-zlib --enable-libada --with-tls --with-cpu=athlon-xp --with-arch=athlon-xp --enable-stage1-checking=assert,gc,misc,rtl,rtlflag,runtime Thread model: posix gcc version 4.3.0 20070523 (experimental) --- # grep -B 5 -A 5 gcc.dg-struct-layout-1_generate gcc/testsuite/gcc/gcc.log FAIL: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute testcase /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/compat.exp completed in 57 seconds Running /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp ... Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ dfprt5233.c -fno-show-column -lm -o dfprt5233.x (timeout = 300) Setting LD_LIBRARY_PATH to :/opt/gcc-4_3-build/gcc::/opt/gcc-4_3-build/gcc:/opt/gcc-4_3-build/i686-pc-linux-gnu/libstdc++-v3/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libmudflap/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libssp/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libgomp/.libs:/opt/gcc-4_3-build/./gcc:/opt/gcc-4_3-build/./prev-gcc Executing on host: gcc -g -O2 -o /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1_generate.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random_r.c (timeout = 300) WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator testcase /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp completed in 0 seconds Running /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/cpp/cpp.exp ... Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/cpp/19921210-1.c -ansi -pedantic-errors -fno-show-column -S -o 19921210-1.s (timeout = 300) PASS: gcc.dg/cpp/19921210-1.c (test for excess errors) The message "WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator " is "odd". The gcc.log _claims_ it is using the OS gcc to compile: # ls -l /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate ls: /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate: No such file or directory # gcc -g -O2 -o /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1_generate.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random_r.c # ls -l /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate -rwxr-xr-x 1 root root 69791 May 23 12:48 /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate When I cut-and-paste the gcc command from the log the generator compiles OK. The testsuite works on 4.2.0 i686-pc-cygwin and 4.2.1 i686-pc-linux-gnu. Point 1): Having the testsuite fail with this warning denies the testsuite from running a whole battery of tests that the generator creates. One warning _might_ cover-up many _possible_ errors if the test were ran (or hide many sucesses). Point 2): (Retorical Questions) Why do we use "gcc" ? - The OS's "gcc". Which version are we using, do we care? Can it actually compile the tests? We _ought_ to use gcc/xgcc ! - then we know which version of gcc we are using. If xgcc can not compile the generator then _IT_ is at fault. If the OS's gcc can not compile the generator then does that _actually_ matter - no. If the program is so trivial that any compiler can compile it then why not have xgcc do it. That makes the "warning" into an error _IF_ it fails, if it succeeds then it is a "pass" and not a warning. The rest of the tests can then get a chance to run instead of being denied simply because the OS's gcc did not compile the file. Another problem occurs immediatly after: WARNING: Could not compile gcc.dg/compat/struct-layout-1 generator FAIL: gcc.dg/debug/dwarf2/dwarf-dfp.c (internal compiler error) FAIL: gcc.dg/debug/dwarf2/dwarf-dfp.c (test for excess errors) ERROR: gcc.dg/debug/dwarf2/dwarf-dfp.c: error executing dg-final: couldn't open "dwarf-dfp.s": no such file or directory UNRESOLVED: gcc.dg/debug/dwarf2/dwarf-dfp.c: error executing dg-final: couldn't open "dwarf-dfp.s": no such file or directory FAIL: gcc.dg/dfp/Wtraditional-conversion-2.c (internal compiler error) FAIL: gcc.dg/dfp/Wtraditional-conversion-2.c (test for excess errors) The testsuite _CLAIMS_ it could not open the file but actually it is an ICE. Here is a bit of the log: # grep -A 8 testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c gcc/testsuite/gcc/gcc.log Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c -O0 -gdwarf-2 -dA -fno-show-column -S -o dwarf-dfp.s (timeout = 300) /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c: In function 'foo': /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: error: unrecognizable insn: (insn 7 6 8 3 /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:15 (set (subreg:TI (reg:TD 58) 0) (subreg:TI (const_double:TD 0 [0x0] 1.5 [N/A]) 0)) -1 (nil) (nil)) /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: internal compiler error: in extract_insn, at recog.c:2119 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. compiler exited with status 1 output is: /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c: In function 'foo': /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: error: unrecognizable insn: (insn 7 6 8 3 /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:15 (set (subreg:TI (reg:TD 58) 0) (subreg:TI (const_double:TD 0 [0x0] 1.5 [N/A]) 0)) -1 (nil) (nil)) /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: internal compiler error: in extract_insn, at recog.c:2119 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. FAIL: gcc.dg/debug/dwarf2/dwarf-dfp.c (internal compiler error) FAIL: gcc.dg/debug/dwarf2/dwarf-dfp.c (test for excess errors) Excess errors: /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: error: unrecognizable insn: (insn 7 6 8 3 /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:15 (set (subreg:TI (reg:TD 58) 0) (subreg:TI (const_double:TD 0 [0x0] 1.5 [N/A]) 0)) -1 (nil) (nil)) /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-dfp.c:16: internal compiler error: in extract_insn, at recog.c:2119 ERROR: gcc.dg/debug/dwarf2/dwarf-dfp.c: error executing dg-final: couldn't open "dwarf-dfp.s": no such file or directory UNRESOLVED: gcc.dg/debug/dwarf2/dwarf-dfp.c: error executing dg-final: couldn't open "dwarf-dfp.s": no such file or directory Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-die1.c -O2 -gdwarf-2 -dA -fno-show-column -S -o dwarf-die1.s (timeout = 300) PASS: gcc.dg/debug/dwarf2/dwarf-die1.c (test for excess errors) PASS: gcc.dg/debug/dwarf2/dwarf-die1.c scan-assembler-not DW_AT_inline Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf-die2.c -O0 -gdwarf-2 -dA -fno-show-column -S -o dwarf-die2.s (timeout = 300) PASS: gcc.dg/debug/dwarf2/dwarf-die2.c (test for excess errors) This little section of the testsuite needs a once over.
> Point 2): (Retorical Questions) Why do we use "gcc" ? - The OS's "gcc". Which > version are we using, do we care? Can it actually compile the tests? Because this has to be the build compiler, otherwise it is hard to test using the just created xgcc (if build!=host!=target) Also this works for me.
>> "has to be the build compiler". >OK. A new error has popped up in this same section of the log between the compiling and execution of gcc.dg-struct-layout-1 . Running /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1.exp ... Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ dfprt27268.c -fno-show-column -lm -o dfprt27268.x (timeout = 300) Setting LD_LIBRARY_PATH to :/opt/gcc-4_3-build/gcc::/opt/gcc-4_3-build/gcc:/opt/gcc-4_3-build/i686-pc-linux-gnu/libstdc++-v3/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libmudflap/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libssp/.libs:/opt/gcc-4_3-build/i686-pc-linux-gnu/libgomp/.libs:/opt/gcc-4_3-build/./gcc:/opt/gcc-4_3-build/./prev-gcc Executing on host: gcc -g -O2 -ffloat-store -mfpmath=sse -march=athlon-xp -msse2 -o /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/struct-layout-1_generate.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random.c /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat/generate-random_r.c (timeout = 300) Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ short_enums27268.c -fno-show-column -S -o short_enums27268.s (timeout = 300) short_enums27268.c:3: error: size of array 's' is negative compiler exited with status 1 output is: short_enums27268.c:3: error: size of array 's' is negative Executing on host: /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1_generate -s /root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat -d /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1 (timeout = 300) Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ -I/root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat -fno-show-column -c -o c_compat_main_tst.o /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1/t001_main.c (timeout = 300) PASS: tmpdir-gcc.dg-struct-layout-1/t001 c_compat_main_tst.o compile Executing on host: /opt/gcc-4_3-build/gcc/xgcc -B/opt/gcc-4_3-build/gcc/ -w -I/root/downloads/gcc-4_3-trunk/gcc/testsuite/gcc.dg/compat -fno-show-column -c -o c_compat_x_tst.o /opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.dg-struct-layout-1//t001_x.c (timeout = 300) PASS: tmpdir-gcc.dg-struct-layout-1/t001 c_compat_x_tst.o compile