3 Commits

Author	SHA1	Message	Date
Eric Christopher	14ec6808c4	If we're only emitting line tables for a particular CU then don't add ... any ranges to the list of ranges for the CU as we don't want to emit them anyway. This ensures that we will still emit ranges if we have a compile unit compiled with only line tables and one compiled with full debug info requested (we'll emit for the one with full debug info). Update testcase metadata accordingly to continue emitting ranges. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@202333 91177308-0d34-0410-b5e6-96231b3b80d8	2014-02-27 01:25:00 +00:00
David Blaikie	cec7ce78d7	DebugInfo: Remove some unneeded conditionals now that DIBuilder no longer emits zero-length arrays as {i32 0} ... A bunch of test cases needed to be cleaned up for this, many my fault - when implementid imported modules I updated test cases by simply duplicating the prior metadata field - which wasn't always the empty metadata entry. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@200731 91177308-0d34-0410-b5e6-96231b3b80d8	2014-02-04 01:23:52 +00:00
Eric Christopher	2f9fe10f6f	Make the use of DW_AT_ranges in the compile unit depend also upon ... the existence of comdat/special sections. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@199954 91177308-0d34-0410-b5e6-96231b3b80d8	2014-01-23 22:55:47 +00:00