This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [trunk<-vta] Re: [vtab] Permit coalescing of user variables


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]