maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/ARM/invalid-hint-arm.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

9 lines
243 B
ArmAsm
Raw Normal View History

Make ARM hint ranges consistent, and add tests for these ranges llvm-svn: 193238
2013-10-23 18:14:40 +08:00
@ RUN: not llvm-mc -triple=armv7-apple-darwin -mcpu=cortex-a8 < %s 2>&1 | FileCheck %s
hint #240
hint #1000
[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 17:18:07 +08:00
@ CHECK: error: operand must be an immediate in the range [0,239]
@ CHECK: error: operand must be an immediate in the range [0,239]
Make ARM hint ranges consistent, and add tests for these ranges llvm-svn: 193238
2013-10-23 18:14:40 +08:00