From: Andrew Pinski <pinskia@gmail.com>
To: Mike Stump <mrs@apple.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Doug Gregor <doug.gregor@gmail.com>,
Brooks Moses <brooks.moses@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, C++] Make Canonical ICE instead of just warn when mismatching
Date: Mon, 08 Jan 2007 05:14:00 -0000 [thread overview]
Message-ID: <1168233222.9076.22.camel@celery.andrew.com> (raw)
In-Reply-To: <FF00481E-80AB-451D-8FB8-5A1613482077@apple.com>
On Fri, 2007-01-05 at 11:02 -0800, Mike Stump wrote:
> If there is a bug in the compiler, the right answer is always
> obtained with checking. The wrong answer is obtained without
> checking, and there is no warning/error and also no way to know that
> the the bug existed.
Right which is why this should not be just a warning for checking. This
case is that we can recover from but only at expense of compile time
speed. If we had it as an ICE before, we would have noticed the
problem, the same day the patch went in. So we get only a warning if
checking defaults or the user explicitly turns on the checking. So
really most people will not see the ICE at all unless someone tells them
to turn on the checking. I don't see why this case is special compared
to all other checking code inside GCC, some of which we can recover from
if we wanted to but we don't currently.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2007-01-08 5:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 5:30 Andrew_Pinski
2007-01-04 19:23 ` Mike Stump
2007-01-04 21:00 ` Andrew_Pinski
2007-01-04 22:26 ` Doug Gregor
2007-01-06 8:25 ` Eric Botcazou
2007-01-04 22:36 ` Mike Stump
2007-01-04 23:44 ` Andrew_Pinski
2007-01-04 23:48 ` Daniel Jacobowitz
2007-01-04 23:59 ` Andrew Pinski
2007-01-05 0:03 ` Daniel Jacobowitz
2007-01-05 0:17 ` Andrew_Pinski
2007-01-05 6:44 ` Gabriel Dos Reis
2007-01-05 14:14 ` Doug Gregor
2007-01-05 14:16 ` Richard Kenner
2007-01-05 6:41 ` Gabriel Dos Reis
2007-01-05 2:04 ` Mike Stump
2007-01-05 3:13 ` Brooks Moses
2007-01-05 14:13 ` Doug Gregor
2007-01-05 14:20 ` Richard Guenther
2007-01-05 14:35 ` Doug Gregor
2007-01-05 19:04 ` Mike Stump
2007-01-05 19:12 ` Richard Guenther
2007-01-08 5:14 ` Andrew Pinski [this message]
2007-01-05 6:35 ` Gabriel Dos Reis
2007-01-05 6:33 ` Gabriel Dos Reis
2007-01-23 3:41 ` Mark Mitchell
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=1168233222.9076.22.camel@celery.andrew.com \
--to=pinskia@gmail.com \
--cc=brooks.moses@codesourcery.com \
--cc=doug.gregor@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mrs@apple.com \
--cc=richard.guenther@gmail.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).