6 Commits

Author	SHA1	Message	Date
David Blaikie	9c550ac4e7	DebugInfo: Support debug_loc under fission ... Implement debug_loc.dwo, as well as llvm-dwarfdump support for dumping this section. Outlined in the DWARF5 spec and http://gcc.gnu.org/wiki/DebugFission the debug_loc.dwo section has more variation than the standard debug_loc, allowing 3 different forms of entry (plus the end of list entry). GCC seems to, and Clang certainly, only use one form, so I've just implemented dumping support for that for now. It wasn't immediately obvious that there was a good refactoring to share the implementation of dumping support between debug_loc and debug_loc.dwo, so they're separate for now - ideas welcome or I may come back to it at some point. As per a comment in the code, we could choose different forms that may reduce the number of debug_addr entries we emit, but that will require further study. llvm-svn: 204697	2014-03-25 01:44:02 +00:00
Alexey Samsonov	1eabf98b32	[C++11] Convert DWARF parser to range-based for loops ... llvm-svn: 203766	2014-03-13 07:52:54 +00:00
Chandler Carruth	002da5db29	[C++11] Switch all uses of the llvm_move macro to use std::move ... directly, and remove the macro. llvm-svn: 202612	2014-03-02 04:08:41 +00:00
Adrian Prantl	6f84d31540	make llvm-dwarfdump a little more resilient when parsing .debug_loc ... sections. The call to data.getUnsigned(&Offset, AddressSize) only increments Offset if the read succeeds, which will result in an infinite loop. llvm-svn: 201179	2014-02-11 21:22:53 +00:00
David Blaikie	b9a18708cc	Spell correct (s/begining/beginning/) ... llvm-svn: 184362	2013-06-19 21:42:05 +00:00
David Blaikie	18e73508c4	llvm-dwarfdump: Add support for dumping the .debug_loc section ... This is a basic implementation - we still don't have any support (that I know of) for dumping DWARF expressions in a meaningful way, so the location information itself is just printed as a sequence of bytes as we do elsewhere. llvm-svn: 184361	2013-06-19 21:37:13 +00:00