This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions)
- From: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: "Tom Tromey" <tromey at redhat dot com>, "Aldy Hernandez" <aldyh at redhat dot com>, dberlin at dberlin dot org, jakub at redhat dot com, gcc at gcc dot gnu dot org, gdr at integrable-solutions dot net, "Chris Lattner" <clattner at apple dot com>, "Gcc Patch List" <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 14 Aug 2008 14:27:18 +0200
- Subject: Re: [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions)
- References: <6c33472e0808140340o2a56b9f4n149025bfa8426331@mail.gmail.com> <Pine.LNX.4.64.0808141209170.24903@digraph.polyomino.org.uk>
2008/8/14 Joseph S. Myers <joseph@codesourcery.com>:
> On Thu, 14 Aug 2008, Manuel López-Ibáñez wrote:
>
>> You can see many examples of the caret output by configuring with
>> --enable-caret-diagnostics, then reverting the changes to
>> gcc/testsuite/lib/gcc.exp and running the testsuite. Check the output
>> in the gcc.log and g++.log files.
>
> It's clear it should be controlled by a -Wcaret (or similar) option rather
> than a configure time option; the choice of style is a matter of user
> preference.
>
It is controlled by -fdiagnostics-show-caret. See the diff for gcc/opts.c.
The configure options are meant to enable/disable all code related to
caret printing in a similar way as it was done with mapped locations.
This was requested the first time I sent this patch because it was
considered too experimental to have it even with
-fno-diagnostics-show-caret as the default.
Cheers,
Manuel.