From: "Harvey J. Stein" <hjstein@bfr.co.il>
To: egcs@cygnus.com
Subject: egcs-1.0 alphaev56-unknown-linux-gnulibc1 test results
Date: Tue, 09 Dec 1997 09:52:00 -0000 [thread overview]
Message-ID: <199712091711.TAA10227@blinky.bfr.co.il> (raw)
Successfully built on linux alpha (Redhat 4.2),
alphaev56-unknown-linux-gnulibc1, *after* removing the f subdirectory so
as to avoid trying to build the fortran compiler (because it fails).
I have miscellaneous gcc & kernel patches installed.
GOOD WORK!
Configuration:
../egcs-1.0/configure --prefix=/usr/local/egcs --enable-haifa
I'm not including the tests run on the existing C compiler because it
doesn't seem like the instructions for doing such are on the website
any longer. If someone tells me how to do it, I'll run it.
Test results:
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
=== gcc tests ===
FAIL: gcc.c-torture/execute/960218-1.c execution, -O0
FAIL: gcc.c-torture/execute/960218-1.c execution, -O1
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
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
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O0
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O1
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2
FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution, -O2 -fomit-frame-pointer -finline-functions
=== gcc Summary ===
# of expected passes 4856
# of unexpected failures 14
# of expected failures 5
# of unsupported tests 9
=== g++ tests ===
FAIL: g++.benjamin/p12475.C (test for warnings, line 4)
XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for errors, line 6)
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 3390
# of unexpected failures 1
# of unexpected successes 4
# of expected failures 82
# of untested testcases 10
=== g77 Summary ===
# of unexpected failures 72
# of untested testcases 60
WARNING: alphaev56-unknown-linux-gnulibc1-g77 does not exist
make[1]: [check-g77] Error 1 (ignored)
make[1]: Leaving directory `/home/hjstein/software/egcs-1.0-build/gcc'
next reply other threads:[~1997-12-09 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-09 9:52 Harvey J. Stein [this message]
1997-12-09 10:59 ` Richard Henderson
1997-12-10 2:27 ` Harvey J. Stein
1997-12-10 2:49 ` Harvey J. Stein
1997-12-09 14:34 ` Toon Moene
1997-12-09 16:25 ` namelist patch [was egcs-1.0 alphaev56-unknown-linux-gnulibc1 test results] Richard Henderson
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=199712091711.TAA10227@blinky.bfr.co.il \
--to=hjstein@bfr.co.il \
--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).