[Dwarf-Discuss] Does gcc optimization impacts retrieving Dwarf information?
M. Mohan Kumar
Wed Nov 18 12:49:01 GMT 2009
On 05/29/2009 03:11 PM, Mark Wielaard wrote:
> (Resent, now actually subscribed to the list from the correct address)
> On Fri, 2009-05-29 at 14:28 +0530, M. Mohan Kumar wrote:
>>>> That's all true in the abstract, but modern gcc has been known to
>>>> abscond with variable location data even for values that are
>>>> live/recomputable. This is the main reason why the VTA (and
>>>> debuglocus and other) gcc projects are under way -- to represent the
>>>> maximum possible conceptual data, despite -O2 etc.
>> Frank, Will VTA/debuglocus have the dwarf compatibility (i.e. it does not
>> need modification to existing applications using libdwarf APIs)?
>> When can we expect this features (VTA/debuglocus) integrated into mainline
> Yes, it will output (hopefully better/more complete) dwarf information.
> I don't know the schedule details of when this will land in gcc
> mainline. But the ideas behind how to improve the tracking of debug
> locations for variables in gcc can be found in this paper from Alexandre
> Olivia: http://www.lsd.ic.unicamp.br/~oliva/papers/vta/slides.pdf
> And on this GCC wiki page:
In one of the dwarf mail threads it is mentioned that VTA is ready for
integration into gcc, but its waiting for the acceptance from the
Are VTA patches part of mainline gcc now? If not, where could we get the
M. Mohan Kumar.
> DebugLocus is an alternative idea on an implementation to improve
> tracking debug information from Andrew MacLeod described here:
> Dwarf-Discuss mailing list
> Dwarf-Discuss at lists.dwarfstd.org
More information about the Dwarf-discuss