[PATCH] D70696: [DebugInfo] Support to emit debugInfo for extern variables
David Blaikie via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Tue Dec 3 11:57:10 PST 2019
dblaikie added a comment.
Many of the test cases could be collapsed into one file - using different variables that are used, unused, locally or globally declared, etc.
Is this new code only active for C compilations? (does clang reject requests for the bpf target when the input is C++?) I ask due to the concerns around globals used in inline functions where the inline function is unused - though C has inline functions too, so I guess the question stands: Is that a problem? What happens?
Should this be driven by a lower level of code generation - ie: is it OK to only produce debug info descriptions for variables that are referenced in the resulting LLVM IR? (compile time constants wouldn't be described then, for instance - since they won't be code generated, loaded from memory, etc)
Is there somewhere I should be reading about the design requirement for these global variable descriptions to understand the justification for them & the ramifications if there are bugs that cause them not to be emitted?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D70696/new/
https://reviews.llvm.org/D70696
More information about the cfe-commits
mailing list