public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: egcs@cygnus.com
Subject: egcs-19980508 on sparc-sun-solaris2.5.1 test results
Date: Tue, 12 May 1998 05:17:00 -0000	[thread overview]
Message-ID: <199805121212.IAA23577@pincoya.inf.utfsm.cl> (raw)

sparc-sun-solaris2.5.1, no much further patches

--enable-{shared,threads,haifa}

{C,CXX,F77,BOOT_C}FLAGS = -O2 -fomit-frame-pointer

WARNING: Couldn't find the global config file.
Test Run By broot on Mon May 11 16:36:39 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 Mon May 11 16:40:37 1998
Native configuration is sparc-sun-solaris2.5.1

		=== libstdc++ tests ===

FAIL: tstring.cc -O compilation

		=== libstdc++ Summary ===

# of expected passes		27
# of unexpected failures	1
# of expected failures		2

WARNING: Couldn't find the global config file.
Test Run By broot on Mon May 11 16:45:16 1998
Native configuration is sparc-sun-solaris2.5.1

		=== gcc tests ===

FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 -fomit-frame-pointer -finline-functions 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -O2 -g 
FAIL: gcc.c-torture/execute/980505-1.c execution,  -Os 
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/980502-1.c (test for excess errors)

		=== gcc Summary ===

# of expected passes		7206
# of unexpected failures	11
# of expected failures		7
# of unsupported tests		12

WARNING: Couldn't find the global config file.
Test Run By broot on Mon May 11 19:21:27 1998
Native configuration is sparc-sun-solaris2.5.1

		=== g++ tests ===

FAIL: g++.law/code-gen5.C (test for excess errors)
XPASS: g++.mike/ns11.C (test for excess errors)
XPASS: g++.mike/ns11.C  Execution test
XPASS: g++.mike/ns13.C (test for excess errors)
XPASS: g++.mike/ns14.C (test for excess errors)
XPASS: g++.mike/ns9.C (test for excess errors)
XPASS: g++.mike/ns9.C  Execution test

		=== g++ Summary ===

# of expected passes		3817
# of unexpected failures	1
# of unexpected successes	6
# of expected failures		68
# of untested testcases		6

WARNING: Couldn't find the global config file.
Test Run By broot on Mon May 11 20:32:42 1998
Native configuration is sparc-sun-solaris2.5.1

		=== g77 tests ===

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/970125-0.f,  -Os  

		=== g77 Summary ===

# of expected passes		222
# of unexpected failures	4

                 reply	other threads:[~1998-05-12  5:17 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=199805121212.IAA23577@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).