bcm5719-llvm/llvm/test/DebugInfo/Inputs/dwarfdump-test.elf-x86-64.debuglink, branch meklort-10.0.1 Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2018-12-21T22:25:01+00:00 Reapply: DebugInfo: Assume an absence of ranges or high_pc on a CU means the CU is empty (devoid of code addresses) 2018-12-21T22:25:01+00:00 David Blaikie dblaikie@gmail.com 2018-12-21T22:25:01+00:00 urn:sha1:c3f30a7fc6a166910d4b674301e9108f537daf3c Originally committed in r349333, reverted in r349353. GCC emitted these unconditionally on/before 4.4/March 2012 Clang emitted these unconditionally on/before 3.5/March 2014 This improves performance when parsing CUs (especially those using split DWARF) that contain no code ranges (such as the mini CUs that may be created by ThinLTO importing - though generally they should be/are avoided, especially for Split DWARF because it produces a lot of very small CUs, which don't scale well in a bunch of other ways too (including size)). The revert was due to a (Google internal) test that had some checked in old object files missing DW_AT_ranges. That's since been fixed. llvm-svn: 349968 Revert "DebugInfo: Assume an absence of ranges or high_pc on a CU means the CU is empty (devoid of code addresses)" 2018-12-17T14:14:40+00:00 Eric Liu ioeric@google.com 2018-12-17T14:14:40+00:00 urn:sha1:6c933a2bed30be7009b1994d112e188343d40265 This reverts commit r349333. It caused internal test to fail. I have sent more information to the author. llvm-svn: 349353 DebugInfo: Assume an absence of ranges or high_pc on a CU means the CU is empty (devoid of code addresses) 2018-12-17T08:27:19+00:00 David Blaikie dblaikie@gmail.com 2018-12-17T08:27:19+00:00 urn:sha1:884deed1b383b869b0e785a2fa5a823bfd4d00e3 GCC emitted these unconditionally on/before 4.4/March 2012 Clang emitted these unconditionally on/before 3.5/March 2014 This improves performance when parsing CUs (especially those using split DWARF) that contain no code ranges (such as the mini CUs that may be created by ThinLTO importing - though generally they should be/are avoided, especially for Split DWARF because it produces a lot of very small CUs, which don't scale well in a bunch of other ways too (including size)). llvm-svn: 349333 llvm-symbolizer: add support for .gnu_debuglink section 2013-08-14T17:09:30+00:00 Alexey Samsonov samsonov@google.com 2013-08-14T17:09:30+00:00 urn:sha1:3e9997f2c5f2512fb51b90f478650a4319be3e79 llvm-svn: 188386