From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Subject: Results for haifa-enabled egcs-2.90.28 980423 (egcs-1.0.3 prerelease) testsuite on mips-sgi-irix6.3
Date: Wed, 29 Apr 1998 08:38:00 -0000 [thread overview]
Message-ID: <199804291226.JAA01642@araguaia.dcc.unicamp.br> (raw)
Native configuration is mips-sgi-irix6.3
=== 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
FAIL: g++.eh/spec4.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/eh23.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
=== g++ Summary ===
# of expected passes 3349
# of unexpected failures 47
# of unexpected successes 1
# of expected failures 86
# of untested testcases 6
/tmp/egcsh-cvs/gcc/testsuite/../xgcc version egcs-2.90.28 980423 (egcs-1.0.3 prerelease)
=== g77 tests ===
=== g77 Summary ===
# of expected passes 132
/tmp/egcsh-cvs/gcc/g77 version egcs-2.90.28 980423 (egcs-1.0.3 prerelease)
=== gcc tests ===
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
=== gcc Summary ===
# of expected passes 4879
# of unexpected failures 4
# of expected failures 5
# of unsupported tests 7
/tmp/egcsh-cvs/gcc/xgcc version egcs-2.90.28 980423 (egcs-1.0.3 prerelease)
=== libio tests ===
=== libio Summary ===
# of expected passes 40
=== libstdc++ tests ===
=== libstdc++ Summary ===
# of expected passes 30
configure flags: --enable-shared --enable-haifa --disable-multilib
BOOT_CFLAGS: -O4 -g
reply other threads:[~1998-04-29 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199804291226.JAA01642@araguaia.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).