Torok Edwin 3324e1f491 Global variables don't have a corresponding llvm.dbg.declare, yet it is possible ... to obtain debug info about them. Introduce helpers to access debug info for global variables. Also introduce a helper that works for both local and global variables. llvm-svn: 66541		2009-03-10 13:41:26 +00:00
..
2008-10-17-C++DebugCrash.ll
2008-11-05-InlinedFuncStart.ll
2008-11-06-Mem2Reg.ll
2008-11-19-InstCombine.ll
2009-01-15-dbg_declare.ll
2009-01-15-member.ll
2009-01-15-RecordVariableCrash.ll
2009-01-28-ArrayType.ll
2009-01-29-HeaderLocation.ll
2009-01-29-MethodDeclaration.ll
2009-01-30-Method.ll
2009-02-18-DefaultScope-Crash.ll
2009-02-23-InstCombine.ll
2009-02-27-licm.ll
2009-03-02-sink.ll
2009-03-03-cheapdse.ll	Make my earlier patch to skip debug intrinsics	2009-03-04 01:20:34 +00:00
2009-03-03-deadstore.ll	When removing a store to an alloca that has only one	2009-03-03 21:26:39 +00:00
2009-03-03-store-to-load-forward.ll	Instruction counters must skip the bitcasts that	2009-03-03 22:36:47 +00:00
2009-03-05-gvn.ll	Ignore the debug info intrinsics when looking for dependency through basic block.	2009-03-05 01:45:43 +00:00
dataOnly.ll
deaddebuglabel.ll
dg.exp
forwardDecl.ll
funccall.ll
globalGetElementPtr.ll
printdbginfo2.ll	Global variables don't have a corresponding llvm.dbg.declare, yet it is possible	2009-03-10 13:41:26 +00:00
printdbginfo.ll	Global variables don't have a corresponding llvm.dbg.declare, yet it is possible	2009-03-10 13:41:26 +00:00