From: Mumit Khan <khan@xraylith.wisc.edu>
To: egcs@cygnus.com
Subject: (971023) i386-linux-gnulibc1 gcc/g++ test results
Date: Thu, 23 Oct 1997 20:19:00 -0000 [thread overview]
Message-ID: <199710240316.WAA02356@eh_pc11.xraylith.wisc.edu> (raw)
Platform: i386-linux-gnulibc1 (libc 5.3.12)
Configure args: --enable-shared
gcc note:
960218-1.c failure is the same old "glob" problem. I assume that
newer versions of libc will have a work around for it.
g++ note:
Note the EH failures. The problem that I had reported for 971016
still exists; basically -fexceptions don't work, but -fsjlj-exceptions
do work. Interesting that HJ Lu reported that he doesn't see the EH
failures using 5.4.(something) libc.
fyi, the same EH problem and work-around on i386-cygwin32, so I'm
inclined to believe it has nothing to do with the libc version.
Sorry, not g77 test results as I'm too lazy to upgrade dejagnu.
============================================================
Test Run By khan on Thu Oct 23 21:11:09 1997
Native configuration is i386-pc-linux-gnulibc1
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
=== gcc tests ===
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
Running /scratch/src/egcs/gcc/testsuite/gcc.c-torture/execute/execute.exp ...
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
=== gcc Summary ===
# of expected passes 4864
# of unexpected failures 10
# of expected failures 4
# of unsupported tests 9
=== g++ tests ===
FAIL: g++.benjamin/warn01.C (test for excess errors)
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.jason/template31.C (test for excess errors)
FAIL: g++.mike/eh10.C Execution test
FAIL: g++.mike/eh12.C Execution test
FAIL: g++.mike/eh14.C Execution test
FAIL: g++.mike/eh16.C Execution test
FAIL: g++.mike/eh17.C Execution test
FAIL: g++.mike/eh18.C Execution test
FAIL: g++.mike/eh2.C Execution test
FAIL: g++.mike/eh21.C Execution test
FAIL: g++.mike/eh24.C Execution test
FAIL: g++.mike/eh25.C Execution test
FAIL: g++.mike/eh26.C Execution test
FAIL: g++.mike/eh27.C Execution test
FAIL: g++.mike/eh28.C Execution test
FAIL: g++.mike/eh29.C Execution test
FAIL: g++.mike/eh3.C Execution test
FAIL: g++.mike/eh31.C Execution test
FAIL: g++.mike/eh33.C Execution test
FAIL: g++.mike/eh34.C Execution test
FAIL: g++.mike/eh35.C Execution test
FAIL: g++.mike/eh36.C Execution test
FAIL: g++.mike/eh37.C Execution test
FAIL: g++.mike/eh38.C Execution test
FAIL: g++.mike/eh39.C Execution test
FAIL: g++.mike/eh40.C Execution test
FAIL: g++.mike/eh41.C Execution test
FAIL: g++.mike/eh42.C Execution test
FAIL: g++.mike/eh44.C Execution test
FAIL: g++.mike/eh47.C Execution test
FAIL: g++.mike/eh48.C Execution test
FAIL: g++.mike/eh49.C Execution test
FAIL: g++.mike/eh5.C Execution test
FAIL: g++.mike/eh50.C Execution test
FAIL: g++.mike/eh51.C Execution test
FAIL: g++.mike/eh6.C Execution test
FAIL: g++.mike/eh8.C Execution test
FAIL: g++.mike/p7912.C Execution test
FAIL: g++.mike/p9706.C Execution test
=== g++ Summary ===
# of expected passes 3336
# of unexpected failures 39
# of unexpected successes 1
# of expected failures 81
# of untested testcases 10
Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/
next reply other threads:[~1997-10-23 20:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 20:19 Mumit Khan [this message]
1997-10-23 21:30 ` (971023) Addendum: i386-linux-gnulibc1 g++ " Mumit Khan
1997-10-23 23:12 ` H.J. Lu
1997-10-24 1:43 ` Theodore Papadopoulo
1997-11-01 21:53 ` Jeffrey A Law
1997-11-02 10:26 ` Thomas Weise
1997-11-02 10:30 ` Thomas Weise
1997-11-02 19:06 ` Jeffrey A Law
1997-11-15 4:58 ` DWARF EH problem (was: Re: (971023) Addendum: i386-linux-gnulibc1 g++ test results) Thomas Weise
[not found] ` <199710240843.KAA07400.cygnus.egcs@mururoa.inria.fr>
1997-10-24 9:35 ` (971023) Addendum: i386-linux-gnulibc1 g++ test results Jason Merrill
1997-10-24 10:46 ` Robert Lipe
1997-10-24 10:59 ` Mumit Khan
1997-10-24 12:11 ` EH bug in Makefile.in H.J. Lu
1997-10-24 14:30 ` Mumit Khan
1997-10-24 14:35 ` H.J. Lu
1997-10-25 9:49 ` Mumit Khan
1997-10-25 20:34 ` Joe Buck
1997-10-26 0:56 ` Mumit Khan
1997-10-26 16:30 ` [ECGS] " chip
[not found] ` <9710260755.AA26107.cygnus.egcs@modi.xraylith.wisc.edu>
1997-10-26 1:17 ` Jason Merrill
1997-10-26 9:49 ` Jeffrey A Law
1997-10-25 11:19 ` acs
1997-10-25 12:18 ` H.J. Lu
1997-10-24 16:16 ` Robert Lipe
1997-10-26 10:22 ` Jeffrey A Law
1997-10-26 12:39 ` EH in egcs H.J. Lu
1997-10-26 12:39 ` Jason Merrill
1997-10-26 16:21 ` H.J. Lu
1997-10-26 19:34 ` Alexandre Oliva
1997-10-26 19:34 ` H.J. Lu
1997-10-26 18:21 ` Alexandre Oliva
1997-10-26 20:44 ` Oleg Krivosheev
1997-10-27 10:50 ` SGI STL patch Oleg Krivosheev
1997-10-27 11:57 ` Joe Buck
1997-10-27 12:00 ` Jason Merrill
1997-10-27 16:30 ` Matt Austern
1997-10-28 15:42 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-28 15:58 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-27 12:24 ` Alexander Stepanov
1997-10-23 22:55 ` (971023) i386-linux-gnulibc1 gcc/g++ test results H.J. Lu
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=199710240316.WAA02356@eh_pc11.xraylith.wisc.edu \
--to=khan@xraylith.wisc.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).