ad3b358180
A typical problem with missing a token is that the missing token is at the end of a line. The problem with this is that the error message gets reported on the start of the following line (which is where the next / invalid token is) which can be confusing. Handle this by noticing this case and backing up to the end of the previous line. Differential Revision: https://reviews.llvm.org/D125295
70 lines
1.4 KiB
MLIR
70 lines
1.4 KiB
MLIR
// RUN: mlir-opt -verify-diagnostics -split-input-file %s
|
|
|
|
func.func @switch_missing_case_value(%flag : i32, %caseOperand : i32) {
|
|
cf.switch %flag : i32, [
|
|
default: ^bb1(%caseOperand : i32),
|
|
45: ^bb2(%caseOperand : i32),
|
|
// expected-error@+1 {{expected integer value}}
|
|
: ^bb3(%caseOperand : i32)
|
|
]
|
|
|
|
^bb1(%bb1arg : i32):
|
|
return
|
|
^bb2(%bb2arg : i32):
|
|
return
|
|
^bb3(%bb3arg : i32):
|
|
return
|
|
}
|
|
|
|
// -----
|
|
|
|
func.func @switch_wrong_type_case_value(%flag : i32, %caseOperand : i32) {
|
|
cf.switch %flag : i32, [
|
|
default: ^bb1(%caseOperand : i32),
|
|
// expected-error@+1 {{expected integer value}}
|
|
"hello": ^bb2(%caseOperand : i32)
|
|
]
|
|
|
|
^bb1(%bb1arg : i32):
|
|
return
|
|
^bb2(%bb2arg : i32):
|
|
return
|
|
^bb3(%bb3arg : i32):
|
|
return
|
|
}
|
|
|
|
// -----
|
|
|
|
func.func @switch_missing_comma(%flag : i32, %caseOperand : i32) {
|
|
cf.switch %flag : i32, [
|
|
default: ^bb1(%caseOperand : i32),
|
|
// expected-error@+1 {{expected ']'}}
|
|
45: ^bb2(%caseOperand : i32)
|
|
43: ^bb3(%caseOperand : i32)
|
|
]
|
|
|
|
^bb1(%bb1arg : i32):
|
|
return
|
|
^bb2(%bb2arg : i32):
|
|
return
|
|
^bb3(%bb3arg : i32):
|
|
return
|
|
}
|
|
|
|
// -----
|
|
|
|
func.func @switch_missing_default(%flag : i32, %caseOperand : i32) {
|
|
cf.switch %flag : i32, [
|
|
// expected-error@+1 {{expected 'default'}}
|
|
45: ^bb2(%caseOperand : i32)
|
|
43: ^bb3(%caseOperand : i32)
|
|
]
|
|
|
|
^bb1(%bb1arg : i32):
|
|
return
|
|
^bb2(%bb2arg : i32):
|
|
return
|
|
^bb3(%bb3arg : i32):
|
|
return
|
|
}
|