public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edmar at freescale dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/30259] [4.1 branch] ICE on valid code
Date: Wed, 20 Dec 2006 16:11:00 -0000 [thread overview]
Message-ID: <20061220161106.11767.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30259-12262@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from edmar at freescale dot com 2006-12-20 16:11 -------
(In reply to comment #3)
> Subject: Re: [4.1 branch] ICE on valid code
>
> On Tue, 19 Dec 2006, edmar at freescale dot com wrote:
>
> > Still, On December 16 I had a complete build, and on December 17 I have an ICE.
> > It feels more like a regression than moving forward...
>
> A complete build with, no doubt, all C++ tests failing with the problem
> you noted in <http://gcc.gnu.org/ml/gcc/2006-09/msg00126.html>. Because
> such a build is not particularly useful, I have taken a base with
> t-ppccomm hacked to avoid building libgcc with -mlong-double-128 as the
> appropriate baseline for testing.
I disagree with that. First there is the C compiler, which is the most used by
our customers, second, the C++ problem was manageable. Those are dejagnu
results (C, C++, gfortran) from December 12:
# of expected passes 40225
# of unexpected failures 58
# of expected failures 81
# of unresolved testcases 94
# of untested testcases 28
# of unsupported tests 493
# of expected passes 13148
# of unexpected failures 43
# of unexpected successes 2
# of expected failures 65
# of unresolved testcases 40
# of unsupported tests 136
# of expected passes 15334
# of unexpected failures 94
# of expected failures 6
# of unresolved testcases 6
# of unsupported tests 91
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30259
next prev parent reply other threads:[~2006-12-20 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 17:48 [Bug c/30259] New: " edmar at freescale dot com
2006-12-19 18:16 ` [Bug c/30259] " joseph at codesourcery dot com
2006-12-19 18:50 ` edmar at freescale dot com
2006-12-19 21:34 ` joseph at codesourcery dot com
2006-12-20 16:11 ` edmar at freescale dot com [this message]
2007-02-04 16:40 ` [Bug target/30259] " guenter at roeck-us dot net
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=20061220161106.11767.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).