From: oliva@saci (Alexandre Oliva)
To: egcs@cygnus.com
Subject: Results for haifa-disabled egcs-980102 testsuite on sparc-sun-sunos4.1.3
Date: Wed, 07 Jan 1998 21:14:00 -0000 [thread overview]
Message-ID: <199801080511.DAA28787@saci.dcc.unicamp.br> (raw)
Native configuration is sparc-sun-sunos4.1.3
=== g++ tests ===
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.law/profile1.C Execution test
XPASS: g++.mike/dyncast1.C Execution test
XPASS: g++.mike/dyncast2.C Execution test
FAIL: g++.mike/p9706.C Execution test
=== g++ Summary ===
# of expected passes 3398
# of unexpected failures 2
# of unexpected successes 3
# of expected failures 80
# of untested testcases 6
/home/msc/oliva/bin/gcc version egcs-2.90.23 980102 (egcs-1.0.1 release)
=== gcc tests ===
FAIL: gcc.c-torture/execute/920501-8.c compilation, -O0
FAIL: gcc.c-torture/execute/920501-8.c compilation, -O1
FAIL: gcc.c-torture/execute/920501-8.c compilation, -O2
FAIL: gcc.c-torture/execute/920501-8.c compilation, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O0
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O1
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
=== gcc Summary ===
# of expected passes 4871
# of unexpected failures 10
# of expected failures 5
# of untested testcases 4
# of unsupported tests 6
/home/msc/oliva/bin/gcc version egcs-2.90.23 980102 (egcs-1.0.1 release)
configure flags: --with-gnu-as --enable-shared --disable-haifa
BOOT_CFLAGS: -O4 -g
reply other threads:[~1998-01-07 21:14 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=199801080511.DAA28787@saci.dcc.unicamp.br \
--to=oliva@saci \
--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).