summaryrefslogtreecommitdiffstats
path: root/llvm/docs/tutorial/JITTutorial2.html
diff options
context:
space:
mode:
authorOwen Anderson <resistor@mac.com>2007-11-19 07:44:43 +0000
committerOwen Anderson <resistor@mac.com>2007-11-19 07:44:43 +0000
commit99057116f60505795c19151a7dab94abf50041be (patch)
treed89f23240b27903b85d8ff48856fd1223ff8885c /llvm/docs/tutorial/JITTutorial2.html
parent4205d25f06ba465c3e90fedf29dabfe2852e8853 (diff)
downloadbcm5719-llvm-99057116f60505795c19151a7dab94abf50041be.tar.gz
bcm5719-llvm-99057116f60505795c19151a7dab94abf50041be.zip
Fix a factually incorrect statement pointed out by Max Hailperin.
llvm-svn: 44228
Diffstat (limited to 'llvm/docs/tutorial/JITTutorial2.html')
-rw-r--r--llvm/docs/tutorial/JITTutorial2.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/tutorial/JITTutorial2.html b/llvm/docs/tutorial/JITTutorial2.html
index 06d0df1bde9..c28524e44a6 100644
--- a/llvm/docs/tutorial/JITTutorial2.html
+++ b/llvm/docs/tutorial/JITTutorial2.html
@@ -47,7 +47,7 @@ unsigned gcd(unsigned x, unsigned y) {
<p>The above is a graphical representation of a program in LLVM IR. It places each basic block on a node of a graph, and uses directed edges to indicate flow control. These blocks will be serialized when written to a text or bitcode file, but it is often useful conceptually to think of them as a graph. Again, if you are unsure about the code in the diagram, you should skim through the <a href="../LangRef.html">LLVM Language Reference Manual</a> and convince yourself that it is, in fact, the GCD algorithm.</p>
-<p>The first part of our code is the same as from first tutorial. The same basic setup is required: creating a module, verifying it, and running the <code>PrintModulePass</code> on it. Even the first segment of <code>makeLLVMModule()</code> looks the same, because <code>gcd</code> happens to have the same prototype as our <code>mul_add</code> function.</p>
+<p>The first part of our code is practically the same as from the first tutorial. The same basic setup is required: creating a module, verifying it, and running the <code>PrintModulePass</code> on it. Even the first segment of <code>makeLLVMModule()</code> looks essentially the same, except that <code>gcd</code> takes one more parameter than <code>mul_add</code>.</p>
<div class="doc_code">
<pre>
OpenPOWER on IntegriCloud