Jeremy Morse 66ac86b58d [DebugInfo][DAG] Process FrameIndex dbg.values unconditionally ... A FrameIndex should be valid throughout a block regardless of what instructions get selected in that block -- therefore we shouldn't harness dbg.values that refer to FrameIndexes to an SDNode. There are numerous codegen reasons why an SDNode never appears or doesn't become a location that a DBG_VALUE can refer to. None of them actually affect the variable location. Therefore, before any other tests to encode dbg_values in a SelectionDAG, identify FrameIndex operands and encode them unattached to any SDNode. Differential Revision: https://reviews.llvm.org/D57328 llvm-svn: 352467		2019-01-29 09:40:05 +00:00
..
cu-range-hole.ll	[DEBUGINFO, NVPTX] Enable support for the debug info on NVPTX target.	2019-01-23 18:59:54 +00:00
dbg-declare-alloca.ll	[DEBUGINFO, NVPTX] Enable support for the debug info on NVPTX target.	2019-01-23 18:59:54 +00:00
dbg-value-const-byref.ll	[DebugInfo][DAG] Process FrameIndex dbg.values unconditionally	2019-01-29 09:40:05 +00:00
debug-empty.ll	[DEBUGINFO, NVPTX] Enable support for the debug info on NVPTX target.	2019-01-23 18:59:54 +00:00
debug-file-loc-only.ll	[DEBUGINFO, NVPTX] Disable emission of ',debug' option if only debug directives are allowed.	2018-12-06 16:25:35 +00:00
debug-file-loc.ll	[DEBUGINFO, NVPTX] Enable support for the debug info on NVPTX target.	2019-01-23 18:59:54 +00:00
debug-info.ll	[DebugInfo][DAG] Avoid re-ordering of DBG_VALUEs	2019-01-28 12:08:31 +00:00
debug-loc-offset.ll	[DEBUGINFO, NVPTX] Enable support for the debug info on NVPTX target.	2019-01-23 18:59:54 +00:00
lit.local.cfg	…