From: Shigeya Suzuki <shigeya@foretune.co.jp>
To: egcs@cygnus.com
Subject: egcs-ss-19980425 result on i386-pc-bsdi3.1
Date: Sun, 26 Apr 1998 08:21:00 -0000 [thread overview]
Message-ID: <19980427002125P.shigeya@foretune.co.jp> (raw)
SOURCE
CVS Snapshot 'egcs_snapshot_19980425'
PLATFORM
i386-pc-bsdi3.1
BSD/OS 3.1, patches up to M310-023 applied.
CONFIGURATION_PARAMETERS
--prefix=/usr/local/egcs
UTILITIES
GNU 'as' snapshot 980301
BOOTSTRAP_WITH
gcc-2.7.2.1 (come with BSD/OS 3.1)
PATCHES
(1) stddef.h patch
Which I sent to egcs-bugs on 5 Apr 1998
Message-Id: <19980405161337D.shigeya@foretune.co.jp>
RESULT_SUMMARY
Test Run By shigeya on Sun Apr 26 23:16:47 1998
Native configuration is i386-pc-bsdi3.1
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
=== gcc Summary ===
# of expected passes 6020
# of unexpected failures 21
# of expected failures 6
# of untested testcases 7
# of unsupported tests 8
=== g++ Summary ===
# of expected passes 3805
# of unexpected failures 2
# of expected failures 74
# of untested testcases 7
=== g77 Summary ===
# of expected passes 175
# of unexpected failures 11
---
FAIL: line on gcc/testsuite/gcc.sum
FAIL: gcc.c-torture/compile/950613-1.c, -O0
FAIL: gcc.c-torture/execute/950511-1.c execution, -O1
FAIL: gcc.c-torture/execute/960218-1.c execution, -O0
FAIL: gcc.c-torture/execute/960218-1.c execution, -O1
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/960218-1.c execution, -O2 -g
FAIL: gcc.c-torture/execute/961122-1.c execution, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O0
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O1
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O2
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O2 -fomit-frame-pointer -finline-functions
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/980424-1.c compilation, -O2 -g
FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O0
FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O1
FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O2
FAIL: gcc.c-torture/execute/ieee/rbug.c execution, -O2 -g
---
FAIL: line on gcc/testsuite/g++.sum
FAIL: g++.jason/thunk2.C (test for excess errors)
FAIL: g++.mike/p9129.C (test for errors, line 10)
---
FAIL: line on gcc/testsuite/g77.sum
FAIL: g77.f-torture/compile/970125-0.f, -O1
FAIL: g77.f-torture/compile/970125-0.f, -O2
FAIL: g77.f-torture/compile/970125-0.f, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/compile/980419-1.f, -O0
FAIL: g77.f-torture/compile/980419-1.f, -O1
FAIL: g77.f-torture/compile/980419-1.f, -O2
FAIL: g77.f-torture/compile/980419-1.f, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/compile/980424-0.f, -O1
FAIL: g77.f-torture/compile/980424-0.f, -O2
FAIL: g77.f-torture/compile/980424-0.f, -O2 -fomit-frame-pointer -finline-functions
FAIL: g77.f-torture/execute/complex_1.f execution, -O2 -fomit-frame-pointer -finline-functions
next reply other threads:[~1998-04-26 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-26 8:21 Shigeya Suzuki [this message]
1998-04-27 2:07 ` Shigeya Suzuki
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=19980427002125P.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).