This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: RFC: c++ diagnostics
- From: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Mon, 5 Apr 2010 20:58:50 +0200
- Subject: Re: RFC: c++ diagnostics
- References: <20100405082033.7a9bcf81@redhat.com>
On 5 April 2010 17:20, Benjamin Kosnik <bkoz@redhat.com> wrote:
>
> Hello all!
>
> I've put up a short diagnostics comparison between gcc, icc, and
> clang. It is my plan to update this with major revisions to individual
> compilers.
Awesome!
How to contribute? patches against the html? I see there are some
examples without output. Also, it would be nicer if the page linked to
each PR in bugzilla.
On the one hand, it is strange that you use
-fdiagnostics-show-location=once without -fmessage-length= because
that doesn't have any effect. On the other hand,
-fdiagnostics-show-option will give an output more similar to the one
of clang.
> Included are most of the outstanding bugzilla requests with the
> "diagnostic" keyword. However, I am looking for help! Please send me
> code samples that frustrate, obfuscate, and annoy.
I guess most of the ones listed here:
http://clang.llvm.org/diagnostics.html
Also, posting this to kde-devel@kde.org may get some further feedback.
> I'm also looking for guidance on how to rank the priority of these
> issues. Is there some way to tell what the biggest annoyance is?
Let people vote in GCC bugzilla? Hum, perhaps not...
Cheers,
Manuel.