From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: egcs@cygnus.com
Subject: egcs-980315 on sparc-sun-solaris2.5.1 test results
Date: Wed, 18 Mar 1998 14:08:00 -0000 [thread overview]
Message-ID: <199803181015.GAA26124@pincoya.inf.utfsm.cl> (raw)
CFLAGS= -O2 -fomit-frame-pointer, --enable-{shared,haifa,threads}
Note that I killed the gcc.c-torture/execute/loop-2c.c compilations after
some 10 min CPU time, they seemed to have gone into an infinite loop.
WARNING: Couldn't find the global config file.
Test Run By broot on Wed Mar 18 01:15:37 1998
Native configuration is sparc-sun-solaris2.5.1
=== libio tests ===
=== libio Summary ===
# of expected passes 40
WARNING: Couldn't find the global config file.
Test Run By broot on Wed Mar 18 01:19:43 1998
Native configuration is sparc-sun-solaris2.5.1
=== libstdc++ tests ===
=== libstdc++ Summary ===
# of expected passes 30
WARNING: Couldn't find the global config file.
Test Run By broot on Wed Mar 18 01:23:53 1998
Native configuration is sparc-sun-solaris2.5.1
=== gcc tests ===
FAIL: gcc.c-torture/execute/loop-2c.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/loop-2c.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
FAIL: gcc.c-torture/execute/loop-2d.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gcc.c-torture/execute/loop-2d.c compilation, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops
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
=== gcc Summary ===
# of expected passes 5994
# of unexpected failures 9
# of expected failures 6
# of untested testcases 4
# of unsupported tests 9
WARNING: Couldn't find the global config file.
Test Run By broot on Wed Mar 18 04:09:04 1998
Native configuration is sparc-sun-solaris2.5.1
=== g++ tests ===
FAIL: g++.ext/arrnew.C (test for excess errors)
FAIL: g++.ext/default.C (test for excess errors)
FAIL: g++.jason/operator.C no class argument (test for errors, line 26)
FAIL: g++.jason/operator.C invalid first argument (test for errors, line 28)
FAIL: g++.jason/operator.C ditto (test for errors, line 29)
FAIL: g++.jason/operator.C return value, nonmember (test for errors, line 31)
FAIL: g++.jason/operator.C (test for excess errors)
XPASS: g++.mike/ns3.C (test for errors, line 1)
FAIL: g++.mike/p10849a.C (test for excess errors)
FAIL: g++.other/friend1.C (test for excess errors)
FAIL: g++.pt/memtemp42.C (test for excess errors)
FAIL: g++.pt/memtemp43.C (test for excess errors)
FAIL: g++.pt/memtemp44.C (test for excess errors)
FAIL: g++.pt/memtemp45.C (test for excess errors)
FAIL: g++.pt/memtemp46.C (test for excess errors)
FAIL: g++.pt/memtemp47.C (test for excess errors)
FAIL: g++.pt/memtemp5.C (test for excess errors)
FAIL: g++.pt/memtemp53.C (test for excess errors)
FAIL: g++.pt/memtemp61.C (test for excess errors)
FAIL: g++.pt/memtemp62.C (test for excess errors)
FAIL: g++.pt/memtemp63.C (test for excess errors)
FAIL: g++.pt/memtemp67.C (test for excess errors)
FAIL: g++.pt/memtemp69.C (test for excess errors)
FAIL: g++.pt/memtemp7.C (test for excess errors)
FAIL: g++.pt/vaarg.C Execution test
=== g++ Summary ===
# of expected passes 3701
# of unexpected failures 24
# of unexpected successes 1
# of expected failures 79
# of untested testcases 6
WARNING: Couldn't find the global config file.
Test Run By broot on Wed Mar 18 05:15:03 1998
Native configuration is sparc-sun-solaris2.5.1
=== g77 tests ===
=== g77 Summary ===
# of expected passes 168
reply other threads:[~1998-03-18 14:08 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=199803181015.GAA26124@pincoya.inf.utfsm.cl \
--to=vonbrand@inf.utfsm.cl \
--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).