On Jun  8, 2009, Joe Buck <joe.b...@synopsys.com> wrote:

> I haven't kept careful track, but at one point you were talking about
> inhibiting some optimizations because they made it harder to keep the
> debug information precise.  Is this no longer an issue?

No, it never was, it must have been some misunderstanding.  I've never
planned on inhibiting any optimizations whatsoever as part of VTA.  The
plan has always been to represent the result of optimizations, not to
modify optimizers.

I suppose there may have been some confusion because of the patch to do
less SSA coalescing to try to improve debug info, long before VTA even
started.  This issue came up again after VTA development was underway,
when it became clear that we could coalesce more, rather than less, and
still get correct and complete debug info.

It is the current trunk code that throttles optimization for better
debug information.  VTA doesn't need that.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

Reply via email to