From: scott snyder <snyder@d0sgif.fnal.gov>
To: egcs@cygnus.COM
Subject: regression test results for 970904 on alpha-dec-osf4.0
Date: Thu, 04 Sep 1997 21:47:00 -0000 [thread overview]
Message-ID: <199709050447.EAA14961@d0sgif.fnal.gov> (raw)
hi -
Here are results from running the test suite on the 970904
snapshot on a alpha-dec-osf4.0 target.
Here's the gcc summary:
=== gcc Summary ===
# of expected passes 4863
# of unexpected failures 16
# of expected failures 4
# of unsupported tests 7
Executing on host: /d0sgif/data1/snyder/egcs-build/ALPHA/gcc/xgcc -v
Here are the failures:
FAIL: gcc.c-torture/compile/961203-1.c, -O0
FAIL: gcc.c-torture/compile/961203-1.c, -O1
FAIL: gcc.c-torture/compile/961203-1.c, -O2
FAIL: gcc.c-torture/compile/961203-1.c, -O2 -fomit-frame-pointer -finline-functions
This is a known problem with this test.
FAIL: gcc.c-torture/execute/cbrt.c execution, -O0
FAIL: gcc.c-torture/execute/cbrt.c execution, -O1
FAIL: gcc.c-torture/execute/cbrt.c execution, -O2
FAIL: gcc.c-torture/execute/cbrt.c execution, -O2 -fomit-frame-pointer -finline-functions
As reported earlier, this is due to assumption in this test case
that 2*sizeof(long) == sizeof(double), which is false for the alpha.
If this is fixed, this test passes.
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
As discussed before, passing __complex__ arguments is broken.
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
This is apparently a problem with the test harness; the program needs
to be compiled with -mieee.
The failures which i saw previously with 920411-1.c and m-un-1.c
are gone now.
And for g++:
=== g++ Summary ===
# of expected passes 3260
# of unexpected failures 3
# of unexpected successes 6
# of expected failures 82
# of untested testcases 6
The changes from the last test are the same as for other platforms.
FAIL: g++.brendan/crash19.C (test for excess errors)
FAIL: g++.ext/pretty.C (test for excess errors)
FAIL: g++.mike/p811.C (test for excess errors)
XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for errors, line 6)
XPASS: g++.brendan/scope4.C (test for excess errors)
XPASS: g++.law/profile1.C (test for excess errors)
XPASS: g++.law/profile1.C Execution test
XPASS: g++.law/temps7.C (test for excess errors)
XPASS: g++.mike/p7325.C *-*-* Execution test
sss
next reply other threads:[~1997-09-04 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-04 21:47 scott snyder [this message]
1997-09-04 22:05 ` Jeffrey A Law
1997-09-04 22:46 ` scott snyder
1997-09-04 22:58 ` Jeffrey A Law
1997-09-04 23:06 ` Richard Henderson
1997-09-04 23:20 ` Jeffrey A Law
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=199709050447.EAA14961@d0sgif.fnal.gov \
--to=snyder@d0sgif.fnal.gov \
--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).