llvm-project/llvm/test/MC/ELF/common-error1.s

// RUN: not llvm-mc -filetype=obj -triple x86_64-pc-linux < %s 2>&1 | FileCheck %s

        .comm   C,4,4
        .set    A,C

// CHECK: Common symbol 'C' cannot be used in assignment expr
Produce errors when an assignment expression would use a common symbol. An assignment will produce a symbol with a given section and offset. There is no way to represent something like "1 byte after a common symbol". This matches the behavior of GNU as. Part of PR22217. llvm-svn: 226470 2015-01-20 01:30:24 +08:00			`// RUN: not llvm-mc -filetype=obj -triple x86_64-pc-linux < %s 2>&1 \| FileCheck %s`

			`.comm C,4,4`
			`.set A,C`

[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 18:00:43 +08:00			`// CHECK: Common symbol 'C' cannot be used in assignment expr`