[docs] Change non-c++ code blocks to 'text' format to fix a sphinx warning.

llvm-svn: 261744
This commit is contained in:
Alexander Kornienko 2016-02-24 15:07:48 +00:00
parent dd01f70085
commit ef10cd7f46

View File

@ -57,7 +57,7 @@ driver, but diagnostics can be :ref:`rendered in many different ways
<DiagnosticClient>` depending on how the ``DiagnosticClient`` interface is <DiagnosticClient>` depending on how the ``DiagnosticClient`` interface is
implemented. A representative example of a diagnostic is: implemented. A representative example of a diagnostic is:
.. code-block:: c++ .. code-block:: text
t.c:38:15: error: invalid operands to binary expression ('int *' and '_Complex float') t.c:38:15: error: invalid operands to binary expression ('int *' and '_Complex float')
P = (P-42) + Gamma*4; P = (P-42) + Gamma*4;
@ -374,7 +374,7 @@ use of a deprecated construct into something more palatable. Here is one such
example from the C++ front end, where we warn about the right-shift operator example from the C++ front end, where we warn about the right-shift operator
changing meaning from C++98 to C++11: changing meaning from C++98 to C++11:
.. code-block:: c++ .. code-block:: text
test.cpp:3:7: warning: use of right-shift operator ('>>') in template argument test.cpp:3:7: warning: use of right-shift operator ('>>') in template argument
will require parentheses in C++11 will require parentheses in C++11
@ -514,7 +514,7 @@ Clang represents most source ranges by [first, last], where "first" and "last"
each point to the beginning of their respective tokens. For example consider each point to the beginning of their respective tokens. For example consider
the ``SourceRange`` of the following statement: the ``SourceRange`` of the following statement:
.. code-block:: c++ .. code-block:: text
x = foo + bar; x = foo + bar;
^first ^last ^first ^last
@ -837,7 +837,7 @@ typedefs. For example, consider this code:
The code above is illegal, and thus we expect there to be diagnostics emitted The code above is illegal, and thus we expect there to be diagnostics emitted
on the annotated lines. In this example, we expect to get: on the annotated lines. In this example, we expect to get:
.. code-block:: c++ .. code-block:: text
test.c:6:1: error: indirection requires pointer operand ('foo' invalid) test.c:6:1: error: indirection requires pointer operand ('foo' invalid)
*X; // error *X; // error
@ -1422,7 +1422,7 @@ pretty-printed version of the CFG to standard error. This is especially useful
when one is using a debugger such as gdb. For example, here is the output of when one is using a debugger such as gdb. For example, here is the output of
``FooCFG->dump()``: ``FooCFG->dump()``:
.. code-block:: c++ .. code-block:: text
[ B5 (ENTRY) ] [ B5 (ENTRY) ]
Predecessors (0): Predecessors (0):