diff options
| author | Adrian Prantl <aprantl@apple.com> | 2015-12-21 20:03:00 +0000 |
|---|---|---|
| committer | Adrian Prantl <aprantl@apple.com> | 2015-12-21 20:03:00 +0000 |
| commit | ce8581389b203f67ae0d5d8227bb8662879fe9ce (patch) | |
| tree | 84ed925c942b9052f5f0a9f5363cbdc9b8135699 /lldb/packages/Python/lldbsuite/test/python_api/interpreter/TestCommandInterpreterAPI.py | |
| parent | 6b4454101502d3f5488895f85cc9a813719b703e (diff) | |
| download | bcm5719-llvm-ce8581389b203f67ae0d5d8227bb8662879fe9ce.tar.gz bcm5719-llvm-ce8581389b203f67ae0d5d8227bb8662879fe9ce.zip | |
Fix PR24563 (LiveDebugVariables unconditionally propagates all DBG_VALUEs)
LiveDebugVariables unconditionally propagates all DBG_VALUE down the
dominator tree, which happens to work fine if there already is another
DBG_VALUE or the DBG_VALUE happends to describe a single-assignment vreg
but is otherwise wrong if the DBG_VALUE is coming from only one of the
predecessors.
In r255759 we introduced a proper data flow analysis scheduled after
LiveDebugVariables that correctly propagates DBG_VALUEs across basic block
boundaries. With the new pass in place, the incorrect propagation in
LiveDebugVariables can be retired witout loosing any of the benefits
where LiveDebugVariables happened to do the right thing.
llvm-svn: 256188
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter/TestCommandInterpreterAPI.py')
0 files changed, 0 insertions, 0 deletions
