From: Joe Buck <Joe.Buck@synopsys.COM>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
gcc Mailing List <gcc@gcc.gnu.org>
Subject: Re: Updated GCC vs Clang diagnostics
Date: Fri, 13 Apr 2012 01:40:00 -0000 [thread overview]
Message-ID: <20120413014027.GA18116@synopsys.com> (raw)
In-Reply-To: <CAESRpQDEp1AEugoCqZV=TCf7unKXKot1HhMaXwm9-hHgVN=S5A@mail.gmail.com>
On Fri, Apr 13, 2012 at 12:42:19AM +0200, Manuel López-Ibáñez wrote:
> I would like to have color output. And since nobody is paying me to do
> this work, I'd rather work on what I would like to have. The question
> is whether this is something that GCC wants to have.
>
> If the answer is NO, that is fine, I will have more free time.
I'm not interested in color output, and would turn it off if it were
implemented (the escape sequences would just mess things up when capturing
compiler output in log files).
Clang is much smarter about identifying what the user probably meant when
the issue is a typo, or "." instead of "->" or vice versa. Getting GCC to
do at least as well in this area is a much better use of developers' time
than presenting a cascade of unintelligible messages resulting from
template expansion in full color.
That said, you're free to work on what interests you.
next prev parent reply other threads:[~2012-04-13 1:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:50 Manuel López-Ibáñez
2012-04-12 21:54 ` Gabriel Dos Reis
2012-04-12 22:05 ` Manuel López-Ibáñez
2012-04-12 22:18 ` Lawrence Crowl
2012-04-13 5:12 ` Ian Lance Taylor
2012-04-13 5:58 ` Gabriel Dos Reis
2012-04-13 6:03 ` Jakub Jelinek
2012-04-13 6:07 ` Gabriel Dos Reis
2012-04-13 8:41 ` Manuel López-Ibáñez
2012-04-13 8:47 ` Gabriel Dos Reis
2012-04-13 9:00 ` Manuel López-Ibáñez
2012-04-13 9:09 ` Gabriel Dos Reis
2012-04-13 14:23 ` Jakub Jelinek
2012-04-13 15:23 ` Gabriel Dos Reis
2012-04-13 15:30 ` NightStrike
2012-04-13 15:36 ` Gabriel Dos Reis
2012-04-13 15:41 ` NightStrike
2012-04-13 15:53 ` Gabriel Dos Reis
2012-04-13 15:59 ` NightStrike
2012-04-13 16:02 ` Gabriel Dos Reis
2012-04-13 20:59 ` Lawrence Crowl
2012-04-14 6:58 ` Marc Glisse
2012-04-12 22:18 ` Gabriel Dos Reis
2012-04-12 22:43 ` Manuel López-Ibáñez
2012-04-13 1:40 ` Joe Buck [this message]
2012-04-13 2:27 ` Manuel López-Ibáñez
2012-04-13 3:37 ` Gabriel Dos Reis
2012-04-13 8:27 ` Manuel López-Ibáñez
2012-04-13 8:41 ` Gabriel Dos Reis
2012-04-13 9:08 ` Jonathan Wakely
2012-04-13 8:59 ` Jonathan Wakely
2012-04-13 9:04 ` Gabriel Dos Reis
2012-04-13 10:54 ` Manuel López-Ibáñez
2012-04-13 11:36 ` Richard Guenther
2012-04-13 13:40 ` Gabriel Dos Reis
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=20120413014027.GA18116@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=jwakely.gcc@gmail.com \
--cc=lopezibanez@gmail.com \
/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).