diff options
| author | David Blaikie <dblaikie@gmail.com> | 2018-12-18 01:06:09 +0000 |
|---|---|---|
| committer | David Blaikie <dblaikie@gmail.com> | 2018-12-18 01:06:09 +0000 |
| commit | c4e08feb002ffc32d0f37505134c4eddb1a784f7 (patch) | |
| tree | 2a0b2851aa8132c1de878d99db28ab91dad0144a /llvm/test/Transforms/ThinLTOBitcodeWriter | |
| parent | 48a28c166518e238bb7c7b305f1473e75bc5ea7d (diff) | |
| download | bcm5719-llvm-c4e08feb002ffc32d0f37505134c4eddb1a784f7.tar.gz bcm5719-llvm-c4e08feb002ffc32d0f37505134c4eddb1a784f7.zip | |
Recommit r348806: DebugInfo: Use symbol difference for CU length to simplify assembly reading/editing
Mucking about simplifying a test case ( https://reviews.llvm.org/D55261 ) I stumbled across something I've hit before - that LLVM's (GCC's does too, FWIW) assembly output includes a hardcode length for a DWARF unit in its header. Instead we could emit a label difference - making the assembly easier to read/edit (though potentially at a slight (I haven't tried to observe it) performance cost of delaying/sinking the length computation into the MC layer).
Fix: Predicated all the changes (including creating the labels, even if they aren't used/needed) behind the NVPTX useSectionsAsReferences, avoiding emitting labels in NVPTX where ptxas can't parse them.
Reviewers: JDevlieghere, probinson, ABataev
Differential Revision: https://reviews.llvm.org/D55281
llvm-svn: 349430
Diffstat (limited to 'llvm/test/Transforms/ThinLTOBitcodeWriter')
0 files changed, 0 insertions, 0 deletions
