search for: reinvigoraetd

...the final DWARF to omit gc'd functions; it's no problem at all to use a tombstone value in .debug_addr IMO. But the tombstone values are Alexey's underlying issue (this ongoing design discussion for over a year now) & /sort/ of mine too recently (which, unfortunately, is what's reinvigoraetd this discussion - would've been nice if I/we/someone had identified this sooner & could've helped Alexey in a more timely manner): Alexey is dealing with a platform where 0 is a valid address so the lld/gold strategy of resolving relocations to dead code to "0+addend" creates...

...9;s no > > problem at all to use a tombstone value in .debug_addr IMO. > > > > But the tombstone values are Alexey's underlying issue (this ongoing > > design discussion for over a year now) & /sort/ of mine too recently > > (which, unfortunately, is what's reinvigoraetd this discussion - > > would've been nice if I/we/someone had identified this sooner & > > could've helped Alexey in a more timely manner): Alexey is dealing > > with a platform where 0 is a valid address so the lld/gold strategy of > > resolving relocations to de...

On Wed, Jun 3, 2020 at 6:34 AM Robinson, Paul <paul.robinson at sony.com> wrote: > > DWARF was designed in an era when COMDAT and ICF were not a thing, or at least not common, certainly not when talking about function code. The overhead of a unit occurred only once per translation unit, so that expense was reasonably amortized. > > > > Splitting functions into their own