public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Subject: Results for haifa-disabled egcs-980221 testsuite on mips-sgi-irix6.3
Date: Tue, 24 Feb 1998 19:54:00 -0000	[thread overview]
Message-ID: <199802250212.AAA03335@tiete.dcc.unicamp.br> (raw)

Native configuration is mips-sgi-irix6.3

		=== g++ tests ===

FAIL: g++.mike/p5840.C (test for excess errors)

		=== g++ Summary ===

# of expected passes		3671
# of unexpected failures	1
# of expected failures		84
# of untested testcases		6
/tmp/egcs/gcc/testsuite/../xgcc version egcs-2.91.09 980221 (gcc-2.8.0 release)

		=== g77 tests ===


		=== g77 Summary ===

# of expected passes		132
/tmp/egcs/gcc/g77 version egcs-2.91.09 980221 (gcc-2.8.0 release)

		=== gcc tests ===

FAIL: gcc.c-torture/execute/complex-5.c execution,  -O0 
FAIL: gcc.c-torture/execute/complex-5.c execution,  -O1 
FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2 
FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2 -g 

		=== gcc Summary ===

# of expected passes		5990
# of unexpected failures	5
# of expected failures		6
# of unsupported tests		9
/tmp/egcs/gcc/xgcc version egcs-2.91.09 980221 (gcc-2.8.0 release)

		=== libio tests ===


		=== libio Summary ===

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


		=== libstdc++ Summary ===

# of expected passes		30
configure flags: --enable-shared --disable-haifa --disable-multilib
BOOT_CFLAGS: -O4 -g

             reply	other threads:[~1998-02-24 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-24 19:54 Alexandre Oliva [this message]
1998-02-25  6:39 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=199802250212.AAA03335@tiete.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --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).