llvm-mirror/test/MC/COFF/invalid-scl-range.s

# RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s

	.def storage_class_range
# CHECK: storage class value '1337' out of range
# CHECK: storage class value '9001' out of range
		.scl 1337
		.scl 9001
	.endef
MC: formalise some assertions into proper errors Now that clang can be used as an assembler via the IAS, invalid assembler inputs would cause the assertions to trigger. Although we cannot recover from the errors here, nor provide caret diagnostics, attempt to handle them slightly more gracefully by reporting a fatal error. llvm-svn: 209387 2014-05-22 04:18:10 +02:00			`# RUN: not llvm-mc -triple i686-windows -filetype obj -o /dev/null %s`

			`.def storage_class_range`
[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 11:00:43 +01:00			`# CHECK: storage class value '1337' out of range`
			`# CHECK: storage class value '9001' out of range`
MC: formalise some assertions into proper errors Now that clang can be used as an assembler via the IAS, invalid assembler inputs would cause the assertions to trigger. Although we cannot recover from the errors here, nor provide caret diagnostics, attempt to handle them slightly more gracefully by reporting a fatal error. llvm-svn: 209387 2014-05-22 04:18:10 +02:00			`.scl 1337`
[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 11:00:43 +01:00			`.scl 9001`
MC: formalise some assertions into proper errors Now that clang can be used as an assembler via the IAS, invalid assembler inputs would cause the assertions to trigger. Although we cannot recover from the errors here, nor provide caret diagnostics, attempt to handle them slightly more gracefully by reporting a fatal error. llvm-svn: 209387 2014-05-22 04:18:10 +02:00			`.endef`