From: Martin Knoblauch <knobi@rocketmail.com>
To: egcs@cygnus.com
Subject: Successful build/check/install of 19980707 on mips-sgi-irix6.5
Date: Wed, 08 Jul 1998 18:52:00 -0000 [thread overview]
Message-ID: <19980708192155.9620.rocketmail@web4.rocketmail.com> (raw)
System: mips-sgi-irix6.5
Bootstrap compiler: egcs-19980628, native binary tools
Configure options: --enable-threads=posix --enable-haifa --with-stabs
gmake bootstrap finished OK
libio, libstdc++ and g77 check out error free
=== gcc Summary ===
# of expected passes 7425
# of unexpected failures 11
# of expected failures 7
# of unsupported tests 18
/mnts/d9/tmp/egcs-snapobjs/gcc/xgcc version egcs-2.91.47 19980707
(gcc2 ss-980609 experimental)
FAIL: gcc.c-torture/execute/980506-2.c execution, -O2
FAIL: gcc.c-torture/execute/980506-2.c execution, -O2 -g
FAIL: gcc.c-torture/execute/980506-2.c execution, -Os
FAIL: gcc.c-torture/execute/980506-2.c execution, -Os
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
FAIL: gcc.c-torture/execute/complex-5.c execution, -Os
FAIL: gcc.dg/980626-1.c (test for excess errors)
=== g++ Summary ===
# of expected passes 4168
# of unexpected failures 21
# of expected failures 103
# of untested testcases 7
/mnts/d9/tmp/egcs-snapobjs/gcc/testsuite/../xgcc version egcs-2.91.47
19980707 (gcc2 ss-980609 experimental)^M
FAIL: g++.jason/rfg15.C (test for excess errors)
FAIL: g++.robertl/980310-2.C (test for excess errors)
FAIL: g++.robertl/980310-3.C (test for excess errors)
FAIL: g++.robertl/eb100.C (test for excess errors)
FAIL: g++.robertl/eb117.C (test for excess errors)
FAIL: g++.robertl/eb130.C (test for excess errors)
FAIL: g++.robertl/eb131.C bar is an unqualified-id. (test for errors,
line 19)
FAIL: g++.robertl/eb131.C (test for excess errors)
FAIL: g++.robertl/eb133.C parse error (test for errors, line 10)
FAIL: g++.robertl/eb25.C (test for excess errors)
FAIL: g++.robertl/eb40.C (test for excess errors)
FAIL: g++.robertl/eb47.C (test for excess errors)
FAIL: g++.robertl/eb53.C (test for excess errors)
FAIL: g++.robertl/eb56.C (test for excess errors)
FAIL: g++.robertl/eb68.C (test for excess errors)
FAIL: g++.robertl/eb72.C (test for excess errors)
FAIL: g++.robertl/eb83.C (test for excess errors)
FAIL: g++.robertl/eb89.C (test for excess errors)
FAIL: g++.robertl/eb96.C (test for excess errors)
FAIL: g++.robertl/float1.C (test for excess errors)
FAIL: g++.robertl/rtti5.C (test for excess errors)
Martin
===
------------------------------------------------------
Martin Knoblauch
email: knobi@knobisoft.de or knobi@rocketmail.com
www: http://www.knobisoft.de
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com
reply other threads:[~1998-07-08 18:52 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=19980708192155.9620.rocketmail@web4.rocketmail.com \
--to=knobi@rocketmail.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).