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-970929 g++ testsuite on i586-pc-linux-gnulibc1
Date: Fri, 03 Oct 1997 10:01:00 -0000	[thread overview]
Message-ID: <199710031656.NAA14729@grande.dcc.unicamp.br> (raw)

Test Run By oliva on Thu Oct  2 21:49:44 1997
Native configuration is i586-pc-linux-gnulibc1

		=== g++ tests ===

FAIL: g++.brendan/crash39.C (test for excess errors)
FAIL: g++.jason/template31.C (test for excess errors)
FAIL: g++.law/missed-error2.C extern (test for errors, line 20)
FAIL: g++.mike/dyncast1.C  Execution test
FAIL: g++.mike/dyncast2.C  Execution test
FAIL: g++.mike/eh10.C  Execution test
FAIL: g++.mike/eh16.C  Execution test
FAIL: g++.mike/eh17.C  Execution test
FAIL: g++.mike/eh2.C  Execution test
FAIL: g++.mike/eh23.C  Execution test
FAIL: g++.mike/eh25.C  Execution test
FAIL: g++.mike/eh29.C  Execution test
FAIL: g++.mike/eh3.C  Execution test
FAIL: g++.mike/eh33.C  Execution test
FAIL: g++.mike/eh35.C  Execution test
FAIL: g++.mike/eh39.C  Execution test
FAIL: g++.mike/eh40.C  Execution test
FAIL: g++.mike/eh41.C  Execution test
FAIL: g++.mike/eh42.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/eh6.C  Execution test

		=== g++ Summary ===

# of expected passes		3354
# of unexpected failures	24
# of expected failures		80
# of untested testcases		6
/n/temp1/gcctest/bin/egcsc version egcs-2.90.11 970929 (gcc2-970802 experimental)
configure flags: --with-gnu-as --with-gnu-ld --enable-shared
BOOT_CFLAGS: -O4 -g

                 reply	other threads:[~1997-10-03 10:01 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=199710031656.NAA14729@grande.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).