Jeremy Morse 2104fd09d6 [DebugInfo] Emit undef DBG_VALUEs when SDNodes are optimised out ... This is a fix for PR39896, where dbg.value's of SDNodes that have been optimised out do not lead to "DBG_VALUE undef" instructions being created. Such undef instructions are necessary to terminate earlier variable ranges, otherwise variable values leak past the point where they're valid. The "invalidated" flag of SDDbgValue is currently being abused to mean two things: * The corresponding SDNode is now invalid * This SDDbgValue should not be emitted Of which there are several legitimate combinations of meaning: * The SDNode has been invalidated and we should emit "DBG_VALUE undef" * The SDNode has been invalidated but the debug data was salvaged, don't emit anything for this SDDbgValue * This SDDbgValue has been emitted This patch introduces distinct "Emitted" and "Invalidated" fields to the SDDbgValue class, updates users accordingly, and generates "undef" DBG_VALUEs for invalidated records. Awkwardly, there are circumstances where we emit SDDbgValue's twice, specifically DebugInfo/X86/dbg-addr-dse.ll which I've preserved. Differential Revision: https://reviews.llvm.org/D55372 llvm-svn: 348751		2018-12-10 11:20:47 +00:00
..
cu-range-hole.ll
dbg-declare-alloca.ll
dbg-value-const-byref.ll
debug-file-loc-only.ll
debug-file-loc.ll
debug-info.ll	[DebugInfo] Emit undef DBG_VALUEs when SDNodes are optimised out	2018-12-10 11:20:47 +00:00
debug-loc-offset.ll
lit.local.cfg