public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jochen Kuepper <jochen@pc1.uni-duesseldorf.de>
To: egcs@cygnus.com
Cc: law@cygnus.com
Subject: Results of egcs-1.00 on alphaev5-dec-osf4.0b
Date: Thu, 04 Dec 1997 01:38:00 -0000	[thread overview]
Message-ID: <9712040936.AA00124@bacchus.pc1.uni-duesseldorf.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2359 bytes --]

Hi,

the results of building/checking egcs-1.00 on alphaev5-dec-osf4.0b
(../configure --with-stabs ; gmake bootstrap ; gmake -k check):

=== libio Summary ===
  # of expected passes            40
=== libstdc++ Summary ===
  # of expected passes            30
=== gcc Summary ===
  # of expected passes            4862
  # of unexpected failures        8
  # of expected failures          5
  # of unsupported tests          9
     FAIL: gcc.c-torture/execute/complex-5.c execution,  -O0 
     FAIL: gcc.c-torture/execute/complex-5.c execution,  -O1 
     FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2
           -finline-functions 
     FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2
           -fomit-frame-pointer -finline-functions 
     FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O0 
     FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O1 
     FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O2
           -fomit-frame-pointer -finline-functions 
     FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O2
           -fomit-frame-pointer -finline-functions 
=== g77 Summary ===
  # of expected passes            131
  # of unexpected failures        1
     FAIL: g77.f-torture/execute/dnrm2.f execution,  -O0 
=== g++ Summary ===
  # of expected passes            3390
  # of unexpected failures        1
  # of unexpected successes       4
  # of expected failures          82
  # of untested testcases         10
     FAIL: g++.benjamin/p12475.C  (test for warnings, line 4)
     XPASS: g++.brendan/array1.C overflow in array dimension.* ,
            (test for errors, line 6)
     XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
     XPASS: g++.mike/dyncast1.C  Execution test
     XPASS: g++.mike/dyncast2.C  Execution test

Pretty good for a first release.

Cheers,
Jochen


-----------------------------------------------------------------------
  Jochen Küpper

  Heinrich-Heine-Universität Düsseldorf     jochen@uni-duesseldorf.de
  Institut für Physikalische Chemie I
  Universitätsstrasse 1, Geb 26.43.02.19       phone ++49-211-8113681
  40225 Düsseldorf                             fax   ++49-211-8115195
  Germany             http://www-public.rz.uni-duesseldorf.de/~jochen
-----------------------------------------------------------------------

                 reply	other threads:[~1997-12-04  1:38 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=9712040936.AA00124@bacchus.pc1.uni-duesseldorf.de \
    --to=jochen@pc1.uni-duesseldorf.de \
    --cc=egcs@cygnus.com \
    --cc=law@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).