From: Christian Joensson FOA 72 <chj@lin.foa.se>
To: egcs@cygnus.com
Subject: egcs-1.0.2: results on Solaris 2.5
Date: Tue, 17 Mar 1998 01:28:00 -0000 [thread overview]
Message-ID: <199803170808.JAA13458@arnljot.lin.foa.se> (raw)
gcc --version
2.7.2
as -V
as: SC4.0 dev 15 Feb 1995
ld -V
ld: Software Generation Utilities (SGU) SunOS/ELF (LK-2.0 (S/I) - versioning)
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
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
/home/guneri/objdir/gcc/xgcc version egcs-2.90.27 980315 (egcs-1.0.2 release)
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
/home/guneri/objdir/gcc/testsuite/../xgcc version egcs-2.90.27 980315 (egcs-1.0.2 release)
=== g77 Summary ===
# of expected passes 132
/home/guneri/objdir/gcc/g77 version egcs-2.90.27 980315 (egcs-1.0.2 release)
Well, all seems quite well, right? Even if I don't use the gnu binutilities, should I
do that?)
The config.status indicate the following:
../egcs-1.0.2/configure --host=sparc-sun-solaris2.5 --prefix=/home72/guneri/egcs-1.0.2 --verbose --norecursion
/ChJ
reply other threads:[~1998-03-17 1:28 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=199803170808.JAA13458@arnljot.lin.foa.se \
--to=chj@lin.foa.se \
--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).