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
..
Analysis
Assembler
Bindings
Bitcode
BugPoint
CodeGen	AVX512 : regenerate the test file against trunk.	2015-11-17 08:03:43 +00:00
DebugInfo	dwarfdump: Use the index to find the right abbrev offset in DWP files	2015-11-17 00:39:55 +00:00
Examples
ExecutionEngine
Feature
FileCheck
Instrumentation
Integer
JitListener
LibDriver
Linker
LTO
MC	[Assembler] Make fatal assembler errors non-fatal	2015-11-17 10:00:43 +00:00
Object
Other
SymbolRewriter
TableGen
tools	SamplePGO - Add dump routines for LineLocation, SampleRecord and FunctionSamples	2015-11-13 20:24:28 +00:00
Transforms	[PRE] Preserve !invariant.load metadata	2015-11-17 00:15:09 +00:00
Unit
Verifier
YAMLParser
.clang-format
CMakeLists.txt
lit.cfg
lit.site.cfg.in
Makefile
Makefile.tests
TestRunner.sh