mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-25 08:26:06 +00:00
af20c1c129
Conventionally, parsing methods return false on success and true on error. However, directive parsing methods need a third state: the directive is not target specific. AsmParser::parseStatement detected this case by using a fragile heuristic: if the target parser did not consume any tokens, the directive is assumed to be not target-specific. Some targets fail to follow the convention: they return success after emitting an error or do not consume the entire line and return failure on successful parsing. This was partially worked around by checking for pending errors in parseStatement. This patch tries to improve the situation by introducing parseDirective method that returns ParseStatus -- three-state class. The new method should eventually replace the old one returning bool. ParseStatus is intentionally implicitly constructible from bool to allow uses like `return Error(Loc, "message")`. It also has a potential to replace OperandMatchResulTy as it is more convenient to use due to the implicit construction from bool and more type safe. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D154101
46 lines
1.6 KiB
ArmAsm
46 lines
1.6 KiB
ArmAsm
# RUN: not llvm-mc -triple=ve -filetype=obj %s -o /dev/null 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
.data
|
|
a:
|
|
.2byte 0xff5588
|
|
.4byte 0xff5588aade
|
|
.8byte 0xff5588aadeadbeafde
|
|
.byte 0xff55
|
|
.short 0xff5588
|
|
.word 0xff5588aaff
|
|
.int 0xff5588aaff
|
|
.long 0xff5588aadeadbeafde
|
|
.quad 0xff5588aadeadbeafde
|
|
.llong 0xff5588aadeadbeafde
|
|
|
|
# CHECK: data-size-error.s:6:8: error: out of range literal value
|
|
# CHECK-NEXT: .2byte 0xff5588
|
|
# CHECK: data-size-error.s:7:8: error: out of range literal value
|
|
# CHECK-NEXT: .4byte 0xff5588aade
|
|
# CHECK: data-size-error.s:8:8: error: literal value out of range for directive
|
|
# CHECK-NEXT: .8byte 0xff5588aadeadbeafde
|
|
# CHECK: data-size-error.s:9:7: error: out of range literal value
|
|
# CHECK-NEXT: .byte 0xff55
|
|
# CHECK: data-size-error.s:10:8: error: out of range literal value
|
|
# CHECK-NEXT: .short 0xff5588
|
|
# CHECK: data-size-error.s:11:1: error: value evaluated as 1096651680511 is out of range.
|
|
# CHECK-NEXT: .word 0xff5588aaff
|
|
# CHECK: data-size-error.s:12:6: error: out of range literal value
|
|
# CHECK-NEXT: .int 0xff5588aaff
|
|
# CHECK: data-size-error.s:13:7: error: literal value out of range for directive
|
|
# CHECK-NEXT: .long 0xff5588aadeadbeafde
|
|
# CHECK: data-size-error.s:14:7: error: literal value out of range for directive
|
|
# CHECK-NEXT: .quad 0xff5588aadeadbeafde
|
|
# CHECK: data-size-error.s:15:8: error: literal value out of range for directive
|
|
# CHECK-NEXT: .llong 0xff5588aadeadbeafde
|
|
|
|
# CHECK: [[#@LINE+1]]:17: error: unknown token in expression
|
|
.word 0xd0bb1e +
|
|
|
|
# CHECK: [[#@LINE+1]]:16: error: unexpected token
|
|
.long 0xd0bb1e =
|
|
|
|
# CHECK: [[#@LINE+1]]:10: error: unexpected token
|
|
.llong 2 0xd0bb1e
|