summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py
diff options
context:
space:
mode:
authorJeremy Morse <jeremy.morse.llvm@gmail.com>2019-08-19 09:02:18 +0000
committerJeremy Morse <jeremy.morse.llvm@gmail.com>2019-08-19 09:02:18 +0000
commitb58ba8aae710cba925e3c59accde6695c1d40aa3 (patch)
tree7dc6582e727b52a837bf9aa728650abf37a625f1 /lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py
parentb8639f5c0fd82d4c29eb55590e1dfaf0a54dbb94 (diff)
downloadbcm5719-llvm-b58ba8aae710cba925e3c59accde6695c1d40aa3.tar.gz
bcm5719-llvm-b58ba8aae710cba925e3c59accde6695c1d40aa3.zip
[DebugInfo] Test for variable range un-coalescing
LiveDebugVariables can coalesce ranges of variable locations across multiple basic blocks. However when it recreates DBG_VALUE instructions, it has to recreate one DBG_VALUE per block, otherwise it doesn't represent the pre-regalloc layout and variable assignments can go missing. This feature works -- however while mucking around with LiveDebugVariables, I commented the relevant code it out and no tests failed. Thus, here's a test that checks LiveDebugVariables preserves DBG_VALUEs across block boundaries. Differential Revision: https://reviews.llvm.org/D66347 llvm-svn: 369243
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud