bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Remove unused "isMain" field from DICompileUnit	David Blaikie	2013-03-12	1	-1/+1
\| \| \| \|	llvm-svn: 176910
*	Update debug info test cases with empty SplitDebugFilename field.	David Blaikie	2013-03-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	This could be 'null' or the empty string, DIDescriptor::getStringField coalesces the two cases anyway so it's just a matter of legible/efficient representation. The change in behavior of the DICompileUnit::get* functions could be subsumed by the full verification check - but ideally that should just be an assertion if we could front-load the actual debug info metadata failure paths. llvm-svn: 176907
*	Upgrading debug info test cases to be (more) compatible with the current ↵	David Blaikie	2013-03-11	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	debug info format. These cases were found by further work to remove support for debug info versioning. Common cleanups (other than changing the version info in the tag field) included adding the last parameter to compile_units (recently added for fission support) and other cases of trailing fields in lexical blocks, compile units, and subprograms. llvm-svn: 176834
*	Remove the (apparently) unnecessary debug info metadata indirection.	David Blaikie	2013-02-02	1	-4/+2
\| \| \| \| \| \| \| \| \| \|	The main lists of debug info metadata attached to the compile_unit had an extra layer of metadata nodes they went through for no apparent reason. This patch removes that (& still passes just as much of the GDB 7.5 test suite). If anyone can show evidence as to why these extra metadata nodes are there I'm open to reverting this patch & documenting why they're there. llvm-svn: 174266
*	Now that llvm-dwarfdump supports flags to specify which DWARF section to dump,	Eli Bendersky	2013-01-25	1	-1/+1
\| \| \| \| \| \| \|	use them in tests that run llvm-dwarfdump. This is in order to make tests as specific as possible. llvm-svn: 173498
*	Add a name for the anonymous type we're creating for subrange	Eric Christopher	2013-01-04	1	-15/+16
\| \| \| \| \| \| \| \|	types and a FIXME for what we should be doing. Should solve the immediacy of PR12069 where our debug info is crashing another tool. llvm-svn: 171536
*	Handle non-default array bounds.	Bill Wendling	2012-12-06	1	-0/+48
	Some languages, e.g. Ada and Pascal, allow you to specify that the array bounds are different from the default (1 in these cases). If we have a lower bound that's non-default, then we emit the lower bound. We also calculate the correct upper bound in those cases. llvm-svn: 169484