From: Daniel Jacobowitz <drow@false.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Andrew MacLeod <amacleod@redhat.com>,
Ian Lance Taylor <iant@google.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [trunk<-vta] Re: [vtab] Permit coalescing of user variables
Date: Wed, 03 Jun 2009 19:45:00 -0000 [thread overview]
Message-ID: <20090603194539.GA20558@caradoc.them.org> (raw)
In-Reply-To: <or4ouxku02.fsf@free.oliva.athome.lsd.ic.unicamp.br>
On Wed, Jun 03, 2009 at 04:16:45PM -0300, Alexandre Oliva wrote:
> On Jun 3, 2009, Daniel Jacobowitz <drow@false.org> wrote:
>
> > On Wed, Jun 03, 2009 at 02:43:27PM -0300, Alexandre Oliva wrote:
> >> Sure enough, if VTA goes in and becomes default and can't be disabled,
> >> the options cease to make much sense. We can remove them then, when and
> >> if it happens. But since so far there's no indication that VTA is
> >> actually going in, rejecting this patch on the grounds of an unwarranted
> >> assumption comes off as very odd to me.
>
> > So, just make the switch flipped by whatever bit of GCC decides VTA is
> > enabled?
>
> And then options that control debug information start controlling
> executable code as well, and the entire universe collapses ;-P :-D
>
> More on this upthread.
I think you've misunderstood my point.
If you want ports to be able to set the default for VTA as it is
tested with them (which I'm not convinced is a good idea, anyway) then
that setting is independent of -g. That's the right place to control
coalescing.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-03 19:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 19:05 Alexandre Oliva
2007-10-02 9:15 ` Richard Guenther
2007-10-02 21:02 ` Andrew MacLeod
2007-10-03 1:11 ` Alexandre Oliva
2007-10-09 21:32 ` Alexandre Oliva
2009-06-01 7:39 ` [trunk<-vta] " Alexandre Oliva
2009-06-01 7:44 ` Alexandre Oliva
2009-06-01 16:11 ` Ian Lance Taylor
2009-06-01 17:35 ` Andrew MacLeod
2009-06-01 19:23 ` Alexandre Oliva
2009-06-02 9:54 ` Richard Guenther
2009-06-02 21:42 ` Alexandre Oliva
2009-06-03 1:13 ` Andrew MacLeod
2009-06-03 10:18 ` Richard Guenther
2009-06-03 17:43 ` Alexandre Oliva
2009-06-03 18:06 ` Daniel Jacobowitz
2009-06-03 19:17 ` Alexandre Oliva
2009-06-03 19:45 ` Daniel Jacobowitz [this message]
2009-06-03 21:42 ` Alexandre Oliva
2009-06-03 18:18 ` Richard Guenther
2009-06-03 19:15 ` Alexandre Oliva
2009-06-03 19:50 ` Richard Guenther
2009-06-03 19:53 ` Ian Lance Taylor
2009-10-13 21:27 ` Alexandre Oliva
2011-06-04 12:45 ` Alexandre Oliva
2011-06-04 13:02 ` Jakub Jelinek
2011-06-05 21:07 ` Alexandre Oliva
2011-06-06 2:42 ` Alexandre Oliva
2012-04-09 5:56 ` Alexandre Oliva
2012-06-13 8:34 ` Alexandre Oliva
2012-06-13 9:48 ` Richard Guenther
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=20090603194539.GA20558@caradoc.them.org \
--to=drow@false.org \
--cc=amacleod@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=richard.guenther@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).