[PATCH] D62196: [LiveDebugValues] Close range for previous variable's location when deducing new variable's location

[Nikola Prica via Phabricator via llvm-commits]

NikolaPrica created this revision.
NikolaPrica added reviewers: llvm-commits, aprantl, jmorse, wolfgangp, dstenb.
NikolaPrica added a project: debug-info.

When LiveDebugValues deduces new variable's location from spill, restore or register copy instruction it should close old variable's location. Otherwise we can have multiple block output locations for same variable. That could lead to inserting two DBG_VALUEs for same variable to the beginning of the successor block which results to ignoring of first DBG_VALUE.

- fission-ranges.ll part which references llvm.dbg.value debuging location is changed in order to give function scope range to variables  "b" and "e".




https://reviews.llvm.org/D62196

Files:
  lib/CodeGen/LiveDebugValues.cpp
  test/DebugInfo/X86/fission-ranges.ll

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D62196.200501.patch
Type: text/x-patch
Size: 4654 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20190521/7dcb170e/attachment.bin>