public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Rees <drees@oto.dyn.ml.org>
To: egcs@cygnus.com
Subject: Results for egcs-2.91.42 19980621 (gcc2 ss-980502 experimental) testsuite on i586-pc-linux-gnulibc1
Date: Sun, 28 Jun 1998 18:01:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.980628154621.5767A-100000@oto.dyn.ml.org> (raw)

Native configuration is i586-pc-linux-gnulibc1

		=== libio tests ===


Running target unix

		=== libio Summary ===

# of expected passes		40
		=== libstdc++ tests ===


Running target unix

		=== libstdc++ Summary ===

# of expected passes		30
		=== gcc tests ===


Running target unix
FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 -g 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -Os 
FAIL: gcc.c-torture/execute/980526-1.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/980612-1.c execution,  -O1 
FAIL: gcc.c-torture/execute/980612-1.c execution,  -O2 
FAIL: gcc.c-torture/execute/980612-1.c execution,  -O2 -g 
FAIL: gcc.c-torture/execute/980612-1.c execution,  -Os 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O1 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O2 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -O2 -g 
FAIL: gcc.c-torture/execute/ieee/980619-1.c execution,  -Os 
FAIL: gcc.dg/clobbers.c execution test

		=== gcc Summary ===

# of expected passes		7404
# of unexpected failures	17
# of expected failures		7
# of unsupported tests		11
/disk2/users/drees/egcs/gcc/xgcc version egcs-2.91.42 19980621 (gcc2 ss-980502 experimental)

		=== g++ tests ===


Running target unix
FAIL: g++.robertl/eb129.C (test for excess errors)
FAIL: g++.robertl/eb130.C (test for excess errors)
FAIL: g++.robertl/eb131.C (test for excess errors)
FAIL: g++.robertl/eb56.C (test for excess errors)

		=== g++ Summary ===

# of expected passes		4169
# of unexpected failures	4
# of expected failures		84
# of untested testcases		7
/disk2/users/drees/egcs/gcc/testsuite/../xgcc version egcs-2.91.42 19980621 (gcc2 ss-980502 experimental)

		=== g77 tests ===


Running target unix

		=== g77 Summary ===

# of expected passes		237
/disk2/users/drees/egcs/gcc/g77 version egcs-2.91.42 19980621 (gcc2 ss-980502 experimental) (from FSF-g77 version 0.5.23)
gcc version egcs-2.91.42 19980621 (gcc2 ss-980502 experimental)


configure flags: --host=i586-pc-linux-gnulibc1 --prefix=/opt/egcs --norecursion


             reply	other threads:[~1998-06-28 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-28 18:01 David Rees [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-06-24  2:28 Alexandre Oliva

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.980628154621.5767A-100000@oto.dyn.ml.org \
    --to=drees@oto.dyn.ml.org \
    --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).