llvm-project/llvm/test/MC/Mips/mips-pc16-fixup.s

# RUN: llvm-mc %s -triple=mips-unknown-linux -mcpu=mips32r2 -arch=mips 2>&1 -filetype=obj | FileCheck %s
#
# CHECK-NOT: error: out of range PC16 fixup

.text
  b foo
  .space 131072 - 8, 1  # -8 = size of b instr plus size of automatically inserted nop
foo:
  add $0,$0,$0
[mips] Fix off by one issue when applying a fixup. The branch offset for a R_MIPS_PC16 relocation is indeed a 16-bit signed immediate. llvm-svn: 197506 2013-12-18 01:10:00 +08:00			`# RUN: llvm-mc %s -triple=mips-unknown-linux -mcpu=mips32r2 -arch=mips 2>&1 -filetype=obj \| FileCheck %s`
			`#`
[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-NOT: error: out of range PC16 fixup`
[mips] Fix off by one issue when applying a fixup. The branch offset for a R_MIPS_PC16 relocation is indeed a 16-bit signed immediate. llvm-svn: 197506 2013-12-18 01:10:00 +08:00
			`.text`
			`b foo`
			`.space 131072 - 8, 1 # -8 = size of b instr plus size of automatically inserted nop`
			`foo:`
			`add $0,$0,$0`