This is the mail archive of the egcs-testresults@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
Sources: - egcs mainline from CVS last updated at Tue Mar 16 22:12:16 1999 - libg++-2.8.1.2a-19981217 Patches: None. Environment: - GNU binutils 2.9.1.0.22b - autoconf-990306 - automake-990306 - dejagnu-19981026 - gperf-2.7 with gperf-2.7-19981006 patch for -F - Linux kernel 2.2.3 (compiled by egcs-2.91.60) - glibc 2.1.0 (compiled by egcs-2.91.60) Remarks: None. configure flags: --with-gnu-ld --with-gnu-as --prefix=/usr/packages.bin/egcs/snapshot --enable-shared --disable-haifa BOOT_CC: egcs-2.91.60 BOOT_CFLAGS: -W -Wall -funroll-all-loops -g -march=pentium -mcpu=pentium -fomit-frame-pointer -Os CFLAGS: -W -Wall -march=pentium -mcpu=pentium -fomit-frame-pointer -g -Os CXXFLAGS: -W -Wall -march=pentium -mcpu=pentium -fomit-frame-pointer -g -Os Changes in testsuite results for g++ since the last successful build (on Tue Mar 16 12:09:29 1999): New tests that PASS: g++.other/lookup9.C (test for excess errors) Changes in testsuite results for g77 since the last successful build (on Tue Mar 16 12:09:29 1999): Changes in testsuite results for gcc since the last successful build (on Tue Mar 16 12:09:29 1999): New tests that FAIL: gcc.dg/setjmp-1.c spurious clobbered warning (test for bogus messages, line 16) gcc.dg/uninit-5.c uninitialized variable warning (test for bogus messages, line 13) gcc.dg/uninit-5.c uninitialized variable warning (test for bogus messages, line 27) gcc.dg/uninit-6.c uninitialized variable warning (test for bogus messages, line 37) gcc.dg/uninit-8.c uninitialized variable warning (test for bogus messages, line 14) gcc.dg/uninit-9.c uninitialized variable warning (test for bogus messages, line 26) New tests that PASS: gcc.dg/setjmp-1.c (test for excess errors) gcc.dg/uninit-5.c (test for excess errors) gcc.dg/uninit-6.c (test for excess errors) gcc.dg/uninit-8.c (test for excess errors) gcc.dg/uninit-9.c (test for excess errors) Changes in testsuite results for libg++ since the last successful build (on Tue Mar 16 12:09:29 1999): Changes in testsuite results for libio since the last successful build (on Tue Mar 16 12:09:28 1999): Changes in testsuite results for libstdc++ since the last successful build (on Tue Mar 16 12:09:29 1999): Changes in testsuite results for objc since the last successful build (on Tue Mar 16 12:09:29 1999): Changes in stage 3 warnings since the last successful build (on Tue Mar 16 12:09:47 1999): 2c2 < there are 371 warnings in stage3 of this bootstrap. --- > there are 383 warnings in stage3 of this bootstrap. 8a9 > 12 ../../egcs/gcc/cse.c 10d10 < 11 ./parse.y 11a12,13 > 10 ./parse.y > 10 ../../egcs/gcc/fold-const.c 13d14 < 10 ../../../egcs/gcc/java/jcf-dump.c 15d15 < 9 ../../egcs/gcc/cse.c 16a17 > 9 ../../../egcs/gcc/java/jcf-dump.c 24d24 < 7 ../../egcs/gcc/c-lex.c 26c26 < 6 ../../egcs/gcc/fold-const.c --- > 6 ../../egcs/gcc/c-lex.c 28a29 > 6 ../../../egcs/gcc/cp/lex.c 58a60 > 1 ../../egcs/gcc/tree.c 82a85 > 1 ../../../egcs/gcc/cp/call.c 87c90 < 88 `???' might be used uninitialized in this function --- > 89 `???' might be used uninitialized in this function 90a94 > 29 variable `???' might be clobbered by `longjmp' or `vfork' 94d97 < 20 variable `???' might be clobbered by `longjmp' or `vfork' 96c99 < 13 unused variable `???' --- > 11 unused variable `???' 97a101 > 5 argument `???' might be clobbered by `longjmp' or `vfork' 101d104 < 2 suggest explicit braces to avoid ambiguous `else' 102a106 > 1 suggest explicit braces to avoid ambiguous `else' Changes in stage 3 no-subdir warnings since the last successful build (on Tue Mar 16 12:09:51 1999): 2c2 < there are 271 warnings in stage3 of this bootstrap. --- > there are 278 warnings in stage3 of this bootstrap. 7a8 > 12 ../../egcs/gcc/cse.c 8a10 > 10 ../../egcs/gcc/fold-const.c 11d12 < 9 ../../egcs/gcc/cse.c 18d18 < 7 ../../egcs/gcc/c-lex.c 20c20 < 6 ../../egcs/gcc/fold-const.c --- > 6 ../../egcs/gcc/c-lex.c 47a48 > 1 ../../egcs/gcc/tree.c 71,72c72 < 8 variable `???' might be clobbered by `longjmp' or `vfork' < 8 unused variable `???' --- > 11 variable `???' might be clobbered by `longjmp' or `vfork' 73a74,75 > 7 unused variable `???' > 5 argument `???' might be clobbered by `longjmp' or `vfork' Changes in stage 0 warnings since the last successful build (on Tue Mar 16 12:09:49 1999):