From: Shigeya Suzuki <shigeya@foretune.co.jp>
To: egcs@cygnus.com
Subject: egcs_snapshot_19980707 result on sparc-sun-sunos2.6
Date: Tue, 14 Jul 1998 09:12:00 -0000 [thread overview]
Message-ID: <19980714181602L.shigeya@foretune.co.jp> (raw)
This looks great!
------------------------------
SOURCE
CVS Snapshot 'egcs_snapshot_19980707'
(actually, via egcs_snapshot_latest)
PLATFORM
sparc-sun-sunos2.6, Japanese environment
CONFIGURATION_PARAMETERS
--prefix=/usr/local/egcs
--with-gnu-ld
--with-gnu-as
(haifa-disabled)
UTILITIES
GNU binutils 2.9.1
BOOTSTRAP_WITH
gcc-2.7.2.3
PATCHES
None
COMMENTS
RESULT_SUMMARY
Test Run By shigeya on Mon Jul 13 19:11:35 1998
Native configuration is sparc-sun-solaris2.6
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
=== gcc Summary ===
# of expected passes 7422
# of unexpected failures 14
# of expected failures 7
# of unsupported tests 17
=== g++ Summary ===
# of expected passes 4190
# of unexpected failures 11
# of expected failures 87
# of untested testcases 6
=== g77 Summary ===
# of expected passes 367
---
FAIL: line on gcc/testsuite/gcc.sum
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/980526-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 -g
FAIL: gcc.c-torture/execute/loop-2f.c execution, -Os
FAIL: gcc.dg/980626-1.c (test for excess errors)
FAIL: gcc.misc-tests/gcov-1.c (test for excess errors)
FAIL: gcov failed: Could not open data file gcov-1.da.
FAIL: gcc.misc-tests/gcov-2.c (test for excess errors) (PRMS 8294)
---
FAIL: line on gcc/testsuite/g++.sum
FAIL: g++.ns/koenig4.C (test for excess errors)
FAIL: g++.ns/lookup4.C (test for excess errors)
FAIL: g++.ns/using7.C (test for excess errors)
FAIL: g++.robertl/eb101.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/eb56.C (test for excess errors)
FAIL: g++.robertl/eb83.C (test for excess errors)
FAIL: g++.robertl/eb91.C (test for excess errors)
---
FAIL: line on gcc/testsuite/g77.sum
reply other threads:[~1998-07-14 9:12 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=19980714181602L.shigeya@foretune.co.jp \
--to=shigeya@foretune.co.jp \
--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).