mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-12-02 16:36:40 +00:00
eecdf22144
As demonstrated by the regression tests added in this patch, the following cases are valid cases: 1. A Function with no DISubprogram attached, but various debug info related to its instructions, coming, for instance, from an inlined function, also defined somewhere else in the same module; 2. ... or coming exclusively from the functions inlined and eliminated from the module entirely. The ValueMap shared between CloneFunctionInto calls within CloneModule needs to contain identity mappings for all of the DISubprogram's to prevent them from being duplicated by MapMetadata / RemapInstruction calls, this is achieved via DebugInfoFinder collecting all the DISubprogram's. However, CloneFunctionInto was missing calls into DebugInfoFinder for functions w/o DISubprogram's attached, but still referring DISubprogram's from within (case 1). This patch fixes that. The fix above, however, exposes another issue: if a module contains a DISubprogram referenced only indirectly from other debug info metadata, but not attached to any Function defined within the module (case 2), cloning such a module causes a DICompileUnit duplication: it will be moved in indirecty via a DISubprogram by DebugInfoFinder first (because of the first bug fix described above), without being self-mapped within the shared ValueMap, and then will be copied during named metadata cloning. So this patch makes sure DebugInfoFinder visits DICompileUnit's referenced from DISubprogram's as it goes w/o re-processing llvm.dbg.cu list over and over again for every function cloned, and makes sure that CloneFunctionInto self-maps DICompileUnit's referenced from the entire function, not just its own DISubprogram attached that may also be missing. The most convenient way of tesing CloneModule I found is to rely on CloneModule call from `opt -run-twice`, instead of writing tedious unit tests. That feature has a couple of properties that makes it hard to use for this purpose though: 1. CloneModule doesn't copy source filename, making `opt -run-twice` report it as a difference. 2. `opt -run-twice` does the second run on the original module, not its clone, making the result of cloning completely invisible in opt's actual output with and without `-run-twice` both, which directly contradicts `opt -run-twice`s own error message. This patch fixes this as well. Reviewed By: aprantl Reviewers: loladiro, GorNishanov, espindola, echristo, dexonsmith Subscribers: vsk, debug-info, JDevlieghere, llvm-commits Differential Revision: https://reviews.llvm.org/D45593 llvm-svn: 330069 |
||
|---|---|---|
| .. | ||
| bugpoint | ||
| bugpoint-passes | ||
| dsymutil | ||
| gold | ||
| llc | ||
| lli | ||
| llvm-ar | ||
| llvm-as | ||
| llvm-as-fuzzer | ||
| llvm-bcanalyzer | ||
| llvm-c-test | ||
| llvm-cat | ||
| llvm-cfi-verify | ||
| llvm-config | ||
| llvm-cov | ||
| llvm-cvtres | ||
| llvm-cxxdump | ||
| llvm-cxxfilt | ||
| llvm-demangle-fuzzer | ||
| llvm-diff | ||
| llvm-dis | ||
| llvm-dwarfdump | ||
| llvm-dwp | ||
| llvm-exegesis | ||
| llvm-extract | ||
| llvm-go | ||
| llvm-isel-fuzzer | ||
| llvm-jitlistener | ||
| llvm-link | ||
| llvm-lto | ||
| llvm-lto2 | ||
| llvm-mc | ||
| llvm-mc-assemble-fuzzer | ||
| llvm-mc-disassemble-fuzzer | ||
| llvm-mca | ||
| llvm-modextract | ||
| llvm-mt | ||
| llvm-nm | ||
| llvm-objcopy | ||
| llvm-objdump | ||
| llvm-opt-fuzzer | ||
| llvm-opt-report | ||
| llvm-pdbutil | ||
| llvm-profdata | ||
| llvm-rc | ||
| llvm-readobj | ||
| llvm-rtdyld | ||
| llvm-shlib | ||
| llvm-size | ||
| llvm-special-case-list-fuzzer | ||
| llvm-split | ||
| llvm-stress | ||
| llvm-strings | ||
| llvm-symbolizer | ||
| llvm-xray | ||
| lto | ||
| msbuild | ||
| obj2yaml | ||
| opt | ||
| opt-viewer | ||
| sancov | ||
| sanstats | ||
| verify-uselistorder | ||
| xcode-toolchain | ||
| yaml2obj | ||
| CMakeLists.txt | ||
| LLVMBuild.txt | ||