From: "Gabriel Dos Reis" <gdr@integrable-solutions.net>
To: "Aldy Hernandez" <aldyh@redhat.com>
Cc: "Manuel L?pez-Ib??ez" <lopezibanez@gmail.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
"Tom Tromey" <tromey@redhat.com>,
dberlin@dberlin.org, jakub@redhat.com, gcc@gcc.gnu.org,
"Chris Lattner" <clattner@apple.com>,
"Gcc Patch List" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions)
Date: Sat, 16 Aug 2008 07:45:00 -0000 [thread overview]
Message-ID: <206fcf960808152343o4c8777d8w2271300ceac532fb@mail.gmail.com> (raw)
In-Reply-To: <20080814171413.GA4460@redhat.com>
On Thu, Aug 14, 2008 at 12:14 PM, Aldy Hernandez <aldyh@redhat.com> wrote:
>> * In the near future, make -fdiagnostics-show-caret the default at
>> least while in experimental mode or at least during stages1 and 2.
>> When making a release -fno-diagnostics-show-caret would be the
>> default. Do this through a configure option that sets the default.
>>
>> * In the far away future, review the defaults and get rid of the
>> configure option.
>
> To be honest, I don't mind either way. Either your option or Joseph's
> is fine. I am however interested in getting the caret diagnostics in,
> and then I can work on location information that will benefit everyone.
I'm in favor of getting -fdiagnostics-show-caret=no by default in this release,
and enable people like you to get useful stuff done. That gives us time
to iron out outstanding bugs for the next release (and making it the default).
-- Gaby
>
> Aldy
>
next prev parent reply other threads:[~2008-08-16 6:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 12:12 Manuel López-Ibáñez
2008-08-14 12:41 ` Joseph S. Myers
2008-08-14 12:57 ` Manuel López-Ibáñez
2008-08-14 13:54 ` Joseph S. Myers
2008-08-14 14:07 ` Manuel López-Ibáñez
2008-08-14 14:41 ` Joseph S. Myers
2008-08-14 15:03 ` Manuel López-Ibáñez
2008-08-14 15:08 ` [PATCH] caret diagnostics Robert Dewar
2008-08-14 15:22 ` Joseph S. Myers
2008-08-14 15:43 ` Robert Dewar
2008-08-14 15:48 ` Manuel López-Ibáñez
2008-08-14 16:06 ` Robert Dewar
2008-08-14 16:18 ` Manuel López-Ibáñez
2008-08-14 16:18 ` Joseph S. Myers
2008-08-14 17:22 ` Chris Lattner
2008-08-16 13:30 ` Paolo Bonzini
2008-08-16 17:19 ` Joseph S. Myers
2008-08-16 18:59 ` Paolo Bonzini
2008-08-14 18:49 ` Mark Mitchell
2008-08-14 19:10 ` Manuel López-Ibáñez
2008-08-14 19:28 ` Mark Mitchell
2008-08-14 15:17 ` [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions) Joseph S. Myers
2008-08-14 17:18 ` [PATCH] caret diagnostics Tom Tromey
2008-08-14 17:21 ` Ralf Wildenhues
2008-08-14 17:34 ` Joseph S. Myers
2008-08-14 18:20 ` Tom Tromey
2008-08-14 18:34 ` Ralf Wildenhues
2008-08-14 19:02 ` Robert Dewar
2008-08-14 17:33 ` Joseph S. Myers
2008-08-14 17:51 ` Joseph S. Myers
2008-08-14 18:52 ` Mark Mitchell
2008-08-16 10:09 ` Gabriel Dos Reis
2008-08-16 13:00 ` Robert Dewar
2008-08-14 15:18 ` [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions) Aldy Hernandez
2008-08-14 15:29 ` Manuel López-Ibáñez
2008-08-14 17:23 ` Aldy Hernandez
2008-08-16 7:45 ` Gabriel Dos Reis [this message]
2008-08-16 13:12 ` [PATCH] caret diagnostics Robert Dewar
2008-08-16 7:44 ` [PATCH] caret diagnostics (was: broken FE diagnostics wrt complex expressions) Gabriel Dos Reis
2008-08-14 18:00 ` [PATCH] caret diagnostics Tom Tromey
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=206fcf960808152343o4c8777d8w2271300ceac532fb@mail.gmail.com \
--to=gdr@integrable-solutions.net \
--cc=aldyh@redhat.com \
--cc=clattner@apple.com \
--cc=dberlin@dberlin.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=lopezibanez@gmail.com \
--cc=tromey@redhat.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).