summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/namespace/ns3.cpp
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2018-06-20 16:50:25 +0000
committerVedant Kumar <vsk@apple.com>2018-06-20 16:50:25 +0000
commit6fa24b0b7fb755114ca3ac50c6617e917222a893 (patch)
tree19d4fef37b764d2e5087f10c2582216744a03cc3 /lldb/packages/Python/lldbsuite/test/lang/cpp/namespace/ns3.cpp
parent37fbb92652e81aa81554e042ea4f87baf754f5a6 (diff)
downloadbcm5719-llvm-6fa24b0b7fb755114ca3ac50c6617e917222a893.tar.gz
bcm5719-llvm-6fa24b0b7fb755114ca3ac50c6617e917222a893.zip
[Local] Add a utility to insert replacement dbg.values, NFC
The purpose of this utility is to make it easier for optimizations to insert replacement dbg.values for instructions they are deleting. This is useful in situations where salvageDebugInfo is inapplicable, say, because the new dbg.value cannot refer to an operand of the dying value. The utility is called insertReplacementDbgValues. It assumes that the instruction 'From' is going to be deleted, and inserts replacement dbg.values for each debug user of 'From'. The newly-inserted dbg.values refer to 'To' instead of 'From'. Each replacement dbg.value has the same location and variable as the debug user it replaces, has a DIExpression determined by the result of 'RewriteExpr' applied to an old debug user of 'From', and is placed before 'InsertBefore'. This should simplify future patches, like D48331. llvm-svn: 335144
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/namespace/ns3.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud