summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
diff options
context:
space:
mode:
authorAdrian Prantl <aprantl@apple.com>2015-05-21 20:37:30 +0000
committerAdrian Prantl <aprantl@apple.com>2015-05-21 20:37:30 +0000
commit1f599f9f653c92f38b9d3784a2dfd8a118942650 (patch)
tree9ca74e0fcc1a76da83a377182b228003114a4382 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
parentbe81cf570e9dcd5c89ee5029b6539b6e8203841e (diff)
downloadbcm5719-llvm-1f599f9f653c92f38b9d3784a2dfd8a118942650.tar.gz
bcm5719-llvm-1f599f9f653c92f38b9d3784a2dfd8a118942650.zip
IR / debug info: Add a DWOId field to DICompileUnit,
so DWARF skeleton CUs can be expression in IR. A skeleton CU is a (typically empty) DW_TAG_compile_unit that has a DW_AT_(GNU)_dwo_name and a DW_AT_(GNU)_dwo_id attribute. It is used to refer to external debug info. This is a prerequisite for clang module debugging as discussed in http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-November/040076.html. In order to refer to external types stored in split DWARF (dwo) objects, such as clang modules, we need to emit skeleton CUs, which identify the dwarf object (i.e., the clang module) by filename (the SplitDebugFilename) and a hash value, the dwo_id. This patch only contains the IR changes. The idea is that a CUs with a non-zero dwo_id field will be emitted together with a DW_AT_GNU_dwo_name and DW_AT_GNU_dwo_id attribute. http://reviews.llvm.org/D9488 rdar://problem/20091852 llvm-svn: 237949
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud