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 alpha-unknown-linux-gnu
Date: Wed, 29 Apr 1998 07:57:00 -0000 [thread overview]
Message-ID: <199804291226.JAA01586@araguaia.dcc.unicamp.br> (raw)
Native configuration is alpha-unknown-linux-gnu
=== g++ tests ===
FAIL: g++.benjamin/p12475.C (test for warnings, line 4)
XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for errors, line 6)
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
XPASS: g++.law/profile1.C (test for excess errors)
XPASS: g++.law/profile1.C Execution test
XPASS: g++.mike/dyncast1.C Execution test
XPASS: g++.mike/dyncast2.C Execution test
FAIL: g++.mike/eh39.C Execution test
FAIL: g++.mike/eh40.C Execution test
FAIL: g++.mike/p6610a.C Execution test
=== g++ Summary ===
# of expected passes 3391
# of unexpected failures 4
# of unexpected successes 6
# of expected failures 82
# of untested testcases 6
/tmp/egcsh-cvs/gcc/testsuite/../xgcc version egcs-2.90.28 980423 (egcs-1.0.3 prerelease)
=== g77 tests ===
FAIL: g77.f-torture/execute/dnrm2.f execution, -O1
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
=== g77 Summary ===
# of expected passes 127
# of unexpected failures 5
/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
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O0
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O1
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2 -fomit-frame-pointer -finline-functions
=== gcc Summary ===
# of expected passes 4875
# of unexpected failures 8
# 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: --with-gnu-as --with-gnu-ld --enable-shared --enable-haifa
BOOT_CFLAGS: -O4 -g
reply other threads:[~1998-04-29 7:57 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.JAA01586@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).