summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorDavid Blaikie <dblaikie@gmail.com>2014-03-25 01:44:02 +0000
committerDavid Blaikie <dblaikie@gmail.com>2014-03-25 01:44:02 +0000
commit9c550ac4e79b20a4e78fc99ec6b57bc62cf502b0 (patch)
tree0024de59c32f3d80596332f3227b800d6adffe74 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent2d33d6a4c29fcda36cc13591c9a007498934c961 (diff)
downloadbcm5719-llvm-9c550ac4e79b20a4e78fc99ec6b57bc62cf502b0.tar.gz
bcm5719-llvm-9c550ac4e79b20a4e78fc99ec6b57bc62cf502b0.zip
DebugInfo: Support debug_loc under fission
Implement debug_loc.dwo, as well as llvm-dwarfdump support for dumping this section. Outlined in the DWARF5 spec and http://gcc.gnu.org/wiki/DebugFission the debug_loc.dwo section has more variation than the standard debug_loc, allowing 3 different forms of entry (plus the end of list entry). GCC seems to, and Clang certainly, only use one form, so I've just implemented dumping support for that for now. It wasn't immediately obvious that there was a good refactoring to share the implementation of dumping support between debug_loc and debug_loc.dwo, so they're separate for now - ideas welcome or I may come back to it at some point. As per a comment in the code, we could choose different forms that may reduce the number of debug_addr entries we emit, but that will require further study. llvm-svn: 204697
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud