public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: jsimon@sunchorus.france.sun.com (Julien SIMON - APRIME)
To: egcs@cygnus.com
Subject: Results for egcs-2.91.43 19980628 (gcc2 ss-980502 experimental) on Solaris 2.6
Date: Mon, 29 Jun 1998 06:39:00 -0000	[thread overview]
Message-ID: <199806291209.OAA10325@albinoni.France.Sun.COM> (raw)

No configure flags except --prefix.

Native configuration is sparc-sun-solaris2.6

                === libio tests ===

Running target unix

                === libio Summary ===

# of expected passes            40

                === libstdc++ tests ===

Running target unix

                === libstdc++ Summary ===

# of expected passes            30

                === gcc tests ===

Running target unix

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/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)

                === gcc Summary ===

# of expected passes            7399
# of unexpected failures        15
# of expected failures          7
# of unsupported tests          17
/export/home/work/egcs-19980628-obj/gcc/xgcc version egcs-2.91.43 19980628 (gcc2 ss-980502 experimental)

                === g++ tests ===

Running target unix

FAIL: g++.robertl/eb101.C (test for excess errors)
FAIL: g++.robertl/eb130.C (test for excess errors)
FAIL: g++.robertl/eb131.C (test for excess errors)
FAIL: g++.robertl/eb56.C (test for excess errors)
FAIL: g++.robertl/eb91.C (test for excess errors)

                === g++ Summary ===

# of expected passes            4169
# of unexpected failures        5
# of expected failures          85
# of untested testcases         6
/export/home/work/egcs-19980628-obj/gcc/testsuite/../xgcc version egcs-2.91.43 19980628 (gcc2 ss-980502 experimental)

                 reply	other threads:[~1998-06-29  6:39 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=199806291209.OAA10325@albinoni.France.Sun.COM \
    --to=jsimon@sunchorus.france.sun.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).