public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Clemens Vonrhein <vonrhein@chemie.uni-freiburg.de>
To: egcs@cygnus.com
Subject: egcs-1.0 on alphaev5-unknown-linux-gnu
Date: Thu, 11 Dec 1997 02:24:00 -0000	[thread overview]
Message-ID: <199712110939.KAA28239@bio5.chemie.uni-freiburg.de> (raw)

I was able to build egcs-1.0 (make bootstrap) on a RedHat 5.0
Alpha/Linux (2.0.30) system.

Clemens

Here's some o/p of the testsuite (make -k check):

                === g++ Summary ===

# of expected passes            3363
# of unexpected failures        17
# of unexpected successes       4
# of expected failures          99
# of untested testcases         6
FAIL: g++.benjamin/p12475.C  (test for warnings, line 4)
FAIL: g++.brendan/copy9.C (test for excess errors)
FAIL: g++.brendan/ptolemy2.C (test for excess errors)
FAIL: g++.brendan/template9.C (test for excess errors)
FAIL: g++.jason/2371.C (test for excess errors)
FAIL: g++.jason/template24.C (test for excess errors)
FAIL: g++.jason/template31.C (test for excess errors)
FAIL: g++.jason/typeid1.C (test for excess errors)
FAIL: g++.law/arg8.C (test for excess errors)
FAIL: g++.law/code-gen5.C (test for excess errors)
FAIL: g++.law/cvt2.C (test for excess errors)
FAIL: g++.law/virtual3.C (test for excess errors)
FAIL: g++.mike/eh2.C (test for excess errors)
FAIL: g++.mike/net34.C (test for excess errors)
FAIL: g++.mike/net46.C (test for excess errors)
FAIL: g++.mike/p658.C (test for excess errors)
FAIL: g++.mike/p6610a.C  Execution test

                === gcc Summary ===

# of expected passes            4875
# of unexpected failures        8
# of expected failures          5
# of unsupported tests          7
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 
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 
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 

-- 

***************************************************************************
* Clemens Vonrhein   email vonrhein@bio5.chemie.uni-freiburg.de           *
*                    WWW   http://bio5.chemie.uni-freiburg.de/~vonrhein/  *
*                                                                         *
*         Institut f. Org. Chemie u. Biochemie                            *
*         Albertstr.21                                                    *
* D-79104 Freiburg i.Br. (Germany)                                        *
*  Tel.: 761/203-6061   FAX: 761/203-6161                                 *
***************************************************************************

                 reply	other threads:[~1997-12-11  2:24 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=199712110939.KAA28239@bio5.chemie.uni-freiburg.de \
    --to=vonrhein@chemie.uni-freiburg.de \
    --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).