From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: egcs@cygnus.com
Subject: egcs-1.0.3 prerelease mips-sgi-irix6.2 results
Date: Tue, 28 Apr 1998 07:23:00 -0000 [thread overview]
Message-ID: <199804281423.KAA10387@caip.rutgers.edu> (raw)
Snapshot: egcs-2.90.28 980423 (egcs-1.0.3 prerelease)
Platform: mips-sgi-irix6.2
Stage1 compiler: cc
Assembler: native
Linker: native
BOOT_CFLAGS: -g -O3 -funroll-all-loops
The results from c-torture and "make check" are below.
-----------
=== libio tests ===
=== libio Summary ===
# of expected passes 40
=== libstdc++ tests ===
=== libstdc++ Summary ===
# of expected passes 30
=== 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
=== g++ tests ===
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
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
=== g++ Summary ===
# of expected passes 3394
# of unexpected failures 2
# of unexpected successes 3
# of expected failures 84
# of untested testcases 6
=== g77 tests ===
=== g77 Summary ===
# of expected passes 132
-----------
Testing with the following flag(s): <>
TEST DIR: execute
ERROR: complex-5.c: compiled program got signal 6:
ERROR: complex-5.c: compiled program got signal 6: -O -fno-omit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O -fomit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O2 -fno-omit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O2 -fomit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O2 -funroll-all-loops
ERROR: complex-5.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O3 -fomit-frame-pointer
ERROR: complex-5.c: compiled program got signal 6: -O3 -funroll-all-loops
Test completed with 9 failures
TEST DIR: execute/ieee
Test completed successfully
TEST DIR: compile
ERROR: 961203-1.c: compiler got signal 11:
ERROR: 961203-1.c: compiler got signal 11: -O -fno-omit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O -fomit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O2 -fno-omit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O2 -fomit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O2 -funroll-all-loops
ERROR: 961203-1.c: compiler got signal 11: -O3 -fno-omit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O3 -fomit-frame-pointer
ERROR: 961203-1.c: compiler got signal 11: -O3 -funroll-all-loops
Test completed with 9 failures
TEST DIR: noncompile
Test completed successfully
TEST DIR: unsorted
Test completed successfully
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu Icon CMT Corp.
reply other threads:[~1998-04-28 7:23 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=199804281423.KAA10387@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--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).