llvm-mirror/invalid-hint-arm.s at a6d1d552c3ad5b856e646252dc701106f802e673 - llvm-mirror - Git.je (Gitea)

RPCS3/llvm-mirror

mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-26 04:32:44 +01:00

Oliver Stannard 33d655fd7a [ARM, Asm] Change grammar of immediate operand diagnostics

Currently, our diagnostics for assembly operands are not consistent.
Some start with (for example) "immediate operand must be ...",
and some with "operand must be an immediate ...". I think the latter
form is preferable for a few reasons:
* It's unambiguous that it is referring to the expected type of operand, not
  the type the user provided. For example, the user could provide an register
  operand, and get a message taking about an operand is if it is already an
  immediate, just not in the accepted range.
* It allows us to have a consistent style once we add diagnostics for operands
  that could take two forms, for example a label or pc-relative memory operand.

Differential revision: https://reviews.llvm.org/D36689

llvm-svn: 314887

2017-10-04 09:18:07 +00:00

9 lines

243 B

ArmAsm

Raw Blame History

 @ RUN: not llvm-mc -triple=armv7-apple-darwin -mcpu=cortex-a8 < %s 2>&1 | FileCheck %s
 hint #240
 hint #1000
 @ CHECK: error: operand must be an immediate in the range [0,239]
 @ CHECK: error: operand must be an immediate in the range [0,239]