public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
	gcc Mailing List <gcc@gcc.gnu.org>
Subject: Re: Updated GCC vs Clang diagnostics
Date: Thu, 12 Apr 2012 22:18:00 -0000	[thread overview]
Message-ID: <CAAiZkiBgKPVqM4rxJSf7EtmQY=b2LfAYCJASyvN0yTwDm16sjw@mail.gmail.com> (raw)
In-Reply-To: <CAESRpQBAjCNmN0bQ8Xp5sg6aVSLvPJ=W2tJcWSK2PokXiRrCaQ@mail.gmail.com>

On Thu, Apr 12, 2012 at 5:05 PM, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
> On 12 April 2012 23:54, Gabriel Dos Reis <gdr@integrable-solutions.net> wrote:
>> On Thu, Apr 12, 2012 at 4:49 PM, Manuel López-Ibáñez
>> <lopezibanez@gmail.com> wrote:
>>> Hi Jonathan,
>>>[....]
>>> Of course, the major question is: Are the decision makers in GCC
>>> interested on any of this?
>>>
>>> Would some reviewer reject patches implementing them?
>>
>> I suspect decisions will be based on the implementations themselves.
>>
>
> So given your ideal implementation, if the user-visible result was
> exactly like the one in Clang, will you be happy with any of the three
> things: ranges, color and fix-it hints?

My ideal isn't to replicate Clang :-)

I would like us to set a standard that Clang would have to follow :-)
There are several things that need to be considered.
The three items above are choices in the toolset.  Ideally, I would
like to have a mechanism where the output could be configured
(through a command line switch, etc) that allows for example IDEs
(not just GNU Emacs) to hook into databases of advices, standard
definitions, etc.  Even for our own testsuites, this might be useful
instead of the current one-dimensional char sequence
oriented diagnostic testing.


>
> Or you will prefer to never have some of them or to have them disabled
> by default?
>
> Or to have them, but in a different (user-visible) manner?

I suspect to some degree this is closer to I would like to see, but again,
I would prefer to make a judgment based on an implementation.

-- Gaby

  parent reply	other threads:[~2012-04-12 22:18 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 [this message]
2012-04-12 22:43       ` Manuel López-Ibáñez
2012-04-13  1:40         ` Joe Buck
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='CAAiZkiBgKPVqM4rxJSf7EtmQY=b2LfAYCJASyvN0yTwDm16sjw@mail.gmail.com' \
    --to=gdr@integrable-solutions.net \
    --cc=gcc@gcc.gnu.org \
    --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).