search for: debug_adr

Displaying 4 results from an estimated 4 matches for "debug_adr".

Did you mean: debug_addr
2020 Jun 03
2
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
...a DWARF-agnostic linker (or even with a DWARF aware one, but in an efficient amount of time/space where it's not only usable for small programs, or for linking when you're shipping a final production binary, etc) & as always, not sure how any of this would work for Split DWARF - just a debug_adr section that has some addresses that point to discardable functions... if we want those addresses themselves to be discardable (so we don't have to use a tombstone value inserted by the linker) then they'd need to be in separate debug_addr contributions with headers, etc - the overhead just...
2020 Jun 04
4
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
...5 new sections per function would be probably a significantly larger growth than anything else I'm aware of, but I haven't run the numbers by any means. Thanks again for the write up! - Dave > > & as always, not sure how any of this would work for Split DWARF - > > just a debug_adr section that has some addresses that point to > > discardable functions... if we want those addresses themselves to be > > discardable (so we don't have to use a tombstone value inserted by the > > linker) then they'd need to be in separate debug_addr contributions > &g...
2020 Jun 09
2
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
...vmtg/2016-11/#talk22) > > > > > Thanks again for the write up! > > NP, it was fun to trot out this stuff. > --paulr > > > > > - Dave > > > > > > & as always, not sure how any of this would work for Split DWARF - > > > > just a debug_adr section that has some addresses that point to > > > > discardable functions... if we want those addresses themselves to be > > > > discardable (so we don't have to use a tombstone value inserted by the > > > > linker) then they'd need to be in separate de...
2020 Jun 03
5
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
It makes me sad that the linker (via a library or otherwise) has to be "DWARF-aware" to be able to effectively handle --gc-sections, COMDATs, --icf etc for debug info, without leaving large blocks of data kicking around. The patching to -1 (or equivalent) is probably a good lightweight solution (though I'd love it if it could be done based on section type in the future rather than