[DWARF parser] Respect address ranges specified in compile unit DIE.

When address ranges for compile unit are specified in compile unit DIE
itself, there is no need to collect ranges from children subprogram DIEs.

This change speeds up llvm-symbolizer on Clang-produced binaries with
full debug info. For instance, symbolizing a first address in a 1Gb binary
is now 2x faster (1s vs. 2s).

llvm-svn: 206641
This commit is contained in:
Alexey Samsonov 2014-04-18 20:30:27 +00:00
parent 25463f1577
commit 84e2423d34
1 changed files with 7 additions and 0 deletions

View File

@ -299,6 +299,13 @@ void DWARFUnit::clearDIEs(bool KeepCUDie) {
} }
void DWARFUnit::collectAddressRanges(DWARFAddressRangesVector &CURanges) { void DWARFUnit::collectAddressRanges(DWARFAddressRangesVector &CURanges) {
// First, check if CU DIE describes address ranges for the unit.
const auto &CUDIERanges = getCompileUnitDIE()->getAddressRanges(this);
if (!CUDIERanges.empty()) {
CURanges.insert(CURanges.end(), CUDIERanges.begin(), CUDIERanges.end());
return;
}
// This function is usually called if there in no .debug_aranges section // This function is usually called if there in no .debug_aranges section
// in order to produce a compile unit level set of address ranges that // in order to produce a compile unit level set of address ranges that
// is accurate. If the DIEs weren't parsed, then we don't want all dies for // is accurate. If the DIEs weren't parsed, then we don't want all dies for