Oliver Stannard e538054e6d [Assembler] Make fatal assembler errors non-fatal ... Currently, if the assembler encounters an error after parsing (such as an out-of-range fixup), it reports this as a fatal error, and so stops after the first error. However, for most of these there is an obvious way to recover after emitting the error, such as emitting the fixup with a value of zero. This means that we can report on all of the errors in a file, not just the first one. MCContext::reportError records the fact that an error was encountered, so we won't actually emit an object file with the incorrect contents. Differential Revision: http://reviews.llvm.org/D14717 llvm-svn: 253328		2015-11-17 10:00:43 +00:00
..
classrefs.s	Revert r240302 ("Bring r240130 back.").	2015-06-23 11:31:32 +00:00
cstexpr-gotpcrel.ll	[opaque pointer type] Add textual IR support for explicit type parameter to gep operator	2015-03-13 18:20:45 +00:00
darwin-ARM64-local-label-diff.s	[MC] Convert other MachO tests from macho-dump to llvm-readobj.	2015-09-05 01:02:05 +00:00
darwin-ARM64-reloc.s	Revert r240302 ("Bring r240130 back.").	2015-06-23 11:31:32 +00:00
ld64-workaround.s	Revert r240302 ("Bring r240130 back.").	2015-06-23 11:31:32 +00:00
lit.local.cfg
mergeable.s	Revert r240302 ("Bring r240130 back.").	2015-06-23 11:31:32 +00:00
reloc-crash2.s	Improve the --expand-relocs handling of MachO.	2015-06-18 22:38:20 +00:00
reloc-crash.s	Revert r240302 ("Bring r240130 back.").	2015-06-23 11:31:32 +00:00
reloc-errors.s	[Assembler] Make fatal assembler errors non-fatal	2015-11-17 10:00:43 +00:00