From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: egcs@cygnus.com
Subject: egcs-971201 sparc-sun-solaris2.5 results
Date: Tue, 02 Dec 1997 11:25:00 -0000 [thread overview]
Message-ID: <199712021910.OAA18633@caip.rutgers.edu> (raw)
I bootstrapped egcs-971201 on sparc-sun-solaris2.5 using cc
for stage1, BOOT_CFLAGS="-g -O3 -funroll-all-loops" and I got a clean
"make compare".
Below are the c-torture errors and the results from "make check".
--Kaveh
ERROR: loop-2f.c: compiled program got signal 6: -O2 -fno-omit-frame-pointer
ERROR: loop-2f.c: compiled program got signal 6: -O2 -fomit-frame-pointer
ERROR: loop-2f.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer
ERROR: loop-2f.c: compiled program got signal 6: -O3 -fomit-frame-pointer
ERROR: loop-2f.c: compiled program got signal 6: -O3 -funroll-all-loops
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: -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
(Duplicates from -fpic/-fPIC omitted.)
ERROR: complex-3.c: compiled program got signal 10: -O3 -fno-omit-frame-pointer -fpic
ERROR: complex-3.c: compiled program got signal 10: -O3 -fomit-frame-pointer -fpic
ERROR: complex-3.c: compiled program got signal 10: -O3 -funroll-all-loops -fpic
ERROR: 930628-1.c: compiled program got signal 11: -O -fno-omit-frame-pointer -fpic
ERROR: 930628-1.c: compiled program got signal 11: -O -fomit-frame-pointer -fpic
ERROR: 930628-1.c: compiled program got signal 11: -O -fno-omit-frame-pointer -fPIC
ERROR: 930628-1.c: compiled program got signal 11: -O -fomit-frame-pointer -fPIC
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
=== gcc tests ===
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 4881
# of unexpected failures 4
# of expected failures 5
# of unsupported tests 6
=== 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
=== g++ Summary ===
# of expected passes 3400
# of unexpected successes 3
# of expected failures 80
# of untested testcases 6
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu ICon CMT Corp.
reply other threads:[~1997-12-02 11:25 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=199712021910.OAA18633@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).