From: "Brad M. Garcia" <bgarcia@fore.com>
To: egcs@cygnus.com
Cc: Bob Sidebotham <rns@fore.com>
Subject: Re: egcs-1.0 on i686 RedHat 5.0 Linux
Date: Tue, 09 Dec 1997 05:53:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.971209085121.540A-100000@spud.eng.fore.com> (raw)
In-Reply-To: <Pine.LNX.3.96.971209071816.27462A-100000@spud.eng.fore.com>
On Tue, 9 Dec 1997, Brad M. Garcia wrote:
> Test summaries:
> --------------
> === g++ Summary ===
>
> # of expected passes 3392
> # of unexpected failures 8
> # of unexpected successes 1
> # of expected failures 82
> # of untested testcases 6
More info on the unexpected cases:
FAIL: g++.eh/spec2.C Execution test
FAIL: g++.eh/spec4.C Execution test
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.mike/eh33.C Execution test
FAIL: g++.mike/eh44.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/p6610a.C Execution test
And I forgot to include the following:
=== g77 Summary ===
# of expected passes 130
# of unexpected failures 2
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
Brad Garcia "These days, you can't throw a tomato out
___/ __ / __ / ___/ the window without hitting a college kid
__/ / / / _/ __/ who knows and loves Linux."
_/ ____/ _/ _| ____/ - Nicholas Petreley, NC WORLD, Aug 1997
next parent reply other threads:[~1997-12-09 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.971209071816.27462A-100000@spud.eng.fore.com>
1997-12-09 5:53 ` Brad M. Garcia [this message]
1997-12-12 3:55 Brad M. Garcia
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.LNX.3.96.971209085121.540A-100000@spud.eng.fore.com \
--to=bgarcia@fore.com \
--cc=egcs@cygnus.com \
--cc=rns@fore.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).