blob: 8c59e3e3014bae982eca5d89c70be0a6584692ca [file] [log] [blame]
Misha Brukman560e9892003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shib65a78e2002-07-17 23:05:56 +00003<html>
Misha Brukman560e9892003-11-07 19:43:14 +00004<head>
Reid Spencer38fcf302004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman560e9892003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
Daniel Dunbar46d611a2012-04-19 20:20:34 +00007 <link rel="stylesheet" href="_static/llvm.css" type="text/css">
Misha Brukman560e9892003-11-07 19:43:14 +00008</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +000010
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000011<h1>
Misha Brukman560e9892003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000013</h1>
John Criswell72989a52003-06-12 19:34:44 +000014
Misha Brukman560e9892003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +000019 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000023 </ol></li>
John Criswell3ef61af2003-06-30 21:59:07 +000024
Misha Brukman560e9892003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell71139f22003-07-08 20:35:59 +000026 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000032 <li><a href="#config">Local LLVM Configuration</a></li>
33 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
34 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
35 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
36 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000037 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +000038
Misha Brukman560e9892003-11-07 19:43:14 +000039 <li><a href="#layout">Program layout</a>
40 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000041 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
42 <li><a href="#include"><tt>llvm/include</tt></a></li>
43 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
44 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
45 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
46 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trick68aa18e42010-09-23 20:26:44 +000047 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000048 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
49 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000050 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +000051
Misha Brukman560e9892003-11-07 19:43:14 +000052 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000053 <ol>
Chad Rosier233f1472012-02-26 21:31:25 +000054 <li><a href="#tutorial4">Example with Clang</a></li>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000055 </ol>
Misha Brukman560e9892003-11-07 19:43:14 +000056 <li><a href="#problems">Common Problems</a>
57 <li><a href="#links">Links</a>
58</ul>
59
Chris Lattner020e1fc2004-05-23 21:07:27 +000060<div class="doc_author">
61 <p>Written by:
62 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
63 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +000064 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner020e1fc2004-05-23 21:07:27 +000065 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
66 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
67 </p>
68</div>
Misha Brukman560e9892003-11-07 19:43:14 +000069
70
71<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000072<h2>
73 <a name="overview">Overview</a>
74</h2>
Misha Brukman560e9892003-11-07 19:43:14 +000075<!-- *********************************************************************** -->
76
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +000077<div>
Misha Brukman560e9892003-11-07 19:43:14 +000078
79<p>Welcome to LLVM! In order to get started, you first need to know some
80basic information.</p>
81
Andrew Trick68aa18e42010-09-23 20:26:44 +000082<p>First, LLVM comes in three pieces. The first piece is the LLVM
83suite. This contains all of the tools, libraries, and header files
Jim Grosbach65e24652012-01-25 22:00:23 +000084needed to use LLVM. It contains an assembler, disassembler, bitcode
85analyzer and bitcode optimizer. It also contains basic regression tests that
Chad Rosier233f1472012-02-26 21:31:25 +000086can be used to test the LLVM tools and the Clang front end.</p>
Misha Brukman560e9892003-11-07 19:43:14 +000087
Chad Rosier690a2b02012-02-26 21:34:02 +000088<p>The second piece is the <a href="http://clang.llvm.org/">Clang</a> front end.
89This component compiles C, C++, Objective C, and Objective C++ code into LLVM
90bitcode. Once compiled into LLVM bitcode, a program can be manipulated with the
91LLVM tools from the LLVM suite.
Chad Rosier233f1472012-02-26 21:31:25 +000092</p>
Misha Brukman560e9892003-11-07 19:43:14 +000093
John Criswell6ab273c2004-12-08 17:53:54 +000094<p>
Andrew Trick68aa18e42010-09-23 20:26:44 +000095There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell6ab273c2004-12-08 17:53:54 +000096with a testing harness that can be used to further test LLVM's functionality
97and performance.
98</p>
99
Misha Brukman560e9892003-11-07 19:43:14 +0000100</div>
101
102<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000103<h2>
104 <a name="quickstart">Getting Started Quickly (A Summary)</a>
105</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000106<!-- *********************************************************************** -->
107
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000108<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000109
Chad Rosier2270b002012-02-26 22:12:59 +0000110<p>The LLVM Getting Started documentation may be out of date. So, the Clang
111<a href="http://clang.llvm.org/get_started.html">Getting Started</a> page might
112also be a good place to start.</p>
Chad Rosier6e220d52012-02-23 21:23:24 +0000113
Misha Brukman560e9892003-11-07 19:43:14 +0000114<p>Here's the short story for getting up and running quickly with LLVM:</p>
115
116<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000117 <li>Read the documentation.</li>
118 <li>Read the documentation.</li>
119 <li>Remember that you were warned twice about reading the documentation.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000120
Chad Rosier2270b002012-02-26 22:12:59 +0000121 <li>Checkout LLVM:
Misha Brukman560e9892003-11-07 19:43:14 +0000122 <ul>
Chad Rosier2270b002012-02-26 22:12:59 +0000123 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
124 <li><tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
125 </ul>
126 </li>
Misha Brukman560e9892003-11-07 19:43:14 +0000127
Chad Rosier2270b002012-02-26 22:12:59 +0000128 <li>Checkout Clang:
John Criswelldfe6a862004-12-10 15:51:16 +0000129 <ul>
Chad Rosier2270b002012-02-26 22:12:59 +0000130 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
131 <li><tt>cd llvm/tools</tt>
132 <li><tt>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang</tt></li>
133 </ul>
134 </li>
John Criswelldfe6a862004-12-10 15:51:16 +0000135
Chad Rosier2270b002012-02-26 22:12:59 +0000136 <li>Checkout Compiler-RT:
137 <ul>
138 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
139 <li><tt>cd llvm/projects</tt>
140 <li><tt>svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk
141 compiler-rt</tt></li>
142 </ul>
143 </li>
John Criswelldfe6a862004-12-10 15:51:16 +0000144
Chad Rosier2270b002012-02-26 22:12:59 +0000145 <li>Get the Test Suite Source Code <b>[Optional]</b>
146 <ul>
147 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
148 <li><tt>cd llvm/projects</tt>
149 <li><tt>svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite</tt></li>
150 </ul>
151 </li>
John Criswelldfe6a862004-12-10 15:51:16 +0000152
Chad Rosier2270b002012-02-26 22:12:59 +0000153 <li>Configure and build LLVM and Clang:
154 <ul>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000155 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
Chad Rosier2270b002012-02-26 22:12:59 +0000156 <li><tt>mkdir build</tt> (for building without polluting the source dir)</li>
157 <li><tt>cd build</tt></li>
NAKAMURA Takumic9d9b922012-03-27 11:25:16 +0000158 <li><tt>../llvm/configure [options]</tt>
159 <br>Some common options:
Misha Brukman20b8a6562005-02-03 22:25:23 +0000160
Misha Brukman560e9892003-11-07 19:43:14 +0000161 <ul>
Chad Rosier2270b002012-02-26 22:12:59 +0000162 <li><tt>--prefix=<i>directory</i></tt> -
163 Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000164 want the LLVM tools and libraries to be installed (default
Chad Rosier2270b002012-02-26 22:12:59 +0000165 <tt>/usr/local</tt>).</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000166 </ul>
Misha Brukman560e9892003-11-07 19:43:14 +0000167
Chad Rosier2270b002012-02-26 22:12:59 +0000168 <ul>
169 <li><tt>--enable-optimized</tt> -
170 Compile with optimizations enabled (default is NO).</li>
171 </ul>
172
173 <ul>
174 <li><tt>--enable-assertions</tt> -
175 Compile with assertion checks enabled (default is YES).</li>
176 </ul>
NAKAMURA Takumic9d9b922012-03-27 11:25:16 +0000177 </li>
Chad Rosier2270b002012-02-26 22:12:59 +0000178 <li><tt>make [-j]</tt> - The -j specifies the number of jobs (commands) to
179 run simultaneously. This builds both LLVM and Clang for Debug+Asserts mode.
180 The --enabled-optimized configure option is used to specify a Release build.</li>
181 <li><tt>make check-all</tt> -
182 This run the regression tests to ensure everything is in working order.</li>
183 <li><tt>make update</tt> -
184 This command is used to update all the svn repositories at once, rather then
185 having to <tt>cd</tt> into the individual repositories and running
186 <tt>svn update</tt>.</li>
187 <li>It is also possible to use CMake instead of the makefiles. With CMake
188 it is also possible to generate project files for several IDEs: Eclipse
189 CDT4, CodeBlocks, Qt-Creator (use the CodeBlocks generator), KDevelop3.</li>
190 <li>If you get an "internal compiler error (ICE)" or test failures, see
191 <a href="#brokengcc">below</a>.</li>
192
193 </ul>
194 </li>
Misha Brukman560e9892003-11-07 19:43:14 +0000195
196</ol>
197
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000198<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000199detailed information on configuring and compiling LLVM. See <a
200href="#environment">Setting Up Your Environment</a> for tips that simplify
Chad Rosierce50eec2012-02-26 22:26:37 +0000201working with the Clang front end and LLVM tools. Go to <a href="#layout">Program
Misha Brukman560e9892003-11-07 19:43:14 +0000202Layout</a> to learn about the layout of the source code tree.</p>
203
204</div>
205
206<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000207<h2>
208 <a name="requirements">Requirements</a>
209</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000210<!-- *********************************************************************** -->
211
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000212<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000213
214<p>Before you begin to use the LLVM system, review the requirements given below.
215This may save you some trouble by knowing ahead of time what hardware and
216software you will need.</p>
217
Misha Brukman560e9892003-11-07 19:43:14 +0000218<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000219<h3>
220 <a name="hardware">Hardware</a>
221</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000222
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000223<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000224
225<p>LLVM is known to work on the following platforms:</p>
226
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000227<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000228<tr>
229 <th>OS</th>
230 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000231 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000232</tr>
233<tr>
Chris Lattner6bad1372009-07-22 04:21:40 +0000234 <td>AuroraUX</td>
235 <td>x86<sup><a href="#pf_1">1</a></sup></td>
236 <td>GCC</td>
Chris Lattner3a56ae82009-07-21 22:47:03 +0000237</tr>
238<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000239 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000240 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000241 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000242</tr>
243<tr>
Edward O'Callaghanab8a04c2009-08-04 05:24:28 +0000244 <td>Linux</td>
245 <td>amd64</td>
246 <td>GCC</td>
247</tr>
248<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000249 <td>Solaris</td>
250 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000251 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000252</tr>
253<tr>
254 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000255 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000256 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000257</tr>
258<tr>
Bill Wendling5d32b702010-12-15 01:35:55 +0000259 <td>FreeBSD</td>
260 <td>amd64</td>
261 <td>GCC</td>
262</tr>
263<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000264 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000265 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000266 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000267</tr>
268<tr>
Scott Michel4799ea72008-03-18 23:13:26 +0000269 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000270 <td>x86</td>
271 <td>GCC</td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000272</tr>
273<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000274 <td>Cygwin/Win32</td>
Anton Korobeynikovd0a0bc32009-12-09 17:26:02 +0000275 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
276 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000277 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000278</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000279<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000280 <td>MinGW/Win32</td>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000281 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000282 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
283 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000284 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000285</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000286</table>
287
288<p>LLVM has partial support for the following platforms:</p>
289
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000290<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000291<tr>
292 <th>OS</th>
293 <th>Arch</th>
294 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000295</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000296<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000297 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000298 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruthd1eafe12011-11-16 19:52:13 +0000299 <td>Visual Studio 2008 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000300<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000301 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000302 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000303 <td>GCC</td>
304</tr>
305<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000306 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000307 <td>PowerPC</td>
308 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000309</tr>
John Criswell05990f32005-05-09 16:49:59 +0000310
311<tr>
312 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
313 <td>Alpha</td>
314 <td>GCC</td>
315</tr>
316<tr>
317 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
318 <td>Itanium (IA-64)</td>
319 <td>GCC</td>
320</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000321<tr>
322 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
323 <td>Itanium (IA-64)</td>
324 <td>HP aCC</td>
325</tr>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000326<tr>
327 <td>Windows x64</td>
328 <td>x86-64</td>
329 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
330</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000331</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000332
Misha Brukman77723092005-02-09 21:01:26 +0000333<p><b>Notes:</b></p>
334
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000335<div class="doc_notes">
336<ol>
337<li><a name="pf_1">Code generation supported for Pentium processors and
338up</a></li>
339<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
340<li><a name="pf_3">No native code generation</a></li>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000341<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000342<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattnerb7481cf2009-01-02 07:10:51 +0000343<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell05990f32005-05-09 16:49:59 +0000344<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000345<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
346 generated by LLVM properly.</a></li>
Jean-Daniel Dupas81b82a02012-05-13 14:36:15 +0000347<li><a name="pf_9">Xcode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel4799ea72008-03-18 23:13:26 +0000348 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner26c74442008-11-09 17:19:14 +0000349 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
350 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel4799ea72008-03-18 23:13:26 +0000351 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000352<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
353 version of the perl package, and be sure it appears in your path
354 before any Windows-based versions such as Strawberry Perl and
355 ActivePerl, as these have Windows-specifics that will cause the
356 build to fail.</a></li>
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000357<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000358 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000359<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000360 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukman77723092005-02-09 21:01:26 +0000361</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000362</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000363
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000364<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswelle1a81202005-05-18 19:43:33 +0000365mode, depending on the system (it is so large because of all the debugging
366information and the fact that the libraries are statically linked into multiple
Chris Lattner0cb89772009-04-25 22:08:52 +0000367tools). If you do not need many of the tools and you are space-conscious, you
368can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
369requires considerably less space.</p>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000370
Misha Brukman560e9892003-11-07 19:43:14 +0000371<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
372guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greifa54634a2007-07-06 22:07:22 +0000373able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman560e9892003-11-07 19:43:14 +0000374generation should work as well, although the generated native code may not work
375on your platform.</p>
376
Misha Brukman560e9892003-11-07 19:43:14 +0000377</div>
378
379<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000380<h3>
381 <a name="software">Software</a>
382</h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000383<div>
Reid Spencer38fcf302004-11-15 21:15:12 +0000384 <p>Compiling LLVM requires that you have several software packages
385 installed. The table below lists those required packages. The Package column
386 is the usual name for the software package that LLVM depends on. The Version
387 column provides "known to work" versions of the package. The Notes column
388 describes how LLVM uses the package and provides other details.</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000389 <table summary="Packages required to compile LLVM">
Reid Spencer38fcf302004-11-15 21:15:12 +0000390 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000391
Reid Spencer38fcf302004-11-15 21:15:12 +0000392 <tr>
393 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
394 <td>3.79, 3.79.1</td>
395 <td>Makefile/build processor</td>
396 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000397
Reid Spencer38fcf302004-11-15 21:15:12 +0000398 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000399 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000400 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000401 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000402 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000403
Reid Spencer38fcf302004-11-15 21:15:12 +0000404 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000405 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000406 <td>4.5</td>
407 <td>For building the CFE</td>
408 </tr>
409
410 <tr>
John Criswell58594852007-06-29 19:12:31 +0000411 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
412 <td>&ge;1.3</td>
413 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000414 </tr>
415
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +0000416 <!-- FIXME:
417 Do we support dg?
418 Are DejaGnu and expect obsolete?
419 Shall we mention Python? -->
420
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000421 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000422 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
423 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000424 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000425 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000426
Reid Spencer38fcf302004-11-15 21:15:12 +0000427 <tr>
428 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
429 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000430 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000431 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000432
Reid Spencer38fcf302004-11-15 21:15:12 +0000433 <tr>
434 <td><a href="http://expect.nist.gov/">expect</a></td>
435 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000436 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000437 </tr>
438
439 <tr>
440 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000441 <td>&ge;5.6.0</td>
Daniel Dunbar06b68122012-02-15 19:24:11 +0000442 <td>Utilities</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000443 </tr>
444
445 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000446 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
447 <td>1.4</td>
448 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000449 </tr>
450
451 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000452 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000453 <td>2.60</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000454 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
455 </tr>
456
457 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000458 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000459 <td>1.9.6</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000460 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
461 </tr>
462
463 <tr>
464 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000465 <td>1.5.22</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000466 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000467 </tr>
468
469 </table>
470
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000471 <p><b>Notes:</b></p>
472 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000473 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000474 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000475 need to build the other languages for LLVM's purposes.</a> See
476 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell58594852007-06-29 19:12:31 +0000477 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000478 latest LLVM sources. If you're working from a release distribution, you
John Criswell58594852007-06-29 19:12:31 +0000479 don't need Subversion.</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000480 <li><a name="sf3">Only needed if you want to run the automated test
481 suite in the <tt>llvm/test</tt> directory.</a></li>
482 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser4518c862010-05-19 07:00:17 +0000483 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
484 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer098fce42004-12-09 17:55:37 +0000485 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000486 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000487 </div>
488
Reid Spencer38fcf302004-11-15 21:15:12 +0000489 <p>Additionally, your compilation host is expected to have the usual
490 plethora of Unix utilities. Specifically:</p>
491 <ul>
492 <li><b>ar</b> - archive library builder</li>
493 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
494 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
495 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000496 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000497 <li><b>cp</b> - copy files</li>
498 <li><b>date</b> - print the current date/time </li>
499 <li><b>echo</b> - print to standard output</li>
500 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000501 <li><b>find</b> - find files/dirs in a file system</li>
502 <li><b>grep</b> - regular expression search utility</li>
503 <li><b>gzip*</b> - gzip command for distribution generation</li>
504 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
505 <li><b>install</b> - install directories/files </li>
506 <li><b>mkdir</b> - create a directory</li>
507 <li><b>mv</b> - move (rename) files</li>
508 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000509 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000510 <li><b>sed</b> - stream editor for transforming output</li>
511 <li><b>sh</b> - Bourne shell for make build scripts</li>
512 <li><b>tar</b> - tape archive for distribution generation</li>
513 <li><b>test</b> - test things in file system</li>
514 <li><b>unzip*</b> - unzip command for distribution checking</li>
515 <li><b>zip*</b> - zip command for distribution generation</li>
516 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000517</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000518
Chris Lattnere0050f02004-07-18 22:32:22 +0000519<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000520<h3>
Chris Lattner55514822007-06-19 05:52:36 +0000521 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000522</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000523
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000524<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000525
526<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
527bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenekaff36402011-10-31 21:23:15 +0000528to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
529Other versions of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000530here are known to not work. If you are using one of these versions, please try
531to upgrade your GCC to something more recent. If you run into a problem with a
532version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
533us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
534of GCC you are using.
535</p>
536
537<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
538problems in the STL that effectively prevent it from compiling LLVM.
539</p>
540
Chris Lattner419df4e2008-02-13 17:50:24 +0000541<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
542a bogus template error. This was fixed in later GCCs.</p>
John Criswellfd769452004-11-23 22:06:24 +0000543
Chris Lattnere0050f02004-07-18 22:32:22 +0000544<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
545href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
546the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000547
Chris Lattner58247622005-02-13 22:20:49 +0000548<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Chad Rosierce50eec2012-02-26 22:26:37 +0000549 Cygwin does not work.</p>
Chris Lattner58247622005-02-13 22:20:49 +0000550<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
551 possibly others) does not compile LLVM correctly (it appears that exception
552 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
553 to a newer version of GCC.</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000554<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000555 code generator, causing an infinite loop in the llvm-gcc build when built
556 with optimizations enabled (i.e. a release build).</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000557<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000558 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
559 correctly compiles LLVM at -O2. A work around is to build release LLVM
560 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000561<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner489ad332007-04-01 20:14:46 +0000562 miscompiles portions of LLVM</a>.</p>
Chris Lattner059a8df2007-11-01 04:20:16 +0000563<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
564 when building with optimizations enabled. It appears to work with
565 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
566 build.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000567<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
568 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000569<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
570 default with ENABLE_OPTIMIZED=1. To work around this, build with
571 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000572<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
573 compiling some files. At the time of this writing, GCC mainline (4.2)
574 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000575<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
576 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
577 code. LLVM will appear to mostly work but will be buggy, e.g. failing
578 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000579<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
580platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbar2a575452008-10-11 18:40:33 +0000581<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
582to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
583about symbols remaining in the table on destruction.</p>
Nuno Lopes94993852008-12-10 16:11:10 +0000584<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes65e877e2008-12-10 16:01:22 +0000585as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Anton Korobeynikovdad58712009-05-04 10:24:46 +0000586<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
587 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
588 with link errors when using this GCC version.</p>
Chris Lattnereba6c722009-09-10 16:25:02 +0000589<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewyckyd562ab12009-07-17 06:32:10 +0000590<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
591when optimizations are turned on. The symptom is an infinite loop in
Chris Lattnereba6c722009-09-10 16:25:02 +0000592FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewyckyabe8c132010-10-07 22:30:47 +0000593<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5941</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
595one symptom of the problem.
Reid Spencer6291ddc2006-11-04 00:33:42 +0000596<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
597long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
598defined in a discarded section. You can safely ignore these messages as they are
599erroneous and the linkage is correct. These messages disappear using ld
6002.17.</p>
Chris Lattner55514822007-06-19 05:52:36 +0000601
602<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
603href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
604causes huge link times (minutes instead of seconds) when building LLVM. We
605recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
606
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000607<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewycky2db07612009-02-25 06:29:47 +0000608<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
609which causes intermittent failures when building LLVM with position independent
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000610code. The symptom is an error about cyclic dependencies. We recommend
611upgrading to a newer version of Gold.</p>
Nick Lewycky2db07612009-02-25 06:29:47 +0000612
Misha Brukman560e9892003-11-07 19:43:14 +0000613</div>
614
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000615</div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000616
Misha Brukman560e9892003-11-07 19:43:14 +0000617<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000618<h2>
619 <a name="starting">Getting Started with LLVM</a>
620</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000621<!-- *********************************************************************** -->
622
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000623<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000624
625<p>The remainder of this guide is meant to get you up and running with
626LLVM and to give you some basic information about the LLVM environment.</p>
627
628<p>The later sections of this guide describe the <a
629href="#layout">general layout</a> of the the LLVM source tree, a <a
630href="#tutorial">simple example</a> using the LLVM tool chain, and <a
631href="#links">links</a> to find more information about LLVM or to get
632help via e-mail.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000633
Misha Brukman560e9892003-11-07 19:43:14 +0000634<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000635<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000636 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000637</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000638
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000639<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000640
641<p>Throughout this manual, the following names are used to denote paths
642specific to the local system and working environment. <i>These are not
643environment variables you need to set but just strings used in the rest
644of this document below</i>. In any of the examples below, simply replace
645each of these names with the appropriate pathname on your local system.
646All these paths are absolute:</p>
647
Misha Brukmand3de5c62004-01-20 00:20:17 +0000648<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000649 <dt>SRC_ROOT
650 <dd>
651 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000652 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000653
Misha Brukman560e9892003-11-07 19:43:14 +0000654 <dt>OBJ_ROOT
655 <dd>
656 This is the top level directory of the LLVM object tree (i.e. the
657 tree where object files and compiled programs will be placed. It
658 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000659 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000660
Misha Brukman560e9892003-11-07 19:43:14 +0000661</dl>
662
663</div>
664
665<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000666<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000667 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000668</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000669
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000670<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000671
672<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000673In order to compile and use LLVM, you may need to set some environment
674variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000675
Misha Brukmand3de5c62004-01-20 00:20:17 +0000676<dl>
Gabor Greifa54634a2007-07-06 22:07:22 +0000677 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000678 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greifa54634a2007-07-06 22:07:22 +0000679 locations of your bitcode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000680 convenience since you can specify the paths using the -L options of the
Gabor Greifa54634a2007-07-06 22:07:22 +0000681 tools and the C/C++ front-end will automatically use the bitcode files
John Criswelle1a81202005-05-18 19:43:33 +0000682 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000683 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000684</dl>
685
686</div>
687
688<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000689<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000690 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000691</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000692
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000693<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000694
695<p>
696If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000697can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000698suite and the LLVM GCC front end compiled for your platform. There is an
699additional test suite that is optional. Each file is a TAR archive that is
700compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000701</p>
702
Misha Brukmand4528ea2005-02-02 18:01:57 +0000703<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000704<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000705 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukman21a63702008-12-11 18:23:24 +0000706 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000707
Misha Brukmand4528ea2005-02-02 18:01:57 +0000708 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000709 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000710
Misha Brukman4050d152008-12-29 19:38:58 +0000711 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
712 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukman21a63702008-12-11 18:23:24 +0000713 directory for build instructions.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000714
Misha Brukman4050d152008-12-29 19:38:58 +0000715 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
716 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000717
Misha Brukman560e9892003-11-07 19:43:14 +0000718</dl>
719
720</div>
721
722<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000723<h3>
John Criswell58594852007-06-29 19:12:31 +0000724 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000725</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000726
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000727<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000728
John Criswell58594852007-06-29 19:12:31 +0000729<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattner1c1595f2009-04-25 22:24:49 +0000730the entire source code. All you need to do is check it out from Subversion as
Misha Brukman560e9892003-11-07 19:43:14 +0000731follows:</p>
732
733<ul>
John Criswell58594852007-06-29 19:12:31 +0000734 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov4c04a93332007-06-29 20:56:49 +0000735 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
736 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell58594852007-06-29 19:12:31 +0000737 llvm</tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000738</ul>
739
John Criswell58594852007-06-29 19:12:31 +0000740
Misha Brukman560e9892003-11-07 19:43:14 +0000741<p>This will create an '<tt>llvm</tt>' directory in the current
742directory and fully populate it with the LLVM source code, Makefiles,
743test directories, and local copies of documentation files.</p>
744
Misha Brukmand3de5c62004-01-20 00:20:17 +0000745<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikoveaa836b2007-06-29 23:13:42 +0000746revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikov09ca62d2007-06-30 00:00:57 +0000747'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman52757bf2008-12-17 16:27:23 +0000748subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000749
John Criswell86a3a482003-12-18 16:43:17 +0000750<ul>
Bill Wendlingdb624242011-04-04 23:42:51 +0000751<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc4735872010-10-06 23:50:30 +0000752<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner3d7ec7b2010-10-06 05:36:01 +0000753<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattner9d3ba88b2009-10-23 06:20:06 +0000754<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000755<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman52757bf2008-12-17 16:27:23 +0000756<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattner610e89d2008-06-09 06:02:09 +0000757<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattner779593c2008-02-12 02:42:55 +0000758<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner586eb8e2007-09-28 22:50:54 +0000759<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000760<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000761<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000762<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000763<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000764<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000765<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000766<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000767<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000768<li>Release 1.2: <b>RELEASE_12</b></li>
769<li>Release 1.1: <b>RELEASE_11</b></li>
770<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000771</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000772
Reid Spencerdfcf7902004-12-08 16:51:31 +0000773<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell58594852007-06-29 19:12:31 +0000774you get it from the Subversion repository:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000775
776<div class="doc_code">
Reid Spencerdfcf7902004-12-08 16:51:31 +0000777<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000778% cd llvm/projects
Andrew Trick68aa18e42010-09-23 20:26:44 +0000779% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencerdfcf7902004-12-08 16:51:31 +0000780</pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000781</div>
782
Reid Spencerdfcf7902004-12-08 16:51:31 +0000783<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000784configured by the LLVM configure script as well as automatically updated when
John Criswell58594852007-06-29 19:12:31 +0000785you run <tt>svn update</tt>.</p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000786
Misha Brukman560e9892003-11-07 19:43:14 +0000787</div>
788
789<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000790<h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000791 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000792</h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000793
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000794<div>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000795
796<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
797 sync automatically with each Subversion commit and contain all necessary
798 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
799 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000800 read-only GIT clone of LLVM via:</p>
801
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000802<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000803git clone http://llvm.org/git/llvm.git
804</pre>
805
806<p>If you want to check out clang too, run:</p>
807
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000808<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000809git clone http://llvm.org/git/llvm.git
810cd llvm/tools
811git clone http://llvm.org/git/clang.git
812</pre>
813
NAKAMURA Takumid92a5fe2011-08-12 07:48:01 +0000814<p>
815Since the upstream repository is in Subversion, you should use
816<tt>&quot;git pull --rebase&quot;</tt>
817instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
818history in your clone.
819To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
820on the master branch, run the following command:
821</p>
822
823<pre class="doc_code">
824git config branch.master.rebase true
825</pre>
826
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000827<h4>Sending patches with Git</h4>
828<div>
829<p>
830Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
831</p>
832
833<p>
834Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
835working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
836At first you may check sanity of whitespaces:
837</p>
838
839<pre class="doc_code">
840git diff --check master..mybranch
841</pre>
842
843<p>
844The easiest way to generate a patch is as below:
845</p>
846
847<pre class="doc_code">
848git diff master..mybranch &gt; /path/to/mybranch.diff
849</pre>
850
851<p>
852It is a little different from svn-generated diff. git-diff-generated diff has
853prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
854know it could be accepted with <tt>patch -p1 -N</tt>.
855</p>
856
857<p>
858But you may generate patchset with git-format-patch. It generates
859by-each-commit patchset. To generate patch files to attach to your article:
860</p>
861
862<pre class="doc_code">
863git format-patch --no-attach master..mybranch -o /path/to/your/patchset
864</pre>
865
866<p>
867If you would like to send patches directly, you may use git-send-email or
868git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
869</p>
870
871<pre class="doc_code">
872git format-patch --attach master..mybranch --stdout | git imap-send
873</pre>
874
875<p>
876Then, your .git/config should have [imap] sections.
877</p>
878
879<pre class="doc_code">
880[imap]
881 host = imaps://imap.gmail.com
882 user = <em>your.gmail.account</em>@gmail.com
883 pass = <em>himitsu!</em>
884 port = 993
885 sslverify = false
886; in English
887 folder = "[Gmail]/Drafts"
888; example for Japanese, "Modified UTF-7" encoded.
889 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumia61f0cc2011-11-06 06:51:58 +0000890; example for Traditional Chinese
891 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000892</pre>
893
894</div>
895
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000896<h4>For developers to work with git-svn</h4>
897<div>
898
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000899<p>To set up clone from which you can submit code using
900 <tt>git-svn</tt>, run:</p>
901
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000902<pre class="doc_code">
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000903git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000904cd llvm
905git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
906git config svn-remote.svn.fetch :refs/remotes/origin/master
907git svn rebase -l # -l avoids fetching ahead of the git mirror.
908
909# If you have clang too:
910cd tools
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000911git clone http://llvm.org/git/clang.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000912cd clang
913git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
914git config svn-remote.svn.fetch :refs/remotes/origin/master
915git svn rebase -l
916</pre>
917
918<p>To update this clone without generating git-svn tags that conflict
919with the upstream git repo, run:</p>
920
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000921<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000922git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
923git checkout master
924git svn rebase -l
925(cd tools/clang &&
926 git checkout master &&
927 git svn rebase -l)
928</pre>
929
930<p>This leaves your working directories on their master branches, so
931you'll need to <tt>checkout</tt> each working branch individually and
932<tt>rebase</tt> it on top of its parent branch. (Note: This script is
933intended for relative newbies to git. If you have more experience,
934you can likely improve on it.)</p>
935
936<p>The git-svn metadata can get out of sync after you mess around with
937branches and <code>dcommit</code>. When that happens, <code>git svn
938dcommit</code> stops working, complaining about files with uncommitted
939changes. The fix is to rebuild the metadata:</p>
940
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000941<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000942rm -rf .git/svn
943git svn rebase -l
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000944</pre>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000945
946</div>
947
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000948</div>
949
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000950<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000951<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000952 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000953</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000954
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000955<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000956
John Criswell58594852007-06-29 19:12:31 +0000957 <p>Once checked out from the Subversion repository, the LLVM suite source
958 code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000959configured via the <tt>configure</tt> script. This script sets variables in the
960various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
961<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
962the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000963
964<p>The following environment variables are used by the <tt>configure</tt>
965script to configure the build system:</p>
966
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000967<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +0000968 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000969 <tr>
970 <td>CC</td>
971 <td>Tells <tt>configure</tt> which C compiler to use. By default,
972 <tt>configure</tt> will look for the first GCC C compiler in
973 <tt>PATH</tt>. Use this variable to override
974 <tt>configure</tt>'s default behavior.</td>
975 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000976 <tr>
977 <td>CXX</td>
978 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
979 <tt>configure</tt> will look for the first GCC C++ compiler in
980 <tt>PATH</tt>. Use this variable to override
981 <tt>configure</tt>'s default behavior.</td>
982 </tr>
983</table>
984
985<p>The following options can be used to set or enable LLVM specific options:</p>
986
Misha Brukmand3de5c62004-01-20 00:20:17 +0000987<dl>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000988 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000989 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000990 Enables optimized compilation (debugging symbols are removed
991 and GCC optimization flags are enabled). Note that this is the default
992 setting if you are using the LLVM distribution. The default behavior
993 of an Subversion checkout is to use an unoptimized build (also known as a
994 debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000995 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000996 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +0000997 <dt><i>--enable-debug-runtime</i></dt>
998 <dd>
999 Enables debug symbols in the runtime libraries. The default is to strip
1000 debug symbols from the runtime libraries.
1001 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001002 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +00001003 <dd>
John Criswell86a3a482003-12-18 16:43:17 +00001004 Compile the Just In Time (JIT) compiler functionality. This is not
1005 available
Misha Brukman560e9892003-11-07 19:43:14 +00001006 on all platforms. The default is dependent on platform, so it is best
1007 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001008 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001009 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +00001010 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1011 <dd>Controls which targets will be built and linked into llc. The default
1012 value for <tt>target_options</tt> is "all" which builds and links all
1013 available targets. The value "host-only" can be specified to build only a
1014 native compiler (no cross-compiler targets available). The "native" target is
1015 selected as the target of the build host. You can also specify a comma
1016 separated list of target names that you want available in llc. The target
Misha Brukman21a63702008-12-11 18:23:24 +00001017 names use all lower case. The current set of targets is: <br>
Jim Grosbach691f4dd2012-04-27 16:29:22 +00001018 <tt>arm, cpp, hexagon, mblaze, mips, mipsel, msp430, powerpc, ptx, sparc, spu, x86, x86_64, xcore</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001019 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001020 <dt><i>--enable-doxygen</i></dt>
1021 <dd>Look for the doxygen program and enable construction of doxygen based
1022 documentation from the source code. This is disabled by default because
1023 generating the documentation can take a long time and producess 100s of
1024 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +00001025 <dt><i>--with-udis86</i></dt>
1026 <dd>LLVM can use external disassembler library for various purposes (now it's
1027 used only for examining code produced by JIT). This option will enable usage
1028 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1029 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001030</dl>
1031
1032<p>To configure LLVM, follow these steps:</p>
1033
1034<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001035 <li><p>Change directory into the object root directory:</p>
John Criswellf531f312003-10-27 18:18:16 +00001036
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001037 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1038
1039 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1040 tree:</p>
1041
1042 <div class="doc_code">
1043 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1044 </div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001045</ol>
John Criswell72989a52003-06-12 19:34:44 +00001046
Misha Brukman560e9892003-11-07 19:43:14 +00001047</div>
John Criswell72989a52003-06-12 19:34:44 +00001048
Misha Brukman560e9892003-11-07 19:43:14 +00001049<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001050<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001051 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001052</h3>
John Criswell72989a52003-06-12 19:34:44 +00001053
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001054<div>
John Criswell71139f22003-07-08 20:35:59 +00001055
Misha Brukman560e9892003-11-07 19:43:14 +00001056<p>Once you have configured LLVM, you can build it. There are three types of
1057builds:</p>
John Criswell71139f22003-07-08 20:35:59 +00001058
Misha Brukmand3de5c62004-01-20 00:20:17 +00001059<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001060 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001061 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001062 These builds are the default when one is using an Subversion checkout and
1063 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1064 used during configuration). The build system will compile the tools and
1065 libraries with debugging information. To get a Debug Build using the
1066 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1067 to <tt>configure</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001068 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001069
1070 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001071 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001072 These builds are enabled with the <tt>--enable-optimized</tt> option to
1073 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1074 <tt>gmake</tt> command line. For these builds, the build system will
1075 compile the tools and libraries with GCC optimizations enabled and strip
1076 debugging information from the libraries and executables it generates.
Chris Lattner1c1595f2009-04-25 22:24:49 +00001077 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001078 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001079
1080 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001081 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001082 These builds are for use with profiling. They compile profiling
1083 information into the code for use with programs like <tt>gprof</tt>.
1084 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1085 on the <tt>gmake</tt> command line.
1086</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001087
Misha Brukman560e9892003-11-07 19:43:14 +00001088<p>Once you have LLVM configured, you can build it by entering the
1089<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001090
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001091<div class="doc_code"><pre>% gmake</pre></div>
John Criswell38cc2b52003-10-10 14:26:14 +00001092
Chris Lattnere0050f02004-07-18 22:32:22 +00001093<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +00001094are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +00001095
1096<p>
1097If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +00001098the parallel build options provided by GNU Make. For example, you could use the
1099command:</p>
John Criswell72989a52003-06-12 19:34:44 +00001100
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001101<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellc5eb4602003-07-03 16:01:38 +00001102
Misha Brukman560e9892003-11-07 19:43:14 +00001103<p>There are several special targets which are useful when working with the LLVM
1104source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001105
Misha Brukmand3de5c62004-01-20 00:20:17 +00001106<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001107 <dt><tt>gmake clean</tt>
1108 <dd>
1109 Removes all files generated by the build. This includes object files,
1110 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001111 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001112
Reid Spencerdfcf7902004-12-08 16:51:31 +00001113 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001114 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +00001115 Removes everything that <tt>gmake clean</tt> does, but also removes files
1116 generated by <tt>configure</tt>. It attempts to return the source tree to the
1117 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001118 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001119
Misha Brukman62a2c1f2004-08-23 20:25:33 +00001120 <dt><tt>gmake install</tt>
1121 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +00001122 Installs LLVM header files, libraries, tools, and documentation in a
1123 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +00001124 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1125 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001126 <br><br>
1127
Reid Spencerdfcf7902004-12-08 16:51:31 +00001128 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001129 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +00001130 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greifa54634a2007-07-06 22:07:22 +00001131 install bitcode libraries into the GCC front end's bitcode library
1132 directory. If you need to update your bitcode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +00001133 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001134 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001135</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001136
Reid Spencerdfcf7902004-12-08 16:51:31 +00001137<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1138details on these <tt>make</tt> targets and descriptions of other targets
1139available.</p>
1140
Misha Brukman560e9892003-11-07 19:43:14 +00001141<p>It is also possible to override default values from <tt>configure</tt> by
1142declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001143
Misha Brukmand3de5c62004-01-20 00:20:17 +00001144<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001145 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1146 <dd>
1147 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001148 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001149
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001150 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001151 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001152 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001153 <br><br>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001154
1155 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1156 <dd>
1157 Perform a Debug build.
1158 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001159
Misha Brukman560e9892003-11-07 19:43:14 +00001160 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1161 <dd>
1162 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001163 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001164
Misha Brukman560e9892003-11-07 19:43:14 +00001165 <dt><tt>gmake VERBOSE=1</tt>
1166 <dd>
1167 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001168 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001169
1170 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1171 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001172 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001173 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001174</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001175
Misha Brukman560e9892003-11-07 19:43:14 +00001176<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1177it and any subdirectories that it contains. Entering any directory inside the
1178LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1179that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001180
Misha Brukman560e9892003-11-07 19:43:14 +00001181</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001182
Misha Brukman560e9892003-11-07 19:43:14 +00001183<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001184<h3>
Reid Spencer734b74f2006-07-27 06:41:31 +00001185 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001186</h3>
Reid Spencerd966b242006-07-27 05:43:30 +00001187
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001188<div>
Jim Grosbach7da1b902009-04-17 17:25:16 +00001189 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1190 executables and libraries to be hosted on a platform different from the
1191 platform where they are build (a Canadian Cross build). To configure a
1192 cross-compile, supply the configure script with <tt>--build</tt> and
1193 <tt>--host</tt> options that are different. The values of these options must
1194 be legal target triples that your GCC compiler supports.</p>
1195
1196 <p>The result of such a build is executables that are not runnable on
1197 on the build host (--build option) but can be executed on the compile host
Reid Spencer734b74f2006-07-27 06:41:31 +00001198 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001199</div>
1200
1201<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001202<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001203 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001204</h3>
John Criswell38cc2b52003-10-10 14:26:14 +00001205
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001206<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001207
Misha Brukman560e9892003-11-07 19:43:14 +00001208<p>The LLVM build system is capable of sharing a single LLVM source tree among
1209several LLVM builds. Hence, it is possible to build LLVM for several different
1210platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001211
Misha Brukman560e9892003-11-07 19:43:14 +00001212<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001213
Misha Brukman560e9892003-11-07 19:43:14 +00001214<ul>
1215 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001216
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001217 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001218
Misha Brukman560e9892003-11-07 19:43:14 +00001219 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1220 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001221
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001222 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001223</ul>
John Criswell72989a52003-06-12 19:34:44 +00001224
Misha Brukman560e9892003-11-07 19:43:14 +00001225<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1226named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001227
Misha Brukmand3de5c62004-01-20 00:20:17 +00001228<dl>
Duncan Sands1567f0f2010-07-08 08:27:18 +00001229 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman560e9892003-11-07 19:43:14 +00001230 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001231 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001232 <dt>Tools
Duncan Sands1567f0f2010-07-08 08:27:18 +00001233 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001234 <dt>Libraries
Duncan Sands1567f0f2010-07-08 08:27:18 +00001235 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001236 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001237 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001238
Misha Brukman560e9892003-11-07 19:43:14 +00001239 <dt>Release Builds
1240 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001241 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001242 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001243 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001244 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001245 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001246 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001247 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001248
Misha Brukman560e9892003-11-07 19:43:14 +00001249 <dt>Profile Builds
1250 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001251 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001252 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001253 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001254 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001255 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001256 </dl>
1257</dl>
John Criswell72989a52003-06-12 19:34:44 +00001258
Misha Brukman560e9892003-11-07 19:43:14 +00001259</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001260
Chris Lattner998c0672004-03-25 20:38:40 +00001261<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001262<h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001263 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001264</h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001265
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001266<div>
Chris Lattner998c0672004-03-25 20:38:40 +00001267
1268<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001269If you're running on a Linux system that supports the "<a
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001270href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001271module, and you have root access on the system, you can set your system up to
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001272execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattner998c0672004-03-25 20:38:40 +00001273first command may not be required if you are already using the module):</p>
1274
Misha Brukman20b8a6562005-02-03 22:25:23 +00001275<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001276<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001277$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckyb8c923b2009-11-04 06:15:28 +00001278$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001279$ chmod u+x hello.bc (if needed)
1280$ ./hello.bc
Chris Lattner998c0672004-03-25 20:38:40 +00001281</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001282</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001283
1284<p>
Chris Lattnerb5c11742010-02-17 18:33:13 +00001285This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +00001286can also use this command instead of the 'echo' command above:
Chris Lattner998c0672004-03-25 20:38:40 +00001287</p>
1288
Chris Lattnerb5c11742010-02-17 18:33:13 +00001289<div class="doc_code">
1290<pre>
1291$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1292</pre>
1293</div>
1294
Chris Lattner998c0672004-03-25 20:38:40 +00001295</div>
1296
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001297</div>
1298
Misha Brukman560e9892003-11-07 19:43:14 +00001299<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001300<h2>
1301 <a name="layout">Program Layout</a>
1302</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001303<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001304
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001305<div>
John Criswell72989a52003-06-12 19:34:44 +00001306
Misha Brukman560e9892003-11-07 19:43:14 +00001307<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001308href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001309href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001310The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001311
Misha Brukman560e9892003-11-07 19:43:14 +00001312<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001313<h3>
1314 <a name="examples"><tt>llvm/examples</tt></a>
1315</h3>
1316
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001317<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001318 <p>This directory contains some simple examples of how to use the LLVM IR and
1319 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001320</div>
John Criswell72989a52003-06-12 19:34:44 +00001321
Misha Brukman560e9892003-11-07 19:43:14 +00001322<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001323<h3>
1324 <a name="include"><tt>llvm/include</tt></a>
1325</h3>
1326
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001327<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001328
1329<p>This directory contains public header files exported from the LLVM
1330library. The three main subdirectories of this directory are:</p>
1331
Reid Spencer075de232004-09-05 20:50:22 +00001332<dl>
1333 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1334 <dd>This directory contains all of the LLVM specific header files. This
1335 directory also has subdirectories for different portions of LLVM:
1336 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1337 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001338
Reid Spencer075de232004-09-05 20:50:22 +00001339 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1340 <dd>This directory contains generic support libraries that are provided with
1341 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1342 and a Command Line option processing library store their header files here.
1343 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001344
Reid Spencer075de232004-09-05 20:50:22 +00001345 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1346 <dd>This directory contains header files configured by the <tt>configure</tt>
1347 script. They wrap "standard" UNIX and C header files. Source code can
1348 include these header files which automatically take care of the conditional
1349 #includes that the <tt>configure</tt> script generates.</dd>
1350</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001351</div>
1352
1353<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001354<h3>
1355 <a name="lib"><tt>llvm/lib</tt></a>
1356</h3>
1357
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001358<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001359
1360<p>This directory contains most of the source files of the LLVM system. In LLVM,
1361almost all code exists in libraries, making it very easy to share code among the
1362different <a href="#tools">tools</a>.</p>
1363
Misha Brukmand3de5c62004-01-20 00:20:17 +00001364<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001365 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1366 <dd> This directory holds the core LLVM source files that implement core
1367 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001368
Reid Spencer075de232004-09-05 20:50:22 +00001369 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1370 <dd>This directory holds the source code for the LLVM assembly language parser
1371 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001372
Gabor Greifa54634a2007-07-06 22:07:22 +00001373 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1374 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001375
Reid Spencer075de232004-09-05 20:50:22 +00001376 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001377 different program analyses, such as Dominator Information, Call Graphs,
1378 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001379 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001380
Reid Spencer075de232004-09-05 20:50:22 +00001381 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1382 <dd> This directory contains the source code for the LLVM to LLVM program
1383 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1384 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1385 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001386
Reid Spencer075de232004-09-05 20:50:22 +00001387 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1388 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001389 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1390 directory holds the X86 machine description while
Eric Christopher64a23232012-03-23 05:50:46 +00001391 <tt>llvm/lib/Target/ARM</tt> implements the ARM backend.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001392
Reid Spencer075de232004-09-05 20:50:22 +00001393 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1394 <dd> This directory contains the major parts of the code generator: Instruction
1395 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001396
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +00001397 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1398 <dd>(FIXME: T.B.D.)</dd>
1399
1400 <!--FIXME: obsoleted -->
Reid Spencer075de232004-09-05 20:50:22 +00001401 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1402 <dd> This directory contains the source level debugger library that makes
1403 it possible to instrument LLVM programs so that a debugger could identify
1404 source code locations at which the program is executing.</dd>
1405
1406 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001407 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer075de232004-09-05 20:50:22 +00001408 at runtime in both interpreted and JIT compiled fashions.</dd>
1409
1410 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar037fc932011-10-11 20:02:52 +00001411 <dd> This directory contains the source code that corresponds to the header
1412 files located in <tt>llvm/include/ADT/</tt>
1413 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001414</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001415
Misha Brukman560e9892003-11-07 19:43:14 +00001416</div>
John Criswell72989a52003-06-12 19:34:44 +00001417
Misha Brukman560e9892003-11-07 19:43:14 +00001418<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001419<h3>
1420 <a name="projects"><tt>llvm/projects</tt></a>
1421</h3>
1422
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001423<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001424 <p>This directory contains projects that are not strictly part of LLVM but are
1425 shipped with LLVM. This is also the directory where you should create your own
1426 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner7b7b6782008-08-11 06:13:31 +00001427 to set up your own project.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001428</div>
1429
1430<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001431<h3>
1432 <a name="runtime"><tt>llvm/runtime</tt></a>
1433</h3>
1434
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001435<div>
John Criswell72989a52003-06-12 19:34:44 +00001436
Gabor Greifa54634a2007-07-06 22:07:22 +00001437<p>This directory contains libraries which are compiled into LLVM bitcode and
Chad Rosierce50eec2012-02-26 22:26:37 +00001438used when linking programs with the Clang front end. Most of these libraries are
Misha Brukman560e9892003-11-07 19:43:14 +00001439skeleton versions of real libraries; for example, libc is a stripped down
1440version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001441
Misha Brukman560e9892003-11-07 19:43:14 +00001442<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1443end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001444
Misha Brukman560e9892003-11-07 19:43:14 +00001445</div>
John Criswell72989a52003-06-12 19:34:44 +00001446
Misha Brukman560e9892003-11-07 19:43:14 +00001447<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001448<h3>
1449 <a name="test"><tt>llvm/test</tt></a>
1450</h3>
1451
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001452<div>
Reid Spencer075de232004-09-05 20:50:22 +00001453 <p>This directory contains feature and regression tests and other basic sanity
1454 checks on the LLVM infrastructure. These are intended to run quickly and cover
1455 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001456</div>
John Criswell72989a52003-06-12 19:34:44 +00001457
Misha Brukman560e9892003-11-07 19:43:14 +00001458<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001459<h3>
1460 <a name="test-suite"><tt>test-suite</tt></a>
1461</h3>
1462
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001463<div>
John Criswell58594852007-06-29 19:12:31 +00001464 <p>This is not a directory in the normal llvm module; it is a separate
1465 Subversion
1466 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1467 This
John Criswell6ab273c2004-12-08 17:53:54 +00001468 module contains a comprehensive correctness, performance, and benchmarking
1469 test
John Criswell58594852007-06-29 19:12:31 +00001470 suite for LLVM. It is a separate Subversion module because not every LLVM
1471 user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001472 interested in downloading or building such a comprehensive test suite. For
1473 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001474 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001475</div>
John Criswell72989a52003-06-12 19:34:44 +00001476
Reid Spencer075de232004-09-05 20:50:22 +00001477<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001478<h3>
1479 <a name="tools"><tt>llvm/tools</tt></a>
1480</h3>
1481
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001482<div>
John Criswell38cc2b52003-10-10 14:26:14 +00001483
Misha Brukman560e9892003-11-07 19:43:14 +00001484<p>The <b>tools</b> directory contains the executables built out of the
1485libraries above, which form the main part of the user interface. You can
Duncan Sands142b9ed2010-02-18 14:08:13 +00001486always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001487following is a brief introduction to the most important tools. More detailed
1488information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001489
Misha Brukmand3de5c62004-01-20 00:20:17 +00001490<dl>
John Criswell72989a52003-06-12 19:34:44 +00001491
Reid Spencer075de232004-09-05 20:50:22 +00001492 <dt><tt><b>bugpoint</b></tt></dt>
1493 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001494 optimization passes or code generation backends by narrowing down the
1495 given test case to the minimum number of passes and/or instructions that
1496 still cause a problem, whether it is a crash or miscompilation. See <a
1497 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001498 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001499
Reid Spencer075de232004-09-05 20:50:22 +00001500 <dt><tt><b>llvm-ar</b></tt></dt>
1501 <dd>The archiver produces an archive containing
Gabor Greifa54634a2007-07-06 22:07:22 +00001502 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001503 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001504
Reid Spencer075de232004-09-05 20:50:22 +00001505 <dt><tt><b>llvm-as</b></tt></dt>
1506 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001507 bitcode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001508
Reid Spencer075de232004-09-05 20:50:22 +00001509 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001510 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer075de232004-09-05 20:50:22 +00001511 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001512
Reid Spencer075de232004-09-05 20:50:22 +00001513 <dt><tt><b>llvm-link</b></tt></dt>
1514 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1515 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001516
Reid Spencer075de232004-09-05 20:50:22 +00001517 <dt><tt><b>lli</b></tt></dt>
1518 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky97467822007-12-03 01:58:01 +00001519 can directly execute LLVM bitcode (although very slowly...). For architectures
1520 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1521 will function as a Just-In-Time compiler (if the functionality was compiled
1522 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001523
Reid Spencer075de232004-09-05 20:50:22 +00001524 <dt><tt><b>llc</b></tt></dt>
1525 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greifa54634a2007-07-06 22:07:22 +00001526 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001527 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001528
Reid Spencer788b0fd2004-12-22 06:29:07 +00001529 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001530 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1531 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001532 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencera7974cc2007-02-09 15:59:08 +00001533 usual machine code output. It works just like any other GCC compiler,
1534 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1535 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell58594852007-06-29 19:12:31 +00001536 separate Subversion module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001537
Reid Spencer075de232004-09-05 20:50:22 +00001538 <dt><tt><b>opt</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001539 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer80f843d2006-08-28 00:34:19 +00001540 transformations (which are specified on the command line), and then outputs
Duncan Sands142b9ed2010-02-18 14:08:13 +00001541 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukman21a63702008-12-11 18:23:24 +00001542 get a list of the program transformations available in LLVM.<br>
Reid Spencer80f843d2006-08-28 00:34:19 +00001543 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greifa54634a2007-07-06 22:07:22 +00001544 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer80f843d2006-08-28 00:34:19 +00001545 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001546</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001547</div>
John Criswell72989a52003-06-12 19:34:44 +00001548
Misha Brukman560e9892003-11-07 19:43:14 +00001549<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001550<h3>
1551 <a name="utils"><tt>llvm/utils</tt></a>
1552</h3>
1553
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001554<div>
John Criswell72989a52003-06-12 19:34:44 +00001555
Misha Brukman560e9892003-11-07 19:43:14 +00001556<p>This directory contains utilities for working with LLVM source code, and some
1557of the utilities are actually required as part of the build process because they
1558are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001559
Misha Brukmand3de5c62004-01-20 00:20:17 +00001560<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001561 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001562 that finds differences between code that LLC generates and code that LLI
1563 generates. This is a useful tool if you are debugging one of them,
1564 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001565 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001566
Misha Brukmand3de5c62004-01-20 00:20:17 +00001567 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001568 syntax-highlighting files which will work with Emacs and XEmacs editors,
1569 providing syntax highlighting support for LLVM assembly files and TableGen
1570 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001571 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001572
Misha Brukmand3de5c62004-01-20 00:20:17 +00001573 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001574 and outputs all non-generated source files, which is useful if one wishes
1575 to do a lot of development across directories and does not want to
1576 individually find each file. One way to use it is to run, for example:
1577 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001578 tree.<br><br>
1579
Reid Spencer075de232004-09-05 20:50:22 +00001580 <dt><tt><b>llvmgrep</b></tt></dt>
1581 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1582 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1583 line. This is a very efficient way of searching the source base for a
1584 particular regular expression.</dd>
1585
Misha Brukmand3de5c62004-01-20 00:20:17 +00001586 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001587 files in the current directory and then compiles and links the tool that
1588 is the first argument. For example, assuming you are in the directory
1589 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1590 simply running <tt>makellvm llc</tt> will make a build of the current
1591 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001592 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001593
Misha Brukmand3de5c62004-01-20 00:20:17 +00001594 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001595 the tool used to generate register descriptions, instruction set
1596 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001597 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001598
Misha Brukmand3de5c62004-01-20 00:20:17 +00001599 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001600 syntax-highlighting files which will work with the VIM editor, providing
1601 syntax highlighting support for LLVM assembly files and TableGen
1602 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001603 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001604
Misha Brukman560e9892003-11-07 19:43:14 +00001605</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001606
Misha Brukman560e9892003-11-07 19:43:14 +00001607</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001608
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001609</div>
1610
Misha Brukman560e9892003-11-07 19:43:14 +00001611<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001612<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001613 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001614</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001615<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001616
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001617<div>
Chad Rosier233f1472012-02-26 21:31:25 +00001618<p>This section gives an example of using LLVM with the Clang front end.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001619
1620<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001621<h3>
Chad Rosier233f1472012-02-26 21:31:25 +00001622 <a name="tutorial4">Example with clang</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001623</h3>
Chris Lattner5b560d92006-08-14 20:45:25 +00001624
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001625<div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001626
1627<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001628 <li><p>First, create a simple C file, name it 'hello.c':</p>
1629
1630<div class="doc_code">
1631<pre>
1632#include &lt;stdio.h&gt;
1633
1634int main() {
1635 printf("hello world\n");
1636 return 0;
1637}
1638</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001639
1640 <li><p>Next, compile the C file into a native executable:</p>
1641
Chad Rosier233f1472012-02-26 21:31:25 +00001642 <div class="doc_code"><pre>% clang hello.c -o hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001643
Chad Rosier233f1472012-02-26 21:31:25 +00001644 <p>Note that clang works just like GCC by default. The standard -S and
Chris Lattner5b560d92006-08-14 20:45:25 +00001645 -c arguments work as usual (producing a native .s or .o file,
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001646 respectively).</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001647
Gabor Greifa54634a2007-07-06 22:07:22 +00001648 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001649
1650 <div class="doc_code">
Chad Rosier233f1472012-02-26 21:31:25 +00001651 <pre>% clang -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001652
1653 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1654 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1655 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Chad Rosier233f1472012-02-26 21:31:25 +00001656 the bitcode file.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001657
1658 <li><p>Run the program in both forms. To run the program, use:</p>
1659
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001660 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001661
1662 <p>and</p>
1663
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001664 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001665
1666 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001667 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001668
1669 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1670 code:</p>
1671
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001672<div class="doc_code">
1673<pre>llvm-dis &lt; hello.bc | less</pre>
1674</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001675
1676 <li><p>Compile the program to native assembly using the LLC code
1677 generator:</p>
1678
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001679 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001680
1681 <li><p>Assemble the native assembly language file into a program:</p>
1682
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001683<div class="doc_code">
1684<pre>
1685<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1686
1687<b>Others:</b> % gcc hello.s -o hello.native
1688</pre>
1689</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001690
1691 <li><p>Execute the native code program:</p>
1692
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001693 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001694
Chad Rosier233f1472012-02-26 21:31:25 +00001695 <p>Note that using clang to compile directly to native code (i.e. when
Chris Lattner5b560d92006-08-14 20:45:25 +00001696 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001697 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001698
1699</ol>
1700
1701</div>
1702
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001703</div>
John Criswell72989a52003-06-12 19:34:44 +00001704
Misha Brukman560e9892003-11-07 19:43:14 +00001705<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001706<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001707 <a name="problems">Common Problems</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001708</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001709<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001710
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001711<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001712
Misha Brukman560e9892003-11-07 19:43:14 +00001713<p>If you are having problems building or using LLVM, or if you have any other
1714general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1715Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001716
Misha Brukman560e9892003-11-07 19:43:14 +00001717</div>
John Criswell72989a52003-06-12 19:34:44 +00001718
Misha Brukman560e9892003-11-07 19:43:14 +00001719<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001720<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001721 <a name="links">Links</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001722</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001723<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001724
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001725<div>
John Criswell72989a52003-06-12 19:34:44 +00001726
Bill Wendlingcb13d702008-07-22 01:10:25 +00001727<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman560e9892003-11-07 19:43:14 +00001728some simple things... there are many more interesting and complicated things
1729that you can do that aren't documented here (but we'll gladly accept a patch
1730if you want to write something up!). For more information about LLVM, check
1731out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001732
Misha Brukman560e9892003-11-07 19:43:14 +00001733<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001734 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1735 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1736 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001737 that Uses LLVM</a></li>
1738</ul>
1739
1740</div>
1741
1742<!-- *********************************************************************** -->
1743
1744<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001745<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001746 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001747 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001748 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +00001749 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001750
Misha Brukman74d4df82003-11-22 01:30:01 +00001751 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001752 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001753 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001754 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001755</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001756</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001757</html>