llvm-mirror/test/MC/ARM/udf-arm-diagnostics.s
Sjoerd Meijer 810b9e24b2 ARMAsmParser: clean up of isImmediate functions
- we are now using immediate AsmOperands so that the range check functions are
  tablegen'ed.
- Big bonus is that error messages become much more accurate, i.e. instead of a
  useless "invalid operand" error message it will not say that the immediate
  operand must in range [x,y], which is why regression tests needed updating.

More tablegen operand descriptions could probably benefit from using
immediateAsmOperand, but this is a first good step to get rid of most of the
nearly identical range check functions. I will address the remaining immediate
operands in next clean ups.

Differential Revision: https://reviews.llvm.org/D31333

llvm-svn: 299358
2017-04-03 14:50:04 +00:00

20 lines
337 B
ArmAsm

@ RUN: not llvm-mc -triple arm-eabi %s 2>&1 | FileCheck %s
.syntax unified
.text
.arm
undefined:
udfpl
@ CHECK: error: instruction 'udf' is not predicable, but condition code specified
@ CHECK: udfpl
@ CHECK: ^
udf #65536
@ CHECK: error: immediate operand must be in the range [0,65535]
@ CHECK: udf #65536
@ CHECK: ^