https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26061
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |egallager at gcc dot gnu.org
--- Comment #21 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Kevin André from comment #20)
> (In reply to comment #19)
>
> > I really don't want to make it default off as it's really useful. I hope to
> > fix
> > the patch and make it default on for gcc 4.4 at least.
>
> I agree. What's the status for getting it into 4.4?
>
> People complain that changing GCC's output will break tools that parse that
> output. I can understand why they're complaining, but IMHO this reveals a
> more fundamental problem. The current diagnostic output tries to serve two
> purposes: being readable for humans and being parseable by tools. And I
> think those two should be separated. Why not have the default output be
> human-friendly, and introduce a separate option, say
> "-fparseable-diagnostics" to switch to an easily parseable output format?
clang has had an error and warning count for a really long time now and tools
work with it. gcc 7 added -fdiagnostics-parseable-fixits but fixits are only
part of diagnostics.
