From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Subject: Results for haifa-disabled egcs-2.91.28 19980508 (gcc2 ss-980502 experimental) testsuite on sparc-sun-solaris2.6
Date: Mon, 11 May 1998 06:35:00 -0000 [thread overview]
Message-ID: <199805111333.KAA19105@araguaia.dcc.unicamp.br> (raw)
Native configuration is sparc-sun-solaris2.6
=== g++ tests ===
XPASS: g++.mike/ns11.C (test for excess errors)
XPASS: g++.mike/ns11.C Execution test
XPASS: g++.mike/ns13.C (test for excess errors)
XPASS: g++.mike/ns14.C (test for excess errors)
XPASS: g++.mike/ns9.C (test for excess errors)
XPASS: g++.mike/ns9.C Execution test
=== g++ Summary ===
# of expected passes 3819
# of unexpected successes 6
# of expected failures 67
# of untested testcases 6
/tmp/egcs/gcc/testsuite/../xgcc version egcs-2.91.28 19980508 (gcc2 ss-980502 experimental)
=== g77 tests ===
FAIL: g77.f-torture/compile/970125-0.f, -O1
FAIL: g77.f-torture/compile/970125-0.f, -O2
FAIL: g77.f-torture/compile/970125-0.f, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/compile/970125-0.f, -Os
FAIL: g77.f-torture/compile/980419-1.f, -O0
FAIL: g77.f-torture/compile/980419-1.f, -O1
FAIL: g77.f-torture/compile/980419-1.f, -O2
FAIL: g77.f-torture/compile/980419-1.f, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/compile/980419-1.f, -Os
=== g77 Summary ===
# of expected passes 222
# of unexpected failures 9
/tmp/egcs/gcc/g77 version egcs-2.91.28 19980508 (gcc2 ss-980502 experimental)
=== gcc tests ===
FAIL: gcc.c-torture/execute/980505-1.c execution, -O2
FAIL: gcc.c-torture/execute/980505-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/980505-1.c execution, -O2 -g
FAIL: gcc.c-torture/execute/980505-1.c execution, -Os
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
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -g
FAIL: gcc.c-torture/execute/loop-2f.c execution, -Os
FAIL: gcc.dg/980502-1.c (test for excess errors)
=== gcc Summary ===
# of expected passes 7206
# of unexpected failures 11
# of expected failures 7
# of unsupported tests 12
/tmp/egcs/gcc/xgcc version egcs-2.91.28 19980508 (gcc2 ss-980502 experimental)
=== 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 --disable-haifa
BOOT_CFLAGS: -O4 -g
reply other threads:[~1998-05-11 6:35 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=199805111333.KAA19105@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).