HomePhabricator

DebugInfo: Reduce long-distance dependence on what will/won't emit a debug_addr…

Authored by dblaikie on May 17 2020, 12:17 PM.

Description

DebugInfo: Reduce long-distance dependence on what will/won't emit a debug_addr section

This is a no-op/NFC at the moment & generally makes the code /somewhat/
cleaner/less reliant on assumptions about what will produce a debug_addr
section.

It's still a bit "spooky action at a distance" - the add ranges code
pre-emptively inserts addresses into the address pool it knows will
eventually be used by the range emission code (or low/high pc).

The 'ideal' would be either to actually compute the addresses needed for
range (& loc) emission earlier - which would mean decanonicalizing the
range/loc representation earlier to account for whether it was going to
use addrx encodings or not (which would be unfortunate, but could be
refactored to be relatively unobtrusive).

Alternatively, emitting the range/loc sections earlier would cause them
to request the needed addresses sooner - but then you endup having to
split finalizeModuleInfo because some things need to be handled there
before the ranges/locs are emitted, I think...

Details

Committed
dblaikieMay 17 2020, 12:45 PM
Parents
rG39beeeff205c: [LVI] Don't use dominator tree in isValidAssumeForContext()
Branches
Unknown
Tags
Unknown