From 0d887a09421e40faadb67f1cfdfd81e5ba7bbed2 Mon Sep 17 00:00:00 2001
From: Dmitri Gribenko <gribozavr@gmail.com>
Date: Tue, 12 Jun 2012 15:45:07 +0000
Subject: [PATCH] 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
---
 docs/CommandGuide/FileCheck.rst   | 14 +++++++-------
 docs/CommandGuide/bugpoint.rst    |  2 +-
 docs/CommandGuide/llvm-config.rst |  2 +-
 docs/CommandGuide/opt.rst         |  4 ++--
 4 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/CommandGuide/FileCheck.rst b/docs/CommandGuide/FileCheck.rst
index b4d4477122d..51a9bf6293b 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]+]]
diff --git a/docs/CommandGuide/bugpoint.rst b/docs/CommandGuide/bugpoint.rst
index 2c66d104963..c1b3b6eca62 100644
--- a/docs/CommandGuide/bugpoint.rst
+++ b/docs/CommandGuide/bugpoint.rst
@@ -211,7 +211,7 @@ OPTIONS
  testcase and pass the name of an executable compile-command script in this form:
 
 
- .. code-block:: perl
+ .. code-block:: sh
 
       #!/bin/sh
       llc "$@"
diff --git a/docs/CommandGuide/llvm-config.rst b/docs/CommandGuide/llvm-config.rst
index 0da42d70faa..0ebb344c06a 100644
--- a/docs/CommandGuide/llvm-config.rst
+++ b/docs/CommandGuide/llvm-config.rst
@@ -25,7 +25,7 @@ EXAMPLES
 To link against the JIT:
 
 
-.. code-block:: perl
+.. code-block:: sh
 
    g++ `llvm-config --cxxflags` -o HowToUseJIT.o -c HowToUseJIT.cpp
    g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \
diff --git a/docs/CommandGuide/opt.rst b/docs/CommandGuide/opt.rst
index 31e57168075..72f19034c9e 100644
--- a/docs/CommandGuide/opt.rst
+++ b/docs/CommandGuide/opt.rst
@@ -86,7 +86,7 @@ OPTIONS
  of options available, use the following command:
 
 
- .. code-block:: perl
+ .. code-block:: sh
 
      llvm-as < /dev/null | opt -std-compile-opts -disable-output -debug-pass=Arguments
 
@@ -161,7 +161,7 @@ OPTIONS
  optimizations, use the **-help** and **-load** options together. For example:
 
 
- .. code-block:: perl
+ .. code-block:: sh
 
      opt -load=plugin.so -help
 
-- 
2.34.1