public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Epler <jepler@inetnebr.com>
To: egcs@cygnus.com
Subject: egcs-971127 i586-pc-linux-gnulibc1 "make check" results
Date: Sun, 30 Nov 1997 08:38:00 -0000	[thread overview]
Message-ID: <19971130080538.48265@inetnebr.com> (raw)

                === libio Summary ===

# of expected passes            40

                === libstdc++ Summary ===

# of expected passes            30

                === gcc Summary ===

# of expected passes            4883
# of expected failures          5
# of unsupported tests          7

                === g++ tests ===

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++.pt/typename5.C (test for excess errors)

                === g++ Summary ===

# of expected passes            3392
# of unexpected failures        8
# of unexpected successes       1
# of expected failures          82
# of untested testcases         6

                === g77 tests ===

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

                === g77 Summary ===

# of expected passes            130
# of unexpected failures        2

It has been suggested elsewhere that having LD_LIBRARY_PATH set before
execution of the tests could cause some of these failures, so I'm
executing the test again with LD_LIBRARY_PATH unset.

I used standard ./configure, no BOOT_CFLAGS or anything else odd.
I did "make bootstrap" and then "make check".  The initial gcc was
egcs-971016.

Jeff
-- 
\/ jepler@inetnebr.com http://www.auburn.net/~errancy/ (0|1(01*0)*1)+

If God didn't mean for us to juggle, tennis balls wouldn't come three
to a can.

                 reply	other threads:[~1997-11-30  8:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19971130080538.48265@inetnebr.com \
    --to=jepler@inetnebr.com \
    --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).