public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: Andrew Haley <aph@redhat.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: # of unexpected failures 768 ?
Date: Mon, 31 Oct 2011 14:07:00 -0000	[thread overview]
Message-ID: <39881.10.0.66.17.1320070044.squirrel@interact.purplecow.org> (raw)


> On 10/31/2011 01:26 PM, Dennis Clarke wrote:
>> This seems blatantly wrong. At what point does one throw out the result
>> of
>> a bootstrap as not-acceptable ? With any non-zero value for "unexpected
>> failures" ?
>
> There's no simple answer.
>
> You need to look at the log to see what's going wrong, and run a few
> of the test cases.  There's probably a common cause.

I kept a full log of the whole test process and see tons of "internal
compiler error" which really scares me.

I'll see if I can find some common cause, hopefully.

Dennis



-- 
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke           | Solaris and Linux and Open Source |
| dclarke@blastwave.org   | Respect for open standards.       |
+-------------------------+-----------------------------------+

             reply	other threads:[~2011-10-31 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:07 Dennis Clarke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-31 14:40 Dennis Clarke
2011-10-31 14:42 ` Andrew Haley
2011-10-31 16:02 ` Jonathan Wakely
2011-10-31 14:15 Dennis Clarke
2011-10-31 14:24 ` Andrew Haley
2011-10-31 13:27 Dennis Clarke
2011-10-31 14:03 ` Andrew Haley

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=39881.10.0.66.17.1320070044.squirrel@interact.purplecow.org \
    --to=dclarke@blastwave.org \
    --cc=aph@redhat.com \
    --cc=gcc-help@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).