llvm-mirror/test/MC/MachO/ARM/bad-darwin-ARM-reloc.s

@ RUN: not llvm-mc -n -triple armv7-apple-darwin10 %s -filetype=obj -o - 2> %t.err > %t
@ RUN: FileCheck --check-prefix=CHECK-ERROR < %t.err %s
@ rdar://15586725
.text
    ldr r3, L___fcommon
.section myseg, mysect
L___fcommon: 
    .word 0
@ CHECK-ERROR: unsupported relocation on symbol

c:
  .word a - b
@ CHECK-ERROR: symbol 'a' can not be undefined in a subtraction expression
  .word c - b
@ CHECK-ERROR: symbol 'b' can not be undefined in a subtraction expression
Fixed a bug in getARMFixupKindMachOInfo() where three ARM fixup kinds were falling into the cases for 24-bit branch kinds which are not 24-bit branches. The routine is to return false for fixups are expected to always be resolvable at assembly time. Which these three fixups are as they have limited displacement and are for local references within a function. rdar://15586725 llvm-svn: 197282 2013-12-13 23:46:54 +01:00			`@ RUN: not llvm-mc -n -triple armv7-apple-darwin10 %s -filetype=obj -o - 2> %t.err > %t`
			`@ RUN: FileCheck --check-prefix=CHECK-ERROR < %t.err %s`
			`@ rdar://15586725`
			`.text`
			`ldr r3, L___fcommon`
			`.section myseg, mysect`
			`L___fcommon:`
			`.word 0`
			`@ CHECK-ERROR: unsupported relocation on symbol`
[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
			`c:`
			`.word a - b`
			`@ CHECK-ERROR: symbol 'a' can not be undefined in a subtraction expression`
			`.word c - b`
			`@ CHECK-ERROR: symbol 'b' can not be undefined in a subtraction expression`