mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 20:23:11 +01:00
28db0415f3
FileCheck string substitution block parsing code only report an invalid variable name in a string variable use if it starts with a forbidden character. It does not report anything if there are unparsed characters after the variable name, i.e. [[X-Y]] is parsed as [[X]] and no error is returned. This commit fixes that. Reviewed By: jdenny, jhenderson Differential Revision: https://reviews.llvm.org/D98691
26 lines
813 B
Plaintext
26 lines
813 B
Plaintext
// RUN: FileCheck -input-file %s %s
|
|
|
|
op1 r1
|
|
op2 r1, r2
|
|
; CHECK: op1 [[REG:r[0-9]]]
|
|
; CHECK-NEXT: op2 [[REG]]
|
|
|
|
op3 r16, r18, r21
|
|
op4 r30, r18, r21
|
|
; CHECK: op3 {{r[0-9]+}}, [[REGa:r[0-9]+]], [[REGb:r[0-9]+]]
|
|
; CHECK-NEXT: op4 {{r[0-9]+}}, [[REGa]], [[REGb]]
|
|
|
|
|
|
// RUN: %ProtectFileCheckOutput \
|
|
// RUN: not FileCheck --check-prefixes INVALID-VARNAME --input-file %s %s 2>&1 \
|
|
// RUN: | FileCheck --check-prefix INVALID-VARNAME-MSG --strict-whitespace %s
|
|
|
|
5
|
|
4
|
|
; INVALID-VARNAME: [[X:]]
|
|
; INVALID-VARNAME-NEXT: [[Y:]]
|
|
; INVALID-VARNAME-NEXT: [[X-Y]]
|
|
; INVALID-VARNAME-MSG: simple-var-capture.txt:[[#@LINE-1]]:27: error: invalid name in string variable use
|
|
; INVALID-VARNAME-MSG-NEXT: ; {{I}}NVALID-VARNAME-NEXT: {{\[\[X-Y\]\]}}
|
|
; INVALID-VARNAME-MSG-NEXT: {{^}} ^{{$}}
|