diff options
| author | Jeremy Morse <jeremy.morse@sony.com> | 2021-11-29 22:06:46 +0000 |
|---|---|---|
| committer | Jeremy Morse <jeremy.morse@sony.com> | 2021-11-29 22:24:19 +0000 |
| commit | a20987adf4f80e2657eb3032a5a91e13f58106a0 (patch) | |
| tree | e91e25b2ac439bcedd8e8acac69cfaf63a7d16d3 /lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h | |
| parent | 829b62adf5db189843b9a9ce626dfef97f76059f (diff) | |
| download | llvm-a20987adf4f80e2657eb3032a5a91e13f58106a0.zip llvm-a20987adf4f80e2657eb3032a5a91e13f58106a0.tar.gz llvm-a20987adf4f80e2657eb3032a5a91e13f58106a0.tar.bz2 | |
[DebugInfo][InstrRef] Add indirection from dbg.declare in SelectionDAG
Usually dbg.declares get translated into either entries in an MF
side-table, or a DBG_VALUE on entry to the function with IsIndirect set
(including in instruction referencing mode). Much rarer is a dbg.declare
attached to a non-argument value, such as in the test added in this patch
where there's a variable-length-array. Such dbg.declares become SDDbgValue
nodes with InIndirect=true.
As it happens, we weren't correctly emitting DBG_INSTR_REFs with the
additional indirection. This patch adds the extra indirection, encoded as
adding an additional DW_OP_deref to the expression.
Differential Revision: https://reviews.llvm.org/D114440
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/SWIGPythonBridge.h')
0 files changed, 0 insertions, 0 deletions