RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-12-26 05:56:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

FileCheck: Document CHECK-SAME, follow-up to r230612

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@231379 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Duncan P. N. Exon Smith 2015-03-05 17:00:05 +00:00
parent b98636a0f8
commit cc2c1c9bf6
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/CommandGuide/FileCheck.rst
View File

@ -185,6 +185,31 @@ For example, something like this works as you'd expect:
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:
.. code-block:: llvm
!0 = !MDLocation(line: 5, scope: !1, inlinedAt: !2)
; CHECK: !MDLocation(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. A "``CHECK-SAME:``" cannot be the first
directive in a file.
The "CHECK-NOT:" directive
~~~~~~~~~~~~~~~~~~~~~~~~~~