llvm-6502/test/DebugInfo
Dale Johannesen 5ed17ae92a Generate DEBUG_VALUE comments on x86. The (limited)
dbg.declare's we currently generate go through both
register allocators without perturbing the results.



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@94480 91177308-0d34-0410-b5e6-96231b3b80d8
2010-01-26 00:09:58 +00:00
..
2009-01-15-dbg_declare.ll
2009-01-15-member.ll
2009-02-27-licm.ll
2009-03-03-cheapdse.ll
2009-03-03-deadstore.ll
2009-03-03-store-to-load-forward.ll
2009-03-05-gvn.ll
2009-10-08-DebugInfo-NullGlobalVariable.ll
2009-10-16-Phi.ll
2009-10-16-Scope.ll Improve llvm.dbg.declare intrinsic by referring directly to the storage in its first argument, via function-local metadata (instead of via a bitcast). 2010-01-15 19:04:09 +00:00
2009-11-03-InsertExtractValue.ll
2009-11-05-DeadGlobalVariable.ll
2009-11-06-InvalidDerivedType.ll
2009-11-06-NamelessGlobalVariable.ll
2009-11-10-CurrentFn.ll
2009-11-10-ParentScope.ll
2010-01-05-DbgScope.ll If a scope has only one instruction then first instruction is also the last instruction. 2010-01-05 16:59:17 +00:00
2010-01-18-DbgValue.ll Generate DEBUG_VALUE comments on x86. The (limited) 2010-01-26 00:09:58 +00:00
2010-01-19-DbgScope.ll If a instruction belongs to another function (and not current function) as per debug info attached with the instruction then ignore the dangling lexical scope of this instruction. Such scopes are unreachable. 2010-01-20 02:05:23 +00:00
deaddebuglabel.ll
dg.exp
funccall.ll
globalGetElementPtr.ll
printdbginfo2.ll Improve llvm.dbg.declare intrinsic by referring directly to the storage in its first argument, via function-local metadata (instead of via a bitcast). 2010-01-15 19:04:09 +00:00