public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: nickc@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/6172: [fr30-elf] does not build
Date: Mon, 09 Dec 2002 09:56:00 -0000	[thread overview]
Message-ID: <20021209175603.16954.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/6172; it has been noted by GNATS.

From: Hans-Peter Nilsson <hp@bitrange.com>
To: gcc-bugs@gcc.gnu.org,  <gcc-prs@gcc.gnu.org>,  <nickc@gcc.gnu.org>, 
     <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: bootstrap/6172: [fr30-elf] does not build
Date: Mon, 9 Dec 2002 05:34:39 -0500 (EST)

 It is relevant to add that most test-cases fail:
                 === gcc Summary ===
 
 # of expected passes            16034
 # of unexpected failures        4825
 # of expected failures          62
 # of unresolved testcases       49
 # of unsupported tests          163
 x/fr30-sim/gcc/xgcc version 3.3 20021207 (experimental)
                 === g++ Summary ===
 
 # of expected passes            6725
 # of unexpected failures        1043
 # of expected failures          93
 # of unresolved testcases       23
 # of untested testcases         29
 # of unsupported tests          20
 x/fr30-sim/gcc/testsuite/../g++ version 3.3 20021207 (experimental)
                 === objc Summary ===
 
 # of expected passes            653
 # of unexpected failures        500
 x/fr30-sim/gcc/xgcc version 3.3 20021207 (experimental)
 


             reply	other threads:[~2002-12-09 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09  9:56 Hans-Peter Nilsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-11 16:36 Joel Sherrill
2002-12-11 16:26 Hans-Peter Nilsson
2002-12-11 16:16 Joel Sherrill
2002-12-08 21:12 hp
2002-12-05 10:36 Nick Clifton
2002-12-05  7:23 joel

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=20021209175603.16954.qmail@sources.redhat.com \
    --to=hp@bitrange.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nickc@gcc.gnu.org \
    /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).