From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: drow@false.org (Daniel Jacobowitz),
Andrew_Pinski@PlayStation.Sony.Com,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, C++] Make Canonical ICE instead of just warn when mismatching
Date: Fri, 05 Jan 2007 06:41:00 -0000 [thread overview]
Message-ID: <m3mz4y9ds9.fsf@zeus.integrable-solutions.net> (raw)
In-Reply-To: <200701050000.l0500MfN029957@localhost.localdomain>
Andrew Pinski <pinskia@physics.uc.edu> writes:
[...]
| Again the warning is useless to the user as it is an internal GCC issue
| rather than a problem with their code.
Labeling the diagnotics "warning: " is indeed confusing; I should have
caught that earlier. Still the diagnotic is useful to us, however
useless you think it is for user. So we want to know about it.
Consequently, I think warning() or error() is NOT a good thing. We
should either issue sorry() or invent a new diagnostic category -- we
only need an enumerator and a forwarding function for that.
-- Gaby
next prev parent reply other threads:[~2007-01-05 6:41 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 [this message]
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
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=m3mz4y9ds9.fsf@zeus.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=Andrew_Pinski@PlayStation.Sony.Com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).