[FileCheck] Fix sphinx error: make input be gas block

[thopre]

Summary

Change example of input text from being llvm block to being gas block
since that text is made-up assembly.

[jhenderson]

I'm not sure I follow what this achieves. https://llvm.org/docs/CommandGuide/FileCheck.html looks okay to me.... I see the build bot failure. Can you point at documentation that indicates what the problem is?

[thopre]

In D61893#1501244, @jhenderson wrote:

I'm not sure I follow what this achieves. https://llvm.org/docs/CommandGuide/FileCheck.html looks okay to me.... I see the build bot failure. Can you point at documentation that indicates what the problem is?

The only documentation I can find is [1] and [2]. where the former mention that code-block:: llvm is for LLVM IR and the latter specifies that it is for syntax highlighting. The error message seems to corroborate that there is some sort of parsing of the block going on and the two block I'm chanking here are not LLVM IR but made up assembly. I am not able to reproduce the bug sadly (I did manage to reproduce the other one eventually FYI) so cannot get 100% sure it will fix the issue but [2] does mention that code-block:: test is a null parser that does not provide any syntax highlighting.

[1] llvm/docs/SphinxQuickstartTemplate.rst
[2] http://pygments.org/docs/lexers/

[jhenderson]

llvm/docs/CommandGuide/FileCheck.rst

596 ↗

(On Diff #199419)

Could you use gas/asm?

[thopre]

llvm/docs/CommandGuide/FileCheck.rst

596 ↗

(On Diff #199419)

I suppose since there isn't any directive but I wouldn't be able to check that it will build successfully.

[thopre]

Use gas block instead of text

[jhenderson]

LGTM. If gas doesn't work, feel free to change to text with no further review.

llvm/docs/CommandGuide/FileCheck.rst

596 ↗

(On Diff #199419)

Since this is generic assembly, my reading of http://pygments.org/docs/lexers/#pygments.lexers.asm.GasLexer is that this would be the best match, but I don't really know. It's easy enough to fix if that doesn't work though.

llvm/trunk/docs/CommandGuide/FileCheck.rst

 For example:
 
 .. code-block:: llvm
 
     ; CHECK: add r[[#REG]], r[[#REG]], r[[#REG+1]]
 
 The above example would match the line:
 
-.. code-block:: llvm
+.. code-block:: gas
 
     add r5, r5, r6
 
 but would not match the line:
 
-.. code-block:: llvm
+.. code-block:: gas
 
     add r5, r5, r7
 
 due to ``7`` being unequal to ``5 + 1``.
 
 The ``--enable-var-scope`` option has the same effect on numeric variables as
 on pattern variables.