replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

rename REG -> REGISTER to make it explicit in the doc. <tt>ify some stuff. 

llvm-svn: 82892
This commit is contained in:
Chris Lattner 2009-09-27 08:01:44 +00:00
parent 8879e06d0a
commit 5e0c74780a
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
llvm/docs/TestingGuide.html
View File

@ -671,17 +671,17 @@ simple example:</p>
<div class="doc_code"> <div class="doc_code">
<pre> <pre>
; CHECK: test5: ; CHECK: test5:
; CHECK: notw <b>[[REG:%[a-z]+]]</b> ; CHECK: notw <b>[[REGISTER:%[a-z]+]]</b>
; CHECK: andw {{.*}}<b>[[REG]]</b> ; CHECK: andw {{.*}}<b>[[REGISTER]]</b>
</pre> </pre>
</div> </div>
<p>The first check line matches a regex (%[a-z]+) and captures it into the <p>The first check line matches a regex (<tt>%[a-z]+</tt>) and captures it into
variables "REG". The second line verifies that whatever is in REG occurs later the variables "REGISTER". The second line verifies that whatever is in REGISTER
in the file after an "andw". FileCheck variable references are always contained occurs later in the file after an "andw". FileCheck variable references are
in [[ ]] pairs, are named, and their names can be formed with the regex always contained in <tt>[[ ]]</tt> pairs, are named, and their names can be
"[a-zA-Z][a-zA-Z0-9]*". If a colon follows the name, then it is a definition of formed with the regex "<tt>[a-zA-Z][a-zA-Z0-9]*</tt>". If a colon follows the
the variable, if not, it is a use.</p> name, then it is a definition of the variable, if not, it is a use.</p>
<p>FileCheck variables can be defined multiple times, and uses always get the <p>FileCheck variables can be defined multiple times, and uses always get the
latest value. Note that variables are all read at the start of a "CHECK" line latest value. Note that variables are all read at the start of a "CHECK" line