From: Andrey Slepuhin <pooh@msu.ru>
To: egcs@cygnus.com
Subject: egcs-971127: results on powerpc-ibm-aix4.2.1.0
Date: Sat, 29 Nov 1997 05:48:00 -0000 [thread overview]
Message-ID: <34801C0C.A67C5FAB@msu.ru> (raw)
Here are the results of egcs-971127 on powerpc-ibm-aix4.2.1.0.
egcs native configuration with --enable-shared.
Used patches: patch for multithreaded exception handling
by Teemu Torma and my patch for shared libraries support.
Why there is a regression in gcc testsuite
(gcc.c-torture/execute/va-arg-5.c)?
----------------------------------------------------------
Test Run By pooh on Sat Nov 29 14:15:04 1997
Native configuration is powerpc-ibm-aix4.2.1.0
=== gcc tests ===
FAIL: gcc.c-torture/compile/920501-4.c, -O2
FAIL: gcc.c-torture/compile/920501-4.c, -O2 -fomit-frame-pointer
-finline-functions
FAIL: gcc.c-torture/compile/920501-4.c, -O2 -fomit-frame-pointer
-finline-functions -funroll-loops
FAIL: gcc.c-torture/compile/920501-4.c, -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/931004-11.c execution, -O0
FAIL: gcc.c-torture/execute/931004-11.c execution, -O1
FAIL: gcc.c-torture/execute/931004-11.c execution, -O2
FAIL: gcc.c-torture/execute/931004-12.c execution, -O0
FAIL: gcc.c-torture/execute/931004-12.c execution, -O1
FAIL: gcc.c-torture/execute/931004-12.c execution, -O2
FAIL: gcc.c-torture/execute/931004-12.c execution, -O2 -fomit-frame-pointer
-finline-functions
FAIL: gcc.c-torture/execute/931004-12.c execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/931004-12.c execution, -O2 -fomit-frame-pointer
-finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/complex-5.c execution, -O2 -fomit-frame-pointer
-finline-functions
FAIL: gcc.c-torture/execute/va-arg-5.c execution, -O0
FAIL: gcc.c-torture/execute/va-arg-5.c execution, -O1
FAIL: gcc.c-torture/execute/va-arg-5.c execution, -O2
FAIL: gcc.c-torture/execute/va-arg-5.c execution, -O2 -fomit-frame-pointer
-finline-functions
=== gcc Summary ===
# of expected passes 4865
# of unexpected failures 18
# of expected failures 5
# of unsupported tests 7
=== g++ tests ===
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.jason/thunk3.C (test for excess errors)
FAIL: g++.law/profile1.C (test for excess errors)
XPASS: g++.mike/dyncast1.C Execution test
XPASS: g++.mike/dyncast2.C Execution test
FAIL: g++.pt/typename5.C (test for excess errors)
=== g++ Summary ===
# of expected passes 3395
# of unexpected failures 3
# of unexpected successes 3
# of expected failures 82
# of untested testcases 6
=== g77 tests ===
=== g77 Summary ===
# of expected passes 132
=== libio tests ===
=== libio Summary ===
# of expected passes 40
=== libstdc++ tests ===
=== libstdc++ Summary ===
# of expected passes 30
next reply other threads:[~1997-11-29 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-29 5:48 Andrey Slepuhin [this message]
1997-11-29 17:19 ` Jeffrey A Law
1997-11-29 17:19 ` Andrey Slepuhin
1997-11-30 14:29 ` Franz Sirl
1997-11-30 20:14 ` Jeffrey A Law
1997-12-02 4:16 ` haifa-enabled " Andrey Slepuhin
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=34801C0C.A67C5FAB@msu.ru \
--to=pooh@msu.ru \
--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).