[PATCH] D85018: [WIP][POC][DebugInfo] Support for DW_AT_start_scope for scoped variables
David Blaikie via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Aug 3 12:59:09 PDT 2020
dblaikie added a comment.
https://github.com/google/bloaty might be a clearer way to compare the section sizes before/after. Though also comparing variable statistics (llvm-dwarfdump --statistics) might be helpful (though I'm guessing --statistics doesn't understand start-scope yet).
I assume in the previous discussion we discussed the complexities of what start_scope means for a variable without a contiguous address range? What was the answer to that? (if a variable/its enclosing scope has multiple discontiguous address ranges, what's the meaning of the start scope? Which ranges are/aren't in scope?)
I'll probably punt most of this review to @aprantl & co who have more context for variable location tracking.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D85018/new/
https://reviews.llvm.org/D85018
More information about the llvm-commits
mailing list