The FileCheck -check-prefix option¶

The FileCheck -check-prefix option allows multiple test configurations to be driven from one .ll file. This is useful in many circumstances, for example, testing different architectural variants with llc. Here's a simple example:

; RUN: llvm-as < %s | llc -mtriple=i686-apple-darwin9 -mattr=sse41 \
; RUN:              | FileCheck %s -check-prefix=X32
; RUN: llvm-as < %s | llc -mtriple=x86_64-apple-darwin9 -mattr=sse41 \
; RUN:              | FileCheck %s -check-prefix=X64
define <4 x i32> @pinsrd_1(i32 %s, <4 x i32> %tmp) nounwind {


        %tmp1 = insertelement <4 x i32>; %tmp, i32 %s, i32 1


        ret <4 x i32> %tmp1
; X32: pinsrd_1:
; X32:    pinsrd $1, 4(%esp), %xmm0
; X64: pinsrd_1:
; X64:    pinsrd $1, %edi, %xmm0
}

In this case, we're testing that we get the expected code generation with both 32-bit and 64-bit code generation.

The COM: directive¶

Sometimes you want to disable a FileCheck directive without removing it entirely, or you want to write comments that mention a directive by name. The "COM:" directive makes it easy to do this. For example, you might have:

; X32: pinsrd_1:
; X32:    pinsrd $1, 4(%esp), %xmm0
; COM: FIXME: X64 isn't working correctly yet for this part of codegen, but
; COM: X64 will have something similar to X32:
; COM:
; COM:   X64: pinsrd_1:
; COM:   X64:    pinsrd $1, %edi, %xmm0

Without "COM:", you would need to use some combination of rewording and directive syntax mangling to prevent FileCheck from recognizing the commented occurrences of "X32:" and "X64:" above as directives. Moreover, FileCheck diagnostics have been proposed that might complain about the above occurrences of "X64" that don't have the trailing ":" because they look like directive typos. Dodging all these problems can be tedious for a test author, and directive syntax mangling can make the purpose of test code unclear. "COM:" avoids all these problems.

A few important usage notes:

; X32: pinsrd $1, 4(%esp), %xmm0 COM: This is part of the X32 pattern!

The CHECK-NEXT: directive¶

Sometimes you want to match lines and would like to verify that matches happen on exactly consecutive lines with no other lines in between them. In this case, you can use "CHECK:" and "CHECK-NEXT:" directives to specify this. If you specified a custom check prefix, just use "<PREFIX>-NEXT:". For example, something like this works as you'd expect:

define void @t2(<2 x double>* %r, <2 x double>* %A, double %B) {


     %tmp3 = load <2 x double>* %A, align 16


     %tmp7 = insertelement <2 x double> undef, double %B, i32 0


     %tmp9 = shufflevector <2 x double> %tmp3,


                            <2 x double> %tmp7,


                            <2 x i32> < i32 0, i32 2 >


     store <2 x double> %tmp9, <2 x double>* %r, align 16


     ret void
; CHECK:          t2:
; CHECK:             movl    8(%esp), %eax
; CHECK-NEXT:        movapd  (%eax), %xmm0
; CHECK-NEXT:        movhpd  12(%esp), %xmm0
; CHECK-NEXT:        movl    4(%esp), %eax
; CHECK-NEXT:        movapd  %xmm0, (%eax)
; CHECK-NEXT:        ret
}

"CHECK-NEXT:" directives reject the input unless there is exactly one newline between it and the previous directive. A "CHECK-NEXT:" cannot be the first directive in a file.

The CHECK-SAME: directive¶

Sometimes you want to match lines and would like to verify that matches happen on the same line as the previous match. In this case, you can use "CHECK:" and "CHECK-SAME:" directives to specify this. If you specified a custom check prefix, just use "<PREFIX>-SAME:".

"CHECK-SAME:" is particularly powerful in conjunction with "CHECK-NOT:" (described below).

For example, the following works like you'd expect:

