aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineBasicBlock.cpp
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2020-04-13 16:15:37 -0700
committerVedant Kumar <vsk@apple.com>2020-04-22 17:03:39 -0700
commit2a5675f11d3bc803a245c0e2a3b47491c8f8a065 (patch)
treec23de1280f407f61fc4960e858ea272036114971 /llvm/lib/CodeGen/MachineBasicBlock.cpp
parentb424b0bf731d1fb338180553a86f912746f640ad (diff)
downloadllvm-2a5675f11d3bc803a245c0e2a3b47491c8f8a065.zip
llvm-2a5675f11d3bc803a245c0e2a3b47491c8f8a065.tar.gz
llvm-2a5675f11d3bc803a245c0e2a3b47491c8f8a065.tar.bz2
[MachineDebugify] Insert synthetic DBG_VALUE instructions
Summary: Teach MachineDebugify how to insert DBG_VALUE instructions. This can help find bugs causing CodeGen differences when debug info is present. DBG_VALUE instructions are only emitted when -debugify-level is set to locations+variables. There is essentially no attempt made to match up DBG_VALUE register operands with the local variables they ought to correspond to. I'm not sure how to improve the situation. In some cases (MachineMemOperand?) it's possible to find the IR instruction a MachineInstr corresponds to, but in general this seems to call for "undoing" the work done by ISel. Reviewers: dsanders, aprantl Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D78135
Diffstat (limited to 'llvm/lib/CodeGen/MachineBasicBlock.cpp')
0 files changed, 0 insertions, 0 deletions