From: Peter Schmid <schmid@ltoi.iap.physik.tu-darmstadt.de>
To: egcs@cygnus.com
Subject: testsuite results
Date: Sat, 29 Nov 1997 03:01:00 -0000 [thread overview]
Message-ID: <Pine.A32.3.95.971129115235.12143A-100000@ltoi.iap.physik.tu-darmstadt.de> (raw)
These are the results of the gcc, g++ and g77 testsuite.
I am using libc-5.4.40 and binutils-2.8.1.0.15
Native configuration is i386-pc-linux-gnulibc1
=== gcc tests ===
=== gcc Summary ===
# of expected passes 4883
# of expected failures 5
# of unsupported tests 7
/dos/peter/ftp/gcc/egcs-971127/gcc/xgcc version egcs-2.90.19 971127 (gcc2-970802 experimental)
=== g++ tests ===
=== g++ Summary ===
# of expected passes 3400
# of unexpected successes 3
# of expected failures 80
# of untested testcases 6
/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/../xgcc version egcs-2.90.19 971127 (gcc2-970802 experimental)
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
=== g77 tests ===
=== g77 Summary ===
# of expected passes 130
# of unexpected failures 2
/dos/peter/ftp/gcc/egcs-971127/gcc/g77 version egcs-2.90.19 971127 (gcc2-970802 experimental)
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: g77.f-torture/execute/dnrm2.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
The
XPASS:g++.jason/destruct3.C - (test for bogus messages, line 38)
is an internal compiler error in disguise:
Executing on host: /dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/../xgcc -B/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/../ /dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/g++.old-deja/g++.jason/destruct3.C -ansi -pedantic-errors -I/dos/peter/ftp/gcc/egcs-9
71127/libio -I/dos/peter/ftp/gcc/egcs-971127/libio -I/dos/peter/ftp/gcc/egcs-971127/libstdc++ -I/dos/peter/ftp/gcc/egcs-971127/libstdc++/stl -I/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/../include -c -o /tmp/destruct3.o
compiler exited with status 1
output is:
/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/g++.old-deja/g++.jason/destruct3.C:35: warning: direct base `ccUnwind' inaccessible in `ccVSTool' due to ambiguity
/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/g++.old-deja/g++.jason/destruct3.C:35: Internal compiler error 369.
/dos/peter/ftp/gcc/egcs-971127/gcc/testsuite/g++.old-deja/g++.jason/destruct3.C:35: Please submit a full bug report to `egcs-bugs@cygnus.com'.
Are you going to fix this?
At least the compiler should not crash.
Peter Schmid
next reply other threads:[~1997-11-29 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-29 3:01 Peter Schmid [this message]
[not found] <Pine.A32.3.95.971124095550.18831A-100000.cygnus.egcs@ltoi.iap.physik.tu-darmstadt.de>
1997-11-24 21:47 ` Jason Merrill
1997-11-25 11:44 ` Joe Buck
1997-11-25 19:10 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-11-24 1:05 Peter Schmid
1997-10-26 7:12 Peter Schmid
1997-10-18 9:55 Peter Schmid
1997-10-13 13:41 Mike Stump
1997-10-12 10:44 Peter Schmid
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=Pine.A32.3.95.971129115235.12143A-100000@ltoi.iap.physik.tu-darmstadt.de \
--to=schmid@ltoi.iap.physik.tu-darmstadt.de \
--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).