[LiveDebugValues] Close range for previous variable's location when adding newly...
authorNikola Prica <nikola.prica@rt-rk.com>
Mon, 3 Jun 2019 09:48:29 +0000 (09:48 +0000)
committerNikola Prica <nikola.prica@rt-rk.com>
Mon, 3 Jun 2019 09:48:29 +0000 (09:48 +0000)
commit2d0106a110410174ae1d1ba394cc58ab127a5949
tree53f9aa5022edf34b56c81d2de7606d171409bd12
parent0aa374a3062eca4cfe61083ee0671b6db6201147
[LiveDebugValues] Close range for previous variable's location when adding newly deduced location

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.

Reviewers: aprantl, jmorse, wolfgangp, dstenb

Reviewed By: aprantl

Subscribers: probinson, asowda, ivanbaev, petarj, djtodoro

Tags: #debug-info

Differential Revision: https://reviews.llvm.org/D62196

llvm-svn: 362373
llvm/lib/CodeGen/LiveDebugValues.cpp
llvm/test/DebugInfo/X86/fission-ranges.ll