This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
egcs-1.1 OK on alpha-dec-osf3.2???
- To: egcs at cygnus dot com
- Subject: egcs-1.1 OK on alpha-dec-osf3.2???
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Sat, 15 Aug 1998 22:21:20 -0500
I just did the first bootstrap of egcs-1.1 CVS 19980815 on a DEC Alpha
running OSF v3.2 148, and the results look quite bad. The only other
testsuite results in the mailing list is from Scott Snyder on a DU4
machine and the results there are much better. Is this expected?
C test results show 21 failures as opposed to Scott's 16 under DU4. C++
is disastrous! The EH tests fail (and I see lots unaligned accesses in
the system logs). Libio and libstdc++ tests thankfully all pass as
expected.
I know that I should upgrade to 4.0, but that's a different story ...
=== gcc Summary ===
# of expected passes 7477
# of unexpected failures 21
# of expected failures 7
# of unsupported tests 18
/users2/local/src/egcs-1.1/OSF/gcc/xgcc version egcs-2.91.53 19980815 (gcc2 ss-980609 experimental)
=== g++ Summary ===
# of expected passes 4143
# of unexpected failures 70
# of unexpected successes 6
# of expected failures 88
# of untested testcases 7
/users2/local/src/egcs-1.1/OSF/gcc/testsuite/../xgcc version egcs-2.91.53 19980815 (gcc2 ss-980609 experimental)
=== gcc tests ===
FAIL: gcc.c-torture/execute/980506-1.c execution, -O2
FAIL: gcc.c-torture/execute/980506-1.c execution, -O2 -g
FAIL: gcc.c-torture/execute/980506-1.c execution, -Os
FAIL: gcc.c-torture/execute/980506-2.c execution, -O2
FAIL: gcc.c-torture/execute/980506-2.c execution, -O2 -g
FAIL: gcc.c-torture/execute/980506-2.c execution, -Os
FAIL: gcc.c-torture/execute/980526-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/complex-5.c execution, -O0
FAIL: gcc.c-torture/execute/complex-5.c execution, -O1
FAIL: gcc.c-torture/execute/complex-5.c execution, -O2
FAIL: gcc.c-torture/execute/complex-5.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/complex-5.c execution, -O2 -g
FAIL: gcc.c-torture/execute/complex-5.c execution, -Os
FAIL: gcc.c-torture/execute/memcpy-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -O0
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -O1
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -O2
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -O2 -g
FAIL: gcc.c-torture/execute/ieee/mzero2.c execution, -Os
FAIL: gcc.dg/980626-1.c (test for excess errors)
=== g++ tests ===
XPASS: g++.benjamin/p12475.C (test for excess errors)
XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for errors, line 6)
FAIL: g++.brendan/eh1.C Execution test
FAIL: g++.eh/cleanup1.C Execution test
FAIL: g++.eh/flow1.C Execution test
FAIL: g++.eh/new1.C Execution test
FAIL: g++.eh/new2.C Execution test
FAIL: g++.eh/pdel1.C Execution test
FAIL: g++.eh/pdel2.C Execution test
FAIL: g++.eh/ptr1.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/rethrow4.C Execution test
FAIL: g++.eh/rethrow5.C Execution test
FAIL: g++.eh/spec1.C Execution test
FAIL: g++.eh/spec2.C Execution test
FAIL: g++.eh/spec3.C Execution test
FAIL: g++.jason/thunk1.C Execution test
FAIL: g++.jason/thunk2.C (test for excess errors)
FAIL: g++.jason/thunk2.C Execution test
XPASS: g++.jason/thunk3.C (test for excess errors)
XPASS: g++.law/profile1.C (test for excess errors)
XPASS: g++.law/profile1.C Execution test
FAIL: g++.mike/dyncast1.C Execution test
FAIL: g++.mike/dyncast2.C Execution test
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/eh55.C Execution test
FAIL: g++.mike/eh6.C Execution test
FAIL: g++.mike/eh8.C Execution test
FAIL: g++.mike/p7912.C Execution test
FAIL: g++.mike/p9706.C Execution test
FAIL: g++.other/new.C (test for excess errors)
FAIL: g++.other/new2.C (test for excess errors)
FAIL: g++.pt/static3.C (test for excess errors)
XPASS: g++.robertl/eb132.C (test for excess errors)
FAIL: g++.robertl/eb15.C (test for excess errors)
FAIL: g++.robertl/eb2.C (test for excess errors)
FAIL: g++.robertl/eb31.C Execution test
FAIL: g++.robertl/eb50.C Execution test
FAIL: g++.robertl/eb66.C Execution test
FAIL: g++.robertl/eb71.C (test for excess errors)
FAIL: g++.robertl/eb88.C Execution test
FAIL: g++.robertl/eb91.C (test for excess errors)