Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / llvm / 5339f85715f94fa237836fd6e6ddafd52c062dce / . / docs / tutorial / JITTutorial1.html
blob: 3bdc551d30628c9558f503af4a548d2c31f569b8 [file] [log] [blame]
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3
4<html>
5<head>
6 <title>LLVM Tutorial 1: A First Function</title>
7 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
8 <meta name="author" content="Owen Anderson">
9 <meta name="description"
10 content="LLVM Tutorial 1: A First Function.">
11 <link rel="stylesheet" href="../llvm.css" type="text/css">
12</head>
13
14<body>
15
16<div class="doc_title"> LLVM Tutorial 1: A First Function </div>
17
18<div class="doc_author">
19 <p>Written by <a href="mailto:owen@apple.com">Owen Anderson</a></p>
20</div>
21
Owen Andersonc333e4f2007-10-22 06:35:07 +0000[diff] [blame]22<!-- *********************************************************************** -->
Owen Andersonc333e4f2007-10-22 06:35:07 +0000[diff] [blame]23<div class="doc_section"><a name="intro">A First Function</a></div>
24<!-- *********************************************************************** -->
25
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]26<div class="doc_text">
27
28<p>For starters, lets consider a relatively straightforward function that takes three integer parameters and returns an arithmetic combination of them. This is nice and simple, especially since it involves no control flow:</p>
29
30<div class="doc_code">
31<pre>
Owen Anderson7d69c952007-10-20 05:41:39 +0000[diff] [blame]32int mul_add(int x, int y, int z) {
33 return x * y + z;
34}
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]35</pre>
36</div>
37
38<p>As a preview, the LLVM IR we’re going to end up generating for this function will look like:</p>
39
40<div class="doc_code">
41<pre>
Owen Anderson7d69c952007-10-20 05:41:39 +0000[diff] [blame]42define i32 @mul_add(i32 %x, i32 %y, i32 %z) {
43entry:
44 %tmp = mul i32 %x, %y
45 %tmp2 = add i32 %tmp, %z
46 ret i32 %tmp2
47}
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]48</pre>
49</div>
50
Owen Anderson0ec16ee2007-10-20 06:12:33 +0000[diff] [blame]51<p>If you're unsure what the above code says, skim through the <a href="../LangRef.html">LLVM Language Reference Manual</a> and convince yourself that the above LLVM IR is actually equivalent to the original function. Once you’re satisfied with that, let’s move on to actually generating it programmatically!</p>
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]52
53<p>... STUFF ABOUT HEADERS ... </p>
54
55<p>Now, let’s get started on our real program. Here’s what our basic <code>main()</code> will look like:</p>
56
57<div class="doc_code">
58<pre>
59using namespace llvm;
60
61Module* makeLLVMModule();
62
63int main(int argc, char**argv) {
64 Module* Mod = makeLLVMModule();
65
66 verifyModule(*Mod, PrintMessageAction);
67
68 PassManager PM;
69 PM.add(new PrintModulePass(&amp;llvm::cout));
70 PM.run(*Mod);
71
72 return 0;
73}
74</pre>
75</div>
76
77<p>The first segment is pretty simple: it creates an LLVM “module.” In LLVM, a module represents a single unit of code that is to be processed together. A module contains things like global variables and function declarations and implementations. Here, we’ve declared a <code>makeLLVMModule()</code> function to do the real work of creating the module. Don’t worry, we’ll be looking at that one next!</p>
78
79<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>
80
81<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>
82
Owen Anderson0ec16ee2007-10-20 06:12:33 +0000[diff] [blame]83<p>Now onto the interesting part: creating a populating a module. Here’s the first chunk of our <code>makeLLVMModule()</code>:</p>
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]84
85<div class="doc_code">
86<pre>
87Module* makeLLVMModule() {
88 // Module Construction
89 Module* mod = new Module("test");
90</pre>
91</div>
92
93<p>Exciting, isn’t it!? All we’re doing here is instantiating a module and giving it a name. The name isn’t particularly important unless you’re going to be dealing with multiple modules at once.</p>
94
95<div class="doc_code">
96<pre>
Owen Andersond2ae9a92007-10-22 06:29:31 +0000[diff] [blame]97 Constant* c = mod->getOrInsertFunction("mul_add",
98 /*ret type*/ IntegerType::get(32),
99 /*args*/ IntegerType::get(32),
100 IntegerType::get(32),
101 IntegerType::get(32),
102 /*varargs terminated with null*/ NULL);
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]103
Owen Anderson2d279f82007-10-20 05:40:47 +0000[diff] [blame]104 Function* mul_add = cast&lt;Function&gt;(c);
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]105 mul_add->setCallingConv(CallingConv::C);
106</pre>
107</div>
108
Owen Anderson2d279f82007-10-20 05:40:47 +0000[diff] [blame]109<p>We construct our <code>Function</code> by calling <code>getOrInsertFunction()</code> on our module, passing in the name, return type, and argument types of the function. In the case of our <code>mul_add</code> function, that means one 32-bit integer for the return value, and three 32-bit integers for the arguments.</p>
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]110
Owen Anderson2d279f82007-10-20 05:40:47 +0000[diff] [blame]111<p>You'll notice that <code>getOrInsertFunction</code> doesn't actually return a <code>Function*</code>. This is because, if the function already existed, but with a different prototype, <code>getOrInsertFunction</code> will return a cast of the existing function to the desired 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>.
112
113<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>
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]114
115<div class="doc_code">
116<pre>
117 Function::arg_iterator args = mul_add->arg_begin();
118 Value* x = args++;
119 x->setName("x");
120 Value* y = args++;
121 y->setName("y");
122 Value* z = args++;
123 z->setName("z");
124</pre>
125</div>
126
127<p>While we’re setting up our function, let’s also give names to the parameters. This also isn’t strictly necessary (LLVM will generate names for them if you don’t specify them), but it’ll make looking at our output somewhat more pleasant. To name the parameters, we iterator over the arguments of our function, and call <code>setName()</code> on them. We’ll also keep the pointer to <code>x</code>, <code>y</code>, and <code>z</code> around, since we’ll need them when we get around to creating instructions.</p>
128
129<p>Great! We have a function now. But what good is a function if it has no body? Before we start working on a body for our new function, we need to recall some details of the LLVM IR. The IR, being an abstract assembly language, represents control flow using jumps (we call them branches), both conditional and unconditional. The straight-line sequences of code between branches are called basic blocks, or just blocks. To create a body for our function, we fill it with blocks!</p>
130
131<div class="doc_code">
132<pre>
133 BasicBlock* block = new BasicBlock("entry", mul_add);
134 LLVMBuilder builder(block);
135</pre>
136</div>
137
138<p>We create a new basic block, as you might expect, by calling its constructor. All we need to tell it is its name and the function to which it belongs. In addition, we’re creating an <code>LLVMBuilder</code> object, which is a convenience interface for creating instructions and appending them to the end of a block. Instructions can be created through their constructors as well, but some of their interfaces are quite complicated. Unless you need a lot of control, using <code>LLVMBuilder</code> will make your life simpler.</p>
139
140<div class="doc_code">
141<pre>
142 Value* tmp = builder.CreateBinOp(Instruction::Mul,
143 x, y, "tmp");
144 Value* tmp2 = builder.CreateBinOp(Instruction::Add,
145 tmp, z, "tmp2");
146
147 builder.CreateRet(tmp2);
Owen Andersond2ae9a92007-10-22 06:29:31 +0000[diff] [blame]148
149 return mod;
Owen Anderson6f1fd942007-10-20 05:23:06 +0000[diff] [blame]150}
151</pre>
152</div>
153
154<p>The final step in creating our function is to create the instructions that make it up. Our <code>mul_add</code> function is composed of just three instructions: a multiply, an add, and a return. <code>LLVMBuilder</code> gives us a simple interface for constructing these instructions and appending them to the “entry” block. Each of the calls to <code>LLVMBuilder</code> returns a <code>Value*</code> that represents the value yielded by the instruction. You’ll also notice that, above, <code>x</code>, <code>y</code>, and <code>z</code> are also <code>Value*</code>’s, so it’s clear that instructions operate on <code>Value*</code>’s.</p>
155
156<p>And that’s it! Now you can compile and run your code, and get a wonder textual print out of the LLVM IR we saw at the beginning.</p>
157
158<p> ... SECTION ABOUT USING llvm-config TO GET THE NECESSARY COMPILER FLAGS TO COMPILE YOUR CODE ... </p>
159
160</div>
161
162</body>
163</html>