From: Eric Botcazou <ebotcazou@adacore.com>
To: dclarke@blastwave.org
Cc: gcc@gcc.gnu.org
Subject: Re: # of unexpected failures 768 ?
Date: Mon, 31 Oct 2011 16:15:00 -0000 [thread overview]
Message-ID: <201110311557.11803.ebotcazou@adacore.com> (raw)
In-Reply-To: <50609.10.0.66.17.1320017288.squirrel@interact.purplecow.org>
> Then if I use the resultant compiler from a 4.6.1 build I get a massive
> increase in failures on both i386 and Sparc :
>
> http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg03286.html
This is unexpected, results are clean here:
http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg03536.html
> Also, I see bucket loads of these :
>
> FAIL: g++.dg/pch/wchar-1.C -O2 -g -I. (internal compiler error)
PCH seems to be totally broken. AFAIK nothing has changed between 4.6.1 and
4.6.2 in this area. Can you try with 4.6.1? Did you change the machines?
--
Eric Botcazou
next prev parent reply other threads:[~2011-10-31 14:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 9:28 Dennis Clarke
2011-10-31 16:15 ` Eric Botcazou [this message]
2011-10-31 17:22 ` Rainer Orth
2011-10-31 18:21 ` Jonathan Wakely
2011-10-31 18:49 Dennis Clarke
2011-10-31 19:07 ` Rainer Orth
2011-10-31 22:33 ` Jonathan Wakely
2011-11-02 6:52 ` Michael Haubenwallner
2011-11-02 11:41 ` Jonathan Wakely
2011-11-02 13:53 ` Michael Haubenwallner
2011-11-02 17:11 ` Jonathan Wakely
2011-11-02 17:42 ` Michael Haubenwallner
2011-11-02 18:07 ` Rainer Orth
2011-11-02 19:55 ` Michael Haubenwallner
2011-11-02 18:10 ` Ian Lance Taylor
2011-11-02 18:15 ` Rainer Orth
2011-11-02 18:21 ` Ian Lance Taylor
2011-11-02 11:26 Dennis Clarke
2011-11-02 14:29 Dennis Clarke
2011-11-02 18:29 Dennis Clarke
2011-11-03 15:32 Dennis Clarke
2011-11-07 2:14 Dennis Clarke
2011-11-07 7:31 ` Ian Lance Taylor
2011-11-07 18:03 Dennis Clarke
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=201110311557.11803.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=dclarke@blastwave.org \
--cc=gcc@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).