6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-30 17:33:24 +00:00
Code Issues Projects Releases Wiki Activity

Grammar fix.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51236 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Bill Wendling 2008-05-19 00:25:01 +00:00
parent 6acc8591d6
commit 40da626d23
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/tutorial/JITTutorial2.html
View File

@ -126,7 +126,15 @@ Module* makeLLVMModule() {
</pre>
</div>
<p><code>cond_false</code> is a more interesting block: we now know that <code>x != y</code>, so we must branch again to determine which of <code>x</code> and <code>y</code> is larger. This is achieved using the <code>ICmpULT</code> instruction, which stands for <em>integer comparison for unsigned less-than</em>. In LLVM, integer types do not carry sign; a 32-bit integer pseudo-register can interpreted as signed or unsigned without casting. Whether a signed or unsigned interpretation is desired is specified in the instruction. This is why several instructions in the LLVM IR, such as integer less-than, include a specifier for signed or unsigned.</p>
<p><code>cond_false</code> is a more interesting block: we now know that <code>x
!= y</code>, so we must branch again to determine which of <code>x</code>
and <code>y</code> is larger. This is achieved using the <code>ICmpULT</code>
instruction, which stands for <em>integer comparison for unsigned
less-than</em>. In LLVM, integer types do not carry sign; a 32-bit integer
pseudo-register can be interpreted as signed or unsigned without casting.
Whether a signed or unsigned interpretation is desired is specified in the
instruction. This is why several instructions in the LLVM IR, such as integer
less-than, include a specifier for signed or unsigned.</p>
<p>Also note that we're again making use of LLVM's automatic name uniquing, this time at a register level. We've deliberately chosen to name every instruction "tmp" to illustrate that LLVM will give them all unique names without getting confused.</p>