This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: diagnostics (was: GCC 3.0 Branch: Guidelines)
Fergus Henderson <fjh@cs.mu.oz.au> writes:
| On 13-Mar-2001, Neil Booth <neil@daikokuya.demon.co.uk> wrote:
| >
| > More generally, after 3.0 one of the things I would like to get done is
| > sharing diagnostic code between the now-integrated CPP and the front ends.
| > As part of that, I'd like to provide a more fine-grained separation of
| > diagnostic types; at present we have little more than Pedwarn, Warn, Error
| > and Ice.
You're my guess, Neil: We're now two in that direction.
| What categories did you have in mind?
It would be useful to instruments the compiler to say when and where
some magic things (such as copy-ctor synthesis) occur or why some
obscur decisions happen (template argument deduction, overloading
resolutions).
I still have a patch Geoff kindly sent me which is
related to notes rather than warnings or errors (Geoff, I didn't forget
your proposal). Obviously, the examples I just gave are C++ specific
but I can imagine that other front-ends could benefit from such
diagnostic categorizations.
-- Gaby