diff options
| author | Dmitri Gribenko <gribozavr@gmail.com> | 2012-06-12 15:45:07 +0000 |
|---|---|---|
| committer | Dmitri Gribenko <gribozavr@gmail.com> | 2012-06-12 15:45:07 +0000 |
| commit | 0d887a09421e40faadb67f1cfdfd81e5ba7bbed2 (patch) | |
| tree | 58b5d38b91d7255384d376f1ca16f6954656b37b /docs/CommandGuide/FileCheck.rst | |
| parent | c038a7833565ecf92a699371d448135a097c9e2f (diff) | |
Use correct syntax highliter in code blocks. Noticed by Sean Silva.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@158359 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/CommandGuide/FileCheck.rst')
| -rw-r--r-- | docs/CommandGuide/FileCheck.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/CommandGuide/FileCheck.rst b/docs/CommandGuide/FileCheck.rst index b4d4477122..51a9bf6293 100644 --- a/docs/CommandGuide/FileCheck.rst +++ b/docs/CommandGuide/FileCheck.rst @@ -78,7 +78,7 @@ line of the test. A simple example of using FileCheck from a RUN line looks like this: -.. code-block:: perl +.. code-block:: llvm ; RUN: llvm-as < %s | llc -march=x86-64 | FileCheck %s @@ -90,7 +90,7 @@ specified (the original .ll file specified by "%s"). To see how this works, let's look at the rest of the .ll file (after the RUN line): -.. code-block:: perl +.. code-block:: llvm define void @sub1(i32* %p, i32 %v) { entry: @@ -135,7 +135,7 @@ driven from one .ll file. This is useful in many circumstances, for example, testing different architectural variants with llc. Here's a simple example: -.. code-block:: perl +.. code-block:: llvm ; RUN: llvm-as < %s | llc -mtriple=i686-apple-darwin9 -mattr=sse41 \ ; RUN: | FileCheck %s -check-prefix=X32 @@ -168,7 +168,7 @@ you specified a custom check prefix, just use "<PREFIX>-NEXT:". For example, something like this works as you'd expect: -.. code-block:: perl +.. code-block:: llvm define void @t2(<2 x double>* %r, <2 x double>* %A, double %B) { %tmp3 = load <2 x double>* %A, align 16 @@ -204,7 +204,7 @@ example, to verify that a load is removed by a transformation, a test like this can be used: -.. code-block:: perl +.. code-block:: llvm define i8 @coerce_offset0(i32 %V, i32* %P) { store i32 %V, i32* %P @@ -235,7 +235,7 @@ mixing and matching fixed string matching with regular expressions. This allows you to write things like this: -.. code-block:: perl +.. code-block:: llvm ; CHECK: movhpd {{[0-9]+}}(%esp), {{%xmm[0-7]}} @@ -261,7 +261,7 @@ allows named variables to be defined and substituted into patterns. Here is a simple example: -.. code-block:: perl +.. code-block:: llvm ; CHECK: test5: ; CHECK: notw [[REGISTER:%[a-z]+]] |