public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Springer <jan.springer@informatik.uni-weimar.de>
To: egcs@cygnus.com
Subject: Results for egcs-971031 g++ testsuite on mips-sgi-irix6.2
Date: Sat, 01 Nov 1997 12:26:00 -0000	[thread overview]
Message-ID: <345B8F51.2781@informatik.uni-weimar.de> (raw)

Test Run By root on Sat Nov  1 20:50:31 1997
Native configuration is mips-sgi-irix6.2

                === g++ tests ===

FAIL: g++.benjamin/warn01.C (test for excess errors)
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
FAIL: g++.jason/rfg10.C enum overflow (test for errors, line 9)
FAIL: g++.jason/rfg10.C (test for excess errors)
FAIL: g++.jason/template31.C (test for excess errors)
FAIL: g++.mike/eh10.C  Execution test
FAIL: g++.mike/eh12.C  Execution test
FAIL: g++.mike/eh14.C  Execution test
FAIL: g++.mike/eh16.C  Execution test
FAIL: g++.mike/eh17.C  Execution test
FAIL: g++.mike/eh18.C  Execution test
FAIL: g++.mike/eh2.C  Execution test
FAIL: g++.mike/eh21.C  Execution test
FAIL: g++.mike/eh23.C  Execution test
FAIL: g++.mike/eh24.C  Execution test
FAIL: g++.mike/eh25.C  Execution test
FAIL: g++.mike/eh26.C  Execution test
FAIL: g++.mike/eh27.C  Execution test
FAIL: g++.mike/eh28.C  Execution test
FAIL: g++.mike/eh29.C  Execution test
FAIL: g++.mike/eh3.C  Execution test
FAIL: g++.mike/eh31.C  Execution test
FAIL: g++.mike/eh33.C  Execution test
FAIL: g++.mike/eh34.C  Execution test
FAIL: g++.mike/eh35.C  Execution test
FAIL: g++.mike/eh36.C  Execution test
FAIL: g++.mike/eh37.C  Execution test
FAIL: g++.mike/eh38.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/eh47.C  Execution test
FAIL: g++.mike/eh48.C  Execution test
FAIL: g++.mike/eh49.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/eh55.C  Execution test
FAIL: g++.mike/eh6.C  Execution test
FAIL: g++.mike/eh8.C  Execution test
FAIL: g++.mike/p7912.C  Execution test
FAIL: g++.mike/p9706.C  Execution test
FAIL: g++.mike/p9732b.C  Execution test

                === g++ Summary ===

# of expected passes            3333
# of unexpected failures        44
# of unexpected successes       1
# of expected failures          85
# of untested testcases         6
/usr/local/src/egcs-971031/gcc/testsuite/../xgcc version egcs-2.90.15
971031 (gcc2-970802 experimental)

configure flags: --enable-shared
BOOT_CFLAGS: -O4 -g

        j.

-- 
+---------------------------------------+-----------------------+
| jan springer                          | this                  |
| student of applied computer science   |    space              |
| bauhaus-university weimar, germany    |        reserved       |
+---------------------------------------+               for     |
| jan.springer@informatik.uni-weimar.de |                 quote |
+---------------------------------------+-----------------------+

                 reply	other threads:[~1997-11-01 12:26 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=345B8F51.2781@informatik.uni-weimar.de \
    --to=jan.springer@informatik.uni-weimar.de \
    --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).