[llvm] r276532 - Change some more llvm highlighting instances to be text instead. It seems that Pygment does not handle "token" or "none" yet, and this caused the documentation bot to go red.

[Aaron Ballman via llvm-commits]

Author: aaronballman
Date: Sat Jul 23 15:11:21 2016
New Revision: 276532

URL: http://llvm.org/viewvc/llvm-project?rev=276532&view=rev
Log:
Change some more llvm highlighting instances to be text instead. It seems that Pygment does not handle "token" or "none" yet, and this caused the documentation bot to go red.

Patch by Gor Nishanov.

Modified:
    llvm/trunk/docs/Coroutines.rst

Modified: llvm/trunk/docs/Coroutines.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/Coroutines.rst?rev=276532&r1=276531&r2=276532&view=diff
==============================================================================
--- llvm/trunk/docs/Coroutines.rst (original)
+++ llvm/trunk/docs/Coroutines.rst Sat Jul 23 15:11:21 2016
@@ -152,7 +152,7 @@ We also store addresses of the resume an
 when its identity cannot be determined statically at compile time. For our 
 example, the coroutine frame will be:
 
-.. code-block:: llvm
+.. code-block:: text
 
   %f.frame = type { void (%f.frame*)*, void (%f.frame*)*, i32 }
 
@@ -288,7 +288,7 @@ Let's consider the coroutine that has mo
 Matching LLVM code would look like (with the rest of the code remaining the same
 as the code in the previous section):
 
-.. code-block:: llvm
+.. code-block:: text
 
   loop:
     %n.addr = phi i32 [ %n, %entry ], [ %inc, %loop.resume ]
@@ -362,7 +362,7 @@ by completions of asynchronous operation
 a coroutine handle as a parameter and resume the coroutine once async
 operation is finished.
 
-.. code-block:: llvm
+.. code-block:: text
 
   void g() {
      for (;;)
@@ -385,7 +385,7 @@ point when coroutine should be ready for
 should be stored in the coroutine frame, so that it can be resumed at the 
 correct resume point):
 
-.. code-block:: llvm
+.. code-block:: text
 
   if.true:
     %save1 = call token @llvm.coro.save(i8* %hdl)
@@ -413,7 +413,7 @@ intrinsic.
 The following coroutine designates a 32 bit integer `promise` and uses it to
 store the current value produced by a coroutine.
 
-.. code-block:: llvm
+.. code-block:: text
 
   define i8* @f(i32 %n) {
   entry:
@@ -987,7 +987,7 @@ basic blocks.
 Example (normal suspend point):
 """""""""""""""""""""""""""""""
 
-.. code-block:: llvm
+.. code-block:: text
 
     %0 = call i8 @llvm.coro.suspend(token none, i1 false)
     switch i8 %0, label %suspend [i8 0, label %resume
@@ -996,7 +996,7 @@ Example (normal suspend point):
 Example (final suspend point):
 """"""""""""""""""""""""""""""
 
-.. code-block:: llvm
+.. code-block:: text
 
   while.end:
     %s.final = call i8 @llvm.coro.suspend(token none, i1 true)
@@ -1057,7 +1057,7 @@ In such a case, a coroutine should be re
 a different thread possibly prior to `async_op` call returning control back
 to the coroutine:
 
-.. code-block:: llvm
+.. code-block:: text
 
     %save1 = call token @llvm.coro.save(i8* %hdl)
     call void async_op1(i8* %hdl)
@@ -1128,7 +1128,7 @@ after suspend.
 
 A frontend can create parameter copies for `a` and `b` as follows:
 
-.. code-block:: C++
+.. code-block:: text
 
   task<int> f(A a', A b') {
     a = alloca A;