This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-1.0.2: results on i486-pc-linux-gnu
- To: ManfredMetzger at swol dot de (Manfred Metzger)
- Subject: Re: egcs-1.0.2: results on i486-pc-linux-gnu
- From: hjl at lucon dot org (H.J. Lu)
- Date: Thu, 19 Mar 1998 06:04:18 -0800 (PST)
- Cc: egcs at cygnus dot com
>
> - Cyrix 6x86 P166+
> - Kernel 2.0.33
> - glibc-2.0.6
> - binutils-2.8.1.0.23
> - make-3.76.1
> - BOOT_CFLAGS=-O2 -mpentium -fomit-frame-pointer -funroll-loops
> - configured with --enable-shared --enable-threads
> - the results are the same with or without --enable-haifa
>
> === libio tests ===
> === libio Summary ===
>
> # of expected passes 40
>
> === libstdc++ tests ===
> === libstdc++ Summary ===
>
> # of expected passes 30
>
> === gcc tests ===
> === gcc Summary ===
>
> # of expected passes 4883
> # of expected failures 5
> # of unsupported tests 7
>
> === g++ tests ===
>
> FAIL: g++.eh/pdel1.C Execution test
> FAIL: g++.eh/pdel2.C Execution test
> FAIL: g++.eh/rethrow1.C Execution test
> FAIL: g++.eh/rethrow2.C Execution test
> FAIL: g++.eh/rethrow3.C Execution test
> FAIL: g++.eh/spec1.C Execution test
> FAIL: g++.eh/spec2.C Execution test
> XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
> FAIL: g++.mike/eh10.C Execution test
> FAIL: g++.mike/eh12.C Execution test
> FAIL: g++.mike/eh14.C Execution test
> FAIL: g++.mike/eh16.C Execution test
> FAIL: g++.mike/eh17.C Execution test
> FAIL: g++.mike/eh18.C Execution test
> FAIL: g++.mike/eh2.C Execution test
> FAIL: g++.mike/eh21.C Execution test
> FAIL: g++.mike/eh24.C Execution test
> FAIL: g++.mike/eh25.C Execution test
> FAIL: g++.mike/eh26.C Execution test
> FAIL: g++.mike/eh27.C Execution test
> FAIL: g++.mike/eh28.C Execution test
> FAIL: g++.mike/eh29.C Execution test
> FAIL: g++.mike/eh3.C Execution test
> FAIL: g++.mike/eh31.C Execution test
> FAIL: g++.mike/eh33.C Execution test
> FAIL: g++.mike/eh34.C Execution test
> FAIL: g++.mike/eh35.C Execution test
> FAIL: g++.mike/eh36.C Execution test
> FAIL: g++.mike/eh37.C Execution test
> FAIL: g++.mike/eh38.C Execution test
> FAIL: g++.mike/eh39.C Execution test
> FAIL: g++.mike/eh40.C Execution test
> FAIL: g++.mike/eh41.C Execution test
> FAIL: g++.mike/eh42.C Execution test
> FAIL: g++.mike/eh44.C Execution test
> FAIL: g++.mike/eh47.C Execution test
> FAIL: g++.mike/eh48.C Execution test
> FAIL: g++.mike/eh49.C Execution test
> FAIL: g++.mike/eh5.C Execution test
> FAIL: g++.mike/eh50.C Execution test
> FAIL: g++.mike/eh51.C Execution test
> FAIL: g++.mike/eh6.C Execution test
> FAIL: g++.mike/eh8.C Execution test
> FAIL: g++.mike/p6610a.C Execution test
> FAIL: g++.mike/p7912.C Execution test
> FAIL: g++.mike/p9706.C Execution test
>
Can you take a look at g++.log? I don't have so many failures.
H.J.