public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.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 01:13:00 -0000	[thread overview]
Message-ID: <4A25CE20.3020102@redhat.com> (raw)
In-Reply-To: <or7hzumhy8.fsf@free.oliva.athome.lsd.ic.unicamp.br>

Alexandre Oliva wrote:
> On Jun  2, 2009, Richard Guenther <richard.guenther@gmail.com> wrote:
>
>   
>> On Mon, Jun 1, 2009 at 9:23 PM, Alexandre Oliva <aoliva@redhat.com> wrote:
>>     
>>> On Jun  1, 2009, Andrew MacLeod <amacleod@redhat.com> wrote:
>>>
>>>       
>>>> Is there a reason we can't leave the current default behaviour the way
>>>> it is, and have the VTA code simple enable the "best" choices for it.
>>>>         
>>> We don't want options used to control generation of debug information
>>> (say the option that enables or disables VTA) to change the generated
>>> code (say enable or disable coalescing), do we?  This would be as bad as
>>> -g/-g0 generating different code.
>>>
>>> Personally, I don't see the point of the options either, but I don't see
>>>       
>
>   
>> Me neither, and I am opposed to adding it.
>>     
>
> I'm missing your rationale here as well.  It would help if you at least
> voiced what you suggest we do instead.
>
>   
I think we are simply proposing that when VTA code is added and enabled, 
the default behaviour is then changed such that we do this coalescing.  
Until then it stays with the current tradeoffs. no options required...

At least that's all I meant.

Andrew

  reply	other threads:[~2009-06-03  1:13 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 [this message]
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
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=4A25CE20.3020102@redhat.com \
    --to=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).