!0 = !DILocation(line: 5, scope: !1, inlinedAt: !2)
; CHECK:       !DILocation(line: 5,
; CHECK-NOT:               column:
; CHECK-SAME:              scope: ![[SCOPE:[0-9]+]]

"CHECK-SAME:" directives reject the input if there are any newlines between it and the previous directive.

"CHECK-SAME:" is also useful to avoid writing matchers for irrelevant fields. For example, suppose you're writing a test which parses a tool that generates output like this:

Name: foo
Field1: ...
Field2: ...
Field3: ...
Value: 1
Name: bar
Field1: ...
Field2: ...
Field3: ...
Value: 2
Name: baz
Field1: ...
Field2: ...
Field3: ...
Value: 1

To write a test that verifies foo has the value 1, you might first write this:

CHECK: Name: foo
CHECK: Value: 1{{$}}

However, this would be a bad test: if the value for foo changes, the test would still pass because the "CHECK: Value: 1" line would match the value from baz. To fix this, you could add CHECK-NEXT matchers for every FieldN: line, but that would be verbose, and need to be updated when Field4 is added. A more succinct way to write the test using the "CHECK-SAME:" matcher would be as follows:

CHECK:      Name: foo
CHECK:      Value:
CHECK-SAME:        {{ 1$}}

This verifies that the next time "Value:" appears in the output, it has the value 1.

Note: a "CHECK-SAME:" cannot be the first directive in a file.

The CHECK-EMPTY: directive¶

If you need to check that the next line has nothing on it, not even whitespace, you can use the "CHECK-EMPTY:" directive.

declare void @foo()
declare void @bar()
; CHECK: foo
; CHECK-EMPTY:
; CHECK-NEXT: bar

Just like "CHECK-NEXT:" the directive will fail if there is more than one newline before it finds the next blank line, and it cannot be the first directive in a file.

The CHECK-NOT: directive¶

The "CHECK-NOT:" directive is used to verify that a string doesn't occur between two matches (or before the first match, or after the last match). For example, to verify that a load is removed by a transformation, a test like this can be used:

define i8 @coerce_offset0(i32 %V, i32* %P) {


  store i32 %V, i32* %P


  %P2 = bitcast i32* %P to i8*


  %P3 = getelementptr i8* %P2, i32 2


  %A = load i8* %P3


  ret i8 %A
; CHECK: @coerce_offset0
; CHECK-NOT: load
; CHECK: ret i8
}

The CHECK-COUNT: directive¶

If you need to match multiple lines with the same pattern over and over again you can repeat a plain CHECK: as many times as needed. If that looks too boring you can instead use a counted check "CHECK-COUNT-<num>:", where <num> is a positive decimal number. It will match the pattern exactly <num> times, no more and no less. If you specified a custom check prefix, just use "<PREFIX>-COUNT-<num>:" for the same effect. Here is a simple example:

Loop at depth 1
Loop at depth 1
Loop at depth 1
Loop at depth 1


  Loop at depth 2


    Loop at depth 3
; CHECK-COUNT-6: Loop at depth {{[0-9]+}}
; CHECK-NOT:     Loop at depth {{[0-9]+}}

The CHECK-DAG: directive¶

If it's necessary to match strings that don't occur in a strictly sequential order, "CHECK-DAG:" could be used to verify them between two matches (or before the first match, or after the last match). For example, clang emits vtable globals in reverse order. Using CHECK-DAG:, we can keep the checks in the natural order:

// RUN: %clang_cc1 %s -emit-llvm -o - | FileCheck %s
struct Foo { virtual void method(); };
Foo f;  // emit vtable
// CHECK-DAG: @_ZTV3Foo =
struct Bar { virtual void method(); };
Bar b;
// CHECK-DAG: @_ZTV3Bar =

CHECK-NOT: directives could be mixed with CHECK-DAG: directives to exclude strings between the surrounding CHECK-DAG: directives. As a result, the surrounding CHECK-DAG: directives cannot be reordered, i.e. all occurrences matching CHECK-DAG: before CHECK-NOT: must not fall behind occurrences matching CHECK-DAG: after CHECK-NOT:. For example,

; CHECK-DAG: BEFORE
; CHECK-NOT: NOT
; CHECK-DAG: AFTER

This case will reject input strings where BEFORE occurs after AFTER.

With captured variables, CHECK-DAG: is able to match valid topological orderings of a DAG with edges from the definition of a variable to its use. It's useful, e.g., when your test cases need to match different output sequences from the instruction scheduler. For example,

; CHECK-DAG: add [[REG1:r[0-9]+]], r1, r2
; CHECK-DAG: add [[REG2:r[0-9]+]], r3, r4
; CHECK:     mul r5, [[REG1]], [[REG2]]

In this case, any order of that two add instructions will be allowed.

If you are defining and using variables in the same CHECK-DAG: block, be aware that the definition rule can match after its use.

So, for instance, the code below will pass:

; CHECK-DAG: vmov.32 [[REG2:d[0-9]+]][0]
; CHECK-DAG: vmov.32 [[REG2]][1]
vmov.32 d0[1]
vmov.32 d0[0]

While this other code, will not:

; CHECK-DAG: vmov.32 [[REG2:d[0-9]+]][0]
; CHECK-DAG: vmov.32 [[REG2]][1]
vmov.32 d1[1]
vmov.32 d0[0]

While this can be very useful, it's also dangerous, because in the case of register sequence, you must have a strong order (read before write, copy before use, etc). If the definition your test is looking for doesn't match (because of a bug in the compiler), it may match further away from the use, and mask real bugs away.

In those cases, to enforce the order, use a non-DAG directive between DAG-blocks.

A CHECK-DAG: directive skips matches that overlap the matches of any preceding CHECK-DAG: directives in the same CHECK-DAG: block. Not only is this non-overlapping behavior consistent with other directives, but it's also necessary to handle sets of non-unique strings or patterns. For example, the following directives look for unordered log entries for two tasks in a parallel program, such as the OpenMP runtime:

// CHECK-DAG: [[THREAD_ID:[0-9]+]]: task_begin
// CHECK-DAG: [[THREAD_ID]]: task_end
//
// CHECK-DAG: [[THREAD_ID:[0-9]+]]: task_begin
// CHECK-DAG: [[THREAD_ID]]: task_end

The second pair of directives is guaranteed not to match the same log entries as the first pair even though the patterns are identical and even if the text of the log entries is identical because the thread ID manages to be reused.

The CHECK-LABEL: directive¶

Sometimes in a file containing multiple tests divided into logical blocks, one or more CHECK: directives may inadvertently succeed by matching lines in a later block. While an error will usually eventually be generated, the check flagged as causing the error may not actually bear any relationship to the actual source of the problem.

In order to produce better error messages in these cases, the "CHECK-LABEL:" directive can be used. It is treated identically to a normal CHECK directive except that FileCheck makes an additional assumption that a line matched by the directive cannot also be matched by any other check present in match-filename; this is intended to be used for lines containing labels or other unique identifiers. Conceptually, the presence of CHECK-LABEL divides the input stream into separate blocks, each of which is processed independently, preventing a CHECK: directive in one block matching a line in another block. If --enable-var-scope is in effect, all local variables are cleared at the beginning of the block.

For example,

define %struct.C* @C_ctor_base(%struct.C* %this, i32 %x) {
entry:
; CHECK-LABEL: C_ctor_base:
; CHECK: mov [[SAVETHIS:r[0-9]+]], r0
; CHECK: bl A_ctor_base
; CHECK: mov r0, [[SAVETHIS]]


  %0 = bitcast %struct.C* %this to %struct.A*


  %call = tail call %struct.A* @A_ctor_base(%struct.A* %0)


  %1 = bitcast %struct.C* %this to %struct.B*


  %call2 = tail call %struct.B* @B_ctor_base(%struct.B* %1, i32 %x)


  ret %struct.C* %this
}
define %struct.D* @D_ctor_base(%struct.D* %this, i32 %x) {
entry:
; CHECK-LABEL: D_ctor_base:

The use of CHECK-LABEL: directives in this case ensures that the three CHECK: directives only accept lines corresponding to the body of the @C_ctor_base function, even if the patterns match lines found later in the file. Furthermore, if one of these three CHECK: directives fail, FileCheck will recover by continuing to the next block, allowing multiple test failures to be detected in a single invocation.

There is no requirement that CHECK-LABEL: directives contain strings that correspond to actual syntactic labels in a source or output language: they must simply uniquely match a single line in the file being verified.

CHECK-LABEL: directives cannot contain variable definitions or uses.

Directive modifiers¶

A directive modifier can be append to a directive by following the directive with {<modifier>} where the only supported value for <modifier> is LITERAL.

The LITERAL directive modifier can be used to perform a literal match. The modifier results in the directive not recognizing any syntax to perform regex matching, variable capture or any substitutions. This is useful when the text to match would require excessive escaping otherwise. For example, the following will perform literal matches rather than considering these as regular expressions:

Input: [[[10, 20]], [[30, 40]]]
Output %r10: [[10, 20]]
Output %r10: [[30, 40]]
; CHECK{LITERAL}: [[[10, 20]], [[30, 40]]]
; CHECK-DAG{LITERAL}: [[30, 40]]
; CHECK-DAG{LITERAL}: [[10, 20]]

FileCheck Regex Matching Syntax¶

All FileCheck directives take a pattern to match. For most uses of FileCheck, fixed string matching is perfectly sufficient. For some things, a more flexible form of matching is desired. To support this, FileCheck allows you to specify regular expressions in matching strings, surrounded by double braces: {{yourregex}}. FileCheck implements a POSIX regular expression matcher; it supports Extended POSIX regular expressions (ERE). Because we want to use fixed string matching for a majority of what we do, FileCheck has been designed to support mixing and matching fixed string matching with regular expressions. This allows you to write things like this:

; CHECK: movhpd      {{[0-9]+}}(%esp), {{%xmm[0-7]}}

In this case, any offset from the ESP register will be allowed, and any xmm register will be allowed.

Because regular expressions are enclosed with double braces, they are visually distinct, and you don't need to use escape characters within the double braces like you would in C. In the rare case that you want to match double braces explicitly from the input, you can use something ugly like {{[}][}]}} as your pattern. Or if you are using the repetition count syntax, for example [[:xdigit:]]{8} to match exactly 8 hex digits, you would need to add parentheses like this {{([[:xdigit:]]{8})}} to avoid confusion with FileCheck's closing double-brace.

FileCheck String Substitution Blocks¶

It is often useful to match a pattern and then verify that it occurs again later in the file. For codegen tests, this can be useful to allow any register, but verify that that register is used consistently later. To do this, FileCheck supports string substitution blocks that allow string variables to be defined and substituted into patterns. Here is a simple example:

; CHECK: test5:
; CHECK:    notw     [[REGISTER:%[a-z]+]]
; CHECK:    andw     {{.*}}[[REGISTER]]

The first check line matches a regex %[a-z]+ and captures it into the string variable REGISTER. The second line verifies that whatever is in REGISTER occurs later in the file after an "andw". FileCheck string substitution blocks are always contained in [[ ]] pairs, and string variable names can be formed with the regex [a-zA-Z_][a-zA-Z0-9_]*. If a colon follows the name, then it is a definition of the variable; otherwise, it is a substitution.

FileCheck variables can be defined multiple times, and substitutions always get the latest value. Variables can also be substituted later on the same line they were defined on. For example:

; CHECK: op [[REG:r[0-9]+]], [[REG]]

Can be useful if you want the operands of op to be the same register, and don't care exactly which register it is.

If --enable-var-scope is in effect, variables with names that start with $ are considered to be global. All others variables are local. All local variables get undefined at the beginning of each CHECK-LABEL block. Global variables are not affected by CHECK-LABEL. This makes it easier to ensure that individual tests are not affected by variables set in preceding tests.

FileCheck Numeric Substitution Blocks¶

FileCheck also supports numeric substitution blocks that allow defining numeric variables and checking for numeric values that satisfy a numeric expression constraint based on those variables via a numeric substitution. This allows CHECK: directives to verify a numeric relation between two numbers, such as the need for consecutive registers to be used.

The syntax to capture a numeric value is [[#%<fmtspec>,<NUMVAR>:]] where:

The syntax of <fmtspec> is: #.<precision><conversion specifier> where:

For example:

; CHECK: mov r[[#REG:]], 0x[[#%.8X,ADDR:]]

would match mov r5, 0x0000FEFE and set REG to the value 5 and ADDR to the value 0xFEFE. Note that due to the precision it would fail to match mov r5, 0xFEFE.

As a result of the numeric variable definition being optional, it is possible to only check that a numeric value is present in a given format. This can be useful when the value itself is not useful, for instance:

; CHECK-NOT: mov r0, r[[#]]

to check that a value is synthesized rather than moved around.

The syntax of a numeric substitution is [[#%<fmtspec>, <constraint> <expr>]] where:

The supported operators are:

The syntax of a function call is <name>(<arguments>) where:

For example:

; CHECK: load r[[#REG:]], [r0]
; CHECK: load r[[#REG+1]], [r1]
; CHECK: Loading from 0x[[#%x,ADDR:]]
; CHECK-SAME: to 0x[[#ADDR + 7]]

The above example would match the text:

load r5, [r0]
load r6, [r1]
Loading from 0xa0463440 to 0xa0463447

but would not match the text:

load r5, [r0]
load r7, [r1]
Loading from 0xa0463440 to 0xa0463443

Due to 7 being unequal to 5 + 1 and a0463443 being unequal to a0463440 + 7.

A numeric variable can also be defined to the result of a numeric expression, in which case the numeric expression constraint is checked and if verified the variable is assigned to the value. The unified syntax for both checking a numeric expression and capturing its value into a numeric variable is thus [[#%<fmtspec>,<NUMVAR>: <constraint> <expr>]] with each element as described previously. One can use this syntax to make a testcase more self-describing by using variables instead of values:

; CHECK: mov r[[#REG_OFFSET:]], 0x[[#%X,FIELD_OFFSET:12]]
; CHECK-NEXT: load r[[#]], [r[[#REG_BASE:]], r[[#REG_OFFSET]]]

which would match:

mov r4, 0xC
load r6, [r5, r4]

The --enable-var-scope option has the same effect on numeric variables as on string variables.

Important note: In its current implementation, an expression cannot use a numeric variable defined earlier in the same CHECK directive.

FileCheck Pseudo Numeric Variables¶

Sometimes there's a need to verify output that contains line numbers of the match file, e.g. when testing compiler diagnostics. This introduces a certain fragility of the match file structure, as "CHECK:" lines contain absolute line numbers in the same file, which have to be updated whenever line numbers change due to text addition or deletion.

To support this case, FileCheck expressions understand the @LINE pseudo numeric variable which evaluates to the line number of the CHECK pattern where it is found.

This way match patterns can be put near the relevant test lines and include relative line number references, for example:

// CHECK: test.cpp:[[# @LINE + 4]]:6: error: expected ';' after top level declarator
// CHECK-NEXT: {{^int a}}
// CHECK-NEXT: {{^     \^}}
// CHECK-NEXT: {{^     ;}}
int a

To support legacy uses of @LINE as a special string variable, FileCheck also accepts the following uses of @LINE with string substitution block syntax: [[@LINE]], [[@LINE+<offset>]] and [[@LINE-<offset>]] without any spaces inside the brackets and where offset is an integer.

Matching Newline Characters¶

To match newline characters in regular expressions the character class [[:space:]] can be used. For example, the following pattern:

// CHECK: DW_AT_location [DW_FORM_sec_offset] ([[DLOC:0x[0-9a-f]+]]){{[[:space:]].*}}"intd"

matches output of the form (from llvm-dwarfdump):

DW_AT_location [DW_FORM_sec_offset]   (0x00000233)
DW_AT_name [DW_FORM_strp]  ( .debug_str[0x000000c9] = "intd")

letting us set the FileCheck variable DLOC to the desired value 0x00000233, extracted from the line immediately preceding "intd".