6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-11-02 07:11:49 +00:00
Code Issues Projects Releases Wiki Activity

s/insure/ensure/

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51232 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Bill Wendling 2008-05-19 00:05:30 +00:00
parent 3d738ca7ea
commit c8968d99c6
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/tutorial/JITTutorial1.html
View File

@ -90,9 +90,16 @@ int main(int argc, char**argv) {
<p>The second segment runs the LLVM module verifier on our newly created module. While this probably isn’t really necessary for a simple module like this one, it’s always a good idea, especially if you’re generating LLVM IR based on some input. The verifier will print an error message if your LLVM module is malformed in any way.</p>
<p>Finally, we instantiate an LLVM <code>PassManager</code> and run the <code>PrintModulePass</code> on our module. LLVM uses an explicit pass infrastructure to manage optimizations and various other things. A <code>PassManager</code>, as should be obvious from its name, manages passes: it is responsible for scheduling them, invoking them, and insuring the proper disposal after we’re done with them. For this example, we’re just using a trivial pass that prints out our module in textual form.</p>
<p>Finally, we instantiate an LLVM <code>PassManager</code> and run
the <code>PrintModulePass</code> on our module. LLVM uses an explicit pass
infrastructure to manage optimizations and various other things.
A <code>PassManager</code>, as should be obvious from its name, manages passes:
it is responsible for scheduling them, invoking them, and ensuring the proper
disposal after we’re done with them. For this example, we’re just using a
trivial pass that prints out our module in textual form.</p>
<p>Now onto the interesting part: creating and populating a module. Here’s the first chunk of our <code>makeLLVMModule()</code>:</p>
<p>Now onto the interesting part: creating and populating a module. Here’s the
first chunk of our <code>makeLLVMModule()</code>:</p>
<div class="doc_code">
<pre>
@ -122,7 +129,9 @@ Module* makeLLVMModule() {
<p>You'll notice that <code>getOrInsertFunction()</code> doesn't actually return a <code>Function*</code>. This is because <code>getOrInsertFunction()</code> will return a cast of the existing function if the function already existed with a different prototype. Since we know that there's not already a <code>mul_add</code> function, we can safely just cast <code>c</code> to a <code>Function*</code>.
<p>In addition, we set the calling convention for our new function to be the C calling convention. This isn’t strictly necessary, but it insures that our new function will interoperate properly with C code, which is a good thing.</p>
<p>In addition, we set the calling convention for our new function to be the C
calling convention. This isn’t strictly necessary, but it ensures that our new
function will interoperate properly with C code, which is a good thing.</p>
<div class="doc_code">
<pre>