blob: 0dad3c22f6627a04c67dbf5bba796fc55f0aa68a [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>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +000010
Misha Brukman560e9892003-11-07 19:43:14 +000011<div class="doc_title">
12 Getting Started with the LLVM System
13</div>
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="#installcf">Install the GCC Front End</a></li>
33 <li><a href="#config">Local LLVM Configuration</a></li>
34 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
35 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
36 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
37 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000038 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +000039
Misha Brukman560e9892003-11-07 19:43:14 +000040 <li><a href="#layout">Program layout</a>
41 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
43 <li><a href="#include"><tt>llvm/include</tt></a></li>
44 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
45 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
46 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
47 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trick68aa18e42010-09-23 20:26:44 +000048 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
50 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000051 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +000052
Misha Brukman560e9892003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000054 <ol>
55 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000056 </ol>
Misha Brukman560e9892003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner020e1fc2004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
65 <a href="http://misha.brukman.net">Misha Brukman</a>,
66 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
67 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
68 </p>
69</div>
Misha Brukman560e9892003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
73<div class="doc_section">
74 <a name="overview"><b>Overview</b></a>
75</div>
76<!-- *********************************************************************** -->
77
78<div class="doc_text">
79
80<p>Welcome to LLVM! In order to get started, you first need to know some
81basic information.</p>
82
Andrew Trick68aa18e42010-09-23 20:26:44 +000083<p>First, LLVM comes in three pieces. The first piece is the LLVM
84suite. This contains all of the tools, libraries, and header files
85needed to use the low level virtual machine. It contains an
86assembler, disassembler, bitcode analyzer and bitcode optimizer. It
87also contains basic regression tests that can be used to test the LLVM
88tools and the GCC front end.</p>
Misha Brukman560e9892003-11-07 19:43:14 +000089
90<p>The second piece is the GCC front end. This component provides a version of
Gabor Greifa54634a2007-07-06 22:07:22 +000091GCC that compiles C and C++ code into LLVM bitcode. Currently, the GCC front
Chris Lattner40872ad2007-03-06 06:27:34 +000092end uses the GCC parser to convert code to LLVM. Once
Gabor Greifa54634a2007-07-06 22:07:22 +000093compiled into LLVM bitcode, a program can be manipulated with the LLVM tools
Misha Brukman560e9892003-11-07 19:43:14 +000094from the LLVM suite.</p>
95
John Criswell6ab273c2004-12-08 17:53:54 +000096<p>
Andrew Trick68aa18e42010-09-23 20:26:44 +000097There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell6ab273c2004-12-08 17:53:54 +000098with a testing harness that can be used to further test LLVM's functionality
99and performance.
100</p>
101
Misha Brukman560e9892003-11-07 19:43:14 +0000102</div>
103
104<!-- *********************************************************************** -->
105<div class="doc_section">
106 <a name="quickstart"><b>Getting Started Quickly (A Summary)</b></a>
107</div>
108<!-- *********************************************************************** -->
109
110<div class="doc_text">
111
112<p>Here's the short story for getting up and running quickly with LLVM:</p>
113
114<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000115 <li>Read the documentation.</li>
116 <li>Read the documentation.</li>
117 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000118 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
119 (see <a href="#installcf">Install the GCC Front End</a> for details):</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000120 <ol>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000121 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000122 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
123 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
124 <li>Note: If the binary extension is "<tt>.bz</tt>" use <tt>bunzip2</tt> instead of <tt>gunzip</tt>.</li>
125 <li>Note: On Windows, use <a href="http://www.7-zip.org">7-Zip</a> or a similar archiving tool.</li>
126 <li>Add <tt>llvm-gcc</tt>'s "<tt>bin</tt>" directory to your <tt>PATH</tt> environment variable.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000127 </ol></li>
128
Misha Brukman20b8a6562005-02-03 22:25:23 +0000129 <li>Get the LLVM Source Code
Misha Brukman560e9892003-11-07 19:43:14 +0000130 <ul>
John Criswell58594852007-06-29 19:12:31 +0000131 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman560e9892003-11-07 19:43:14 +0000132 <ol>
133 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell64f13ab2004-03-12 20:31:37 +0000134 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000135 </ol></li>
136
Misha Brukman560e9892003-11-07 19:43:14 +0000137 </ul></li>
138
Misha Brukman20b8a6562005-02-03 22:25:23 +0000139 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswelldfe6a862004-12-10 15:51:16 +0000140 <ul>
John Criswell58594852007-06-29 19:12:31 +0000141 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswelldfe6a862004-12-10 15:51:16 +0000142 <ol>
143 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
144 <li><tt>cd llvm/projects</tt>
145 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000146 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswelldfe6a862004-12-10 15:51:16 +0000147 </ol></li>
148
John Criswelldfe6a862004-12-10 15:51:16 +0000149 </ul></li>
150
151
Misha Brukman560e9892003-11-07 19:43:14 +0000152 <li>Configure the LLVM Build Environment
153 <ol>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000154 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
155 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
156 Some common options:
157
Misha Brukman560e9892003-11-07 19:43:14 +0000158 <ul>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000159 <li><tt>--prefix=<i>directory</i></tt>
160 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000161 want the LLVM tools and libraries to be installed (default
162 <tt>/usr/local</tt>).</p></li>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000163 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
164 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswellcfdeb5c2005-05-09 16:39:27 +0000165 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sands10961cd2009-04-18 12:40:19 +0000166 not specified, the PATH will be searched. This is only needed if you
Andrew Trick68aa18e42010-09-23 20:26:44 +0000167 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000168 <li><tt>--enable-spec2000=<i>directory</i></tt>
169 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
170 benchmarks should be available in
171 <tt><i>directory</i></tt>.</p></li>
172 </ul>
173 </ol></li>
174
175 <li>Build the LLVM Suite:
176 <ol>
Chris Lattnere0050f02004-07-18 22:32:22 +0000177 <li><tt>gmake -k |&amp; tee gnumake.out
178 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner13ce9182007-01-04 07:06:05 +0000179 <li>If you get an "internal compiler error (ICE)" or test failures, see
180 <a href="#brokengcc">below</a>.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000181 </ol>
182
183</ol>
184
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000185<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000186detailed information on configuring and compiling LLVM. See <a
187href="#environment">Setting Up Your Environment</a> for tips that simplify
188working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
189Layout</a> to learn about the layout of the source code tree.</p>
190
191</div>
192
193<!-- *********************************************************************** -->
194<div class="doc_section">
195 <a name="requirements"><b>Requirements</b></a>
196</div>
197<!-- *********************************************************************** -->
198
199<div class="doc_text">
200
201<p>Before you begin to use the LLVM system, review the requirements given below.
202This may save you some trouble by knowing ahead of time what hardware and
203software you will need.</p>
204
205</div>
206
207<!-- ======================================================================= -->
208<div class="doc_subsection">
209 <a name="hardware"><b>Hardware</b></a>
210</div>
211
212<div class="doc_text">
213
214<p>LLVM is known to work on the following platforms:</p>
215
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000216<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000217<tr>
218 <th>OS</th>
219 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000220 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000221</tr>
222<tr>
Chris Lattner6bad1372009-07-22 04:21:40 +0000223 <td>AuroraUX</td>
224 <td>x86<sup><a href="#pf_1">1</a></sup></td>
225 <td>GCC</td>
Chris Lattner3a56ae82009-07-21 22:47:03 +0000226</tr>
227<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000228 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000229 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000230 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000231</tr>
232<tr>
Edward O'Callaghanab8a04c2009-08-04 05:24:28 +0000233 <td>Linux</td>
234 <td>amd64</td>
235 <td>GCC</td>
236</tr>
237<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000238 <td>Solaris</td>
239 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000240 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000241</tr>
242<tr>
243 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000244 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000245 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000246</tr>
247<tr>
Bill Wendling5d32b702010-12-15 01:35:55 +0000248 <td>FreeBSD</td>
249 <td>amd64</td>
250 <td>GCC</td>
251</tr>
252<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000253 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000254 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000255 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000256</tr>
257<tr>
Scott Michel4799ea72008-03-18 23:13:26 +0000258 <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 +0000259 <td>x86</td>
260 <td>GCC</td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000261</tr>
262<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000263 <td>Cygwin/Win32</td>
Anton Korobeynikovd0a0bc32009-12-09 17:26:02 +0000264 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
265 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000266 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000267</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000268<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000269 <td>MinGW/Win32</td>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000270 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000271 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
272 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000273 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000274</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000275</table>
276
277<p>LLVM has partial support for the following platforms:</p>
278
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000279<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000280<tr>
281 <th>OS</th>
282 <th>Arch</th>
283 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000284</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000285<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000286 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000287 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000288 <td>Visual Studio 2005 SP1 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000289<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000290 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000291 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000292 <td>GCC</td>
293</tr>
294<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000295 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000296 <td>PowerPC</td>
297 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000298</tr>
John Criswell05990f32005-05-09 16:49:59 +0000299
300<tr>
301 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
302 <td>Alpha</td>
303 <td>GCC</td>
304</tr>
305<tr>
306 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
307 <td>Itanium (IA-64)</td>
308 <td>GCC</td>
309</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000310<tr>
311 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
312 <td>Itanium (IA-64)</td>
313 <td>HP aCC</td>
314</tr>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000315<tr>
316 <td>Windows x64</td>
317 <td>x86-64</td>
318 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
319</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000320</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000321
Misha Brukman77723092005-02-09 21:01:26 +0000322<p><b>Notes:</b></p>
323
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000324<div class="doc_notes">
325<ol>
326<li><a name="pf_1">Code generation supported for Pentium processors and
327up</a></li>
328<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
329<li><a name="pf_3">No native code generation</a></li>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000330<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 +0000331<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattnerb7481cf2009-01-02 07:10:51 +0000332<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell05990f32005-05-09 16:49:59 +0000333<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000334<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
335 generated by LLVM properly.</a></li>
Chris Lattner26c74442008-11-09 17:19:14 +0000336<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 +0000337 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner26c74442008-11-09 17:19:14 +0000338 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
339 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel4799ea72008-03-18 23:13:26 +0000340 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000341<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
342 version of the perl package, and be sure it appears in your path
343 before any Windows-based versions such as Strawberry Perl and
344 ActivePerl, as these have Windows-specifics that will cause the
345 build to fail.</a></li>
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000346<li><a name="pf_11">To use LLVM modules on Win32-based system,
347 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</li>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000348<li><a name="pf_12">To compile SPU backend, you need to add
349 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</li>
Misha Brukman77723092005-02-09 21:01:26 +0000350</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000351</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000352
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000353<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 +0000354mode, depending on the system (it is so large because of all the debugging
355information and the fact that the libraries are statically linked into multiple
Chris Lattner0cb89772009-04-25 22:08:52 +0000356tools). If you do not need many of the tools and you are space-conscious, you
357can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
358requires considerably less space.</p>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000359
Misha Brukman560e9892003-11-07 19:43:14 +0000360<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
361guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greifa54634a2007-07-06 22:07:22 +0000362able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman560e9892003-11-07 19:43:14 +0000363generation should work as well, although the generated native code may not work
364on your platform.</p>
365
366<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman876d5f12004-08-09 19:57:01 +0000367to work on another platform, you can download a copy of the source and <a
Duncan Sands551d3e62008-02-14 17:53:22 +0000368href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000369
370</div>
371
372<!-- ======================================================================= -->
Reid Spencer38fcf302004-11-15 21:15:12 +0000373<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000374<div class="doc_text">
Reid Spencer38fcf302004-11-15 21:15:12 +0000375 <p>Compiling LLVM requires that you have several software packages
376 installed. The table below lists those required packages. The Package column
377 is the usual name for the software package that LLVM depends on. The Version
378 column provides "known to work" versions of the package. The Notes column
379 describes how LLVM uses the package and provides other details.</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000380 <table summary="Packages required to compile LLVM">
Reid Spencer38fcf302004-11-15 21:15:12 +0000381 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000382
Reid Spencer38fcf302004-11-15 21:15:12 +0000383 <tr>
384 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
385 <td>3.79, 3.79.1</td>
386 <td>Makefile/build processor</td>
387 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000388
Reid Spencer38fcf302004-11-15 21:15:12 +0000389 <tr>
390 <td><a href="http://gcc.gnu.org">GCC</a></td>
391 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000392 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000393 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000394
Reid Spencer38fcf302004-11-15 21:15:12 +0000395 <tr>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000396 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
397 <td>4.5</td>
398 <td>For building the CFE</td>
399 </tr>
400
401 <tr>
John Criswell58594852007-06-29 19:12:31 +0000402 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
403 <td>&ge;1.3</td>
404 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000405 </tr>
406
407 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000408 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
409 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000410 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000411 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000412
Reid Spencer38fcf302004-11-15 21:15:12 +0000413 <tr>
414 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
415 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000416 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000417 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000418
Reid Spencer38fcf302004-11-15 21:15:12 +0000419 <tr>
420 <td><a href="http://expect.nist.gov/">expect</a></td>
421 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000422 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000423 </tr>
424
425 <tr>
426 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000427 <td>&ge;5.6.0</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000428 <td>Nightly tester, utilities</td>
429 </tr>
430
431 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000432 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
433 <td>1.4</td>
434 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000435 </tr>
436
437 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000438 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000439 <td>2.60</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000440 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
441 </tr>
442
443 <tr>
444 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000445 <td>1.9.6</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000446 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
447 </tr>
448
449 <tr>
450 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000451 <td>1.5.22</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000452 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000453 </tr>
454
455 </table>
456
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000457 <p><b>Notes:</b></p>
458 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000459 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000460 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000461 need to build the other languages for LLVM's purposes.</a> See
462 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell58594852007-06-29 19:12:31 +0000463 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000464 latest LLVM sources. If you're working from a release distribution, you
John Criswell58594852007-06-29 19:12:31 +0000465 don't need Subversion.</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000466 <li><a name="sf3">Only needed if you want to run the automated test
467 suite in the <tt>llvm/test</tt> directory.</a></li>
468 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser4518c862010-05-19 07:00:17 +0000469 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
470 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer098fce42004-12-09 17:55:37 +0000471 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000472 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000473 </div>
474
Reid Spencer38fcf302004-11-15 21:15:12 +0000475 <p>Additionally, your compilation host is expected to have the usual
476 plethora of Unix utilities. Specifically:</p>
477 <ul>
478 <li><b>ar</b> - archive library builder</li>
479 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
480 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
481 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000482 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000483 <li><b>cp</b> - copy files</li>
484 <li><b>date</b> - print the current date/time </li>
485 <li><b>echo</b> - print to standard output</li>
486 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000487 <li><b>find</b> - find files/dirs in a file system</li>
488 <li><b>grep</b> - regular expression search utility</li>
489 <li><b>gzip*</b> - gzip command for distribution generation</li>
490 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
491 <li><b>install</b> - install directories/files </li>
492 <li><b>mkdir</b> - create a directory</li>
493 <li><b>mv</b> - move (rename) files</li>
494 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000495 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000496 <li><b>sed</b> - stream editor for transforming output</li>
497 <li><b>sh</b> - Bourne shell for make build scripts</li>
498 <li><b>tar</b> - tape archive for distribution generation</li>
499 <li><b>test</b> - test things in file system</li>
500 <li><b>unzip*</b> - unzip command for distribution checking</li>
501 <li><b>zip*</b> - zip command for distribution generation</li>
502 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000503</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000504
Chris Lattnere0050f02004-07-18 22:32:22 +0000505<!-- ======================================================================= -->
506<div class="doc_subsection">
Chris Lattner55514822007-06-19 05:52:36 +0000507 <a name="brokengcc">Broken versions of GCC and other tools</a>
Chris Lattnere0050f02004-07-18 22:32:22 +0000508</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000509
Chris Lattnere0050f02004-07-18 22:32:22 +0000510<div class="doc_text">
511
512<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
513bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner29052c82006-06-16 17:20:33 +0000514to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000515successfully with them (however, see important notes below). Other versions
516of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000517here are known to not work. If you are using one of these versions, please try
518to upgrade your GCC to something more recent. If you run into a problem with a
519version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
520us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
521of GCC you are using.
522</p>
523
524<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
525problems in the STL that effectively prevent it from compiling LLVM.
526</p>
527
Chris Lattner419df4e2008-02-13 17:50:24 +0000528<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
529a bogus template error. This was fixed in later GCCs.</p>
John Criswellfd769452004-11-23 22:06:24 +0000530
Chris Lattnere0050f02004-07-18 22:32:22 +0000531<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
532href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
533the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000534
Chris Lattner58247622005-02-13 22:20:49 +0000535<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands551d3e62008-02-14 17:53:22 +0000536 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner58247622005-02-13 22:20:49 +0000537 to a newer version</a> if possible.</p>
538<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
539 possibly others) does not compile LLVM correctly (it appears that exception
540 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
541 to a newer version of GCC.</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000542<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000543 code generator, causing an infinite loop in the llvm-gcc build when built
544 with optimizations enabled (i.e. a release build).</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000545<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000546 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
547 correctly compiles LLVM at -O2. A work around is to build release LLVM
548 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000549<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 +0000550 miscompiles portions of LLVM</a>.</p>
Chris Lattner059a8df2007-11-01 04:20:16 +0000551<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
552 when building with optimizations enabled. It appears to work with
553 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
554 build.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000555<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
556 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000557<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
558 default with ENABLE_OPTIMIZED=1. To work around this, build with
559 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000560<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
561 compiling some files. At the time of this writing, GCC mainline (4.2)
562 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000563<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
564 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
565 code. LLVM will appear to mostly work but will be buggy, e.g. failing
566 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000567<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
568platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbar2a575452008-10-11 18:40:33 +0000569<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
570to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
571about symbols remaining in the table on destruction.</p>
Nuno Lopes94993852008-12-10 16:11:10 +0000572<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 +0000573as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Anton Korobeynikovdad58712009-05-04 10:24:46 +0000574<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
575 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
576 with link errors when using this GCC version.</p>
Chris Lattnereba6c722009-09-10 16:25:02 +0000577<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 +0000578<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
579when optimizations are turned on. The symptom is an infinite loop in
Chris Lattnereba6c722009-09-10 16:25:02 +0000580FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewyckyabe8c132010-10-07 22:30:47 +0000581<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5821</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
583one symptom of the problem.
Reid Spencer6291ddc2006-11-04 00:33:42 +0000584<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
585long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
586defined in a discarded section. You can safely ignore these messages as they are
587erroneous and the linkage is correct. These messages disappear using ld
5882.17.</p>
Chris Lattner55514822007-06-19 05:52:36 +0000589
590<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
591href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
592causes huge link times (minutes instead of seconds) when building LLVM. We
593recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
594
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000595<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewycky2db07612009-02-25 06:29:47 +0000596<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
597which causes intermittent failures when building LLVM with position independent
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000598code. The symptom is an error about cyclic dependencies. We recommend
599upgrading to a newer version of Gold.</p>
Nick Lewycky2db07612009-02-25 06:29:47 +0000600
Misha Brukman560e9892003-11-07 19:43:14 +0000601</div>
602
Chris Lattnere0050f02004-07-18 22:32:22 +0000603
604
Misha Brukman560e9892003-11-07 19:43:14 +0000605<!-- *********************************************************************** -->
606<div class="doc_section">
607 <a name="starting"><b>Getting Started with LLVM</b></a>
608</div>
609<!-- *********************************************************************** -->
610
Chris Lattnere0050f02004-07-18 22:32:22 +0000611<div class="doc_text">
612
613<p>The remainder of this guide is meant to get you up and running with
614LLVM and to give you some basic information about the LLVM environment.</p>
615
616<p>The later sections of this guide describe the <a
617href="#layout">general layout</a> of the the LLVM source tree, a <a
618href="#tutorial">simple example</a> using the LLVM tool chain, and <a
619href="#links">links</a> to find more information about LLVM or to get
620help via e-mail.</p>
621</div>
622
Misha Brukman560e9892003-11-07 19:43:14 +0000623<!-- ======================================================================= -->
624<div class="doc_subsection">
625 <a name="terminology">Terminology and Notation</a>
626</div>
627
628<div class="doc_text">
629
630<p>Throughout this manual, the following names are used to denote paths
631specific to the local system and working environment. <i>These are not
632environment variables you need to set but just strings used in the rest
633of this document below</i>. In any of the examples below, simply replace
634each of these names with the appropriate pathname on your local system.
635All these paths are absolute:</p>
636
Misha Brukmand3de5c62004-01-20 00:20:17 +0000637<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000638 <dt>SRC_ROOT
639 <dd>
640 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000641 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000642
Misha Brukman560e9892003-11-07 19:43:14 +0000643 <dt>OBJ_ROOT
644 <dd>
645 This is the top level directory of the LLVM object tree (i.e. the
646 tree where object files and compiled programs will be placed. It
647 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000648 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000649
650 <dt>LLVMGCCDIR
651 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000652 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000653 <p>
654 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000655 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000656</dl>
657
658</div>
659
660<!-- ======================================================================= -->
661<div class="doc_subsection">
662 <a name="environment">Setting Up Your Environment</a>
663</div>
664
665<div class="doc_text">
666
667<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000668In order to compile and use LLVM, you may need to set some environment
669variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000670
Misha Brukmand3de5c62004-01-20 00:20:17 +0000671<dl>
Gabor Greifa54634a2007-07-06 22:07:22 +0000672 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000673 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greifa54634a2007-07-06 22:07:22 +0000674 locations of your bitcode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000675 convenience since you can specify the paths using the -L options of the
Gabor Greifa54634a2007-07-06 22:07:22 +0000676 tools and the C/C++ front-end will automatically use the bitcode files
John Criswelle1a81202005-05-18 19:43:33 +0000677 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000678 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000679</dl>
680
681</div>
682
683<!-- ======================================================================= -->
684<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000685 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000686</div>
687
688<div class="doc_text">
689
690<p>
691If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000692can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000693suite and the LLVM GCC front end compiled for your platform. There is an
694additional test suite that is optional. Each file is a TAR archive that is
695compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000696</p>
697
Misha Brukmand4528ea2005-02-02 18:01:57 +0000698<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000699<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000700 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukman21a63702008-12-11 18:23:24 +0000701 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000702
Misha Brukmand4528ea2005-02-02 18:01:57 +0000703 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000704 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000705
Misha Brukman4050d152008-12-29 19:38:58 +0000706 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
707 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukman21a63702008-12-11 18:23:24 +0000708 directory for build instructions.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000709
Misha Brukman4050d152008-12-29 19:38:58 +0000710 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
711 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000712
Misha Brukman560e9892003-11-07 19:43:14 +0000713</dl>
714
715</div>
716
717<!-- ======================================================================= -->
718<div class="doc_subsection">
John Criswell58594852007-06-29 19:12:31 +0000719 <a name="checkout">Checkout LLVM from Subversion</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000720</div>
721
722<div class="doc_text">
723
John Criswell58594852007-06-29 19:12:31 +0000724<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattner1c1595f2009-04-25 22:24:49 +0000725the entire source code. All you need to do is check it out from Subversion as
Misha Brukman560e9892003-11-07 19:43:14 +0000726follows:</p>
727
728<ul>
John Criswell58594852007-06-29 19:12:31 +0000729 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov4c04a93332007-06-29 20:56:49 +0000730 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
731 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell58594852007-06-29 19:12:31 +0000732 llvm</tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000733</ul>
734
John Criswell58594852007-06-29 19:12:31 +0000735
Misha Brukman560e9892003-11-07 19:43:14 +0000736<p>This will create an '<tt>llvm</tt>' directory in the current
737directory and fully populate it with the LLVM source code, Makefiles,
738test directories, and local copies of documentation files.</p>
739
Misha Brukmand3de5c62004-01-20 00:20:17 +0000740<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikoveaa836b2007-06-29 23:13:42 +0000741revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikov09ca62d2007-06-30 00:00:57 +0000742'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman52757bf2008-12-17 16:27:23 +0000743subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000744
John Criswell86a3a482003-12-18 16:43:17 +0000745<ul>
Bill Wendlingc4735872010-10-06 23:50:30 +0000746<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner3d7ec7b2010-10-06 05:36:01 +0000747<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattner9d3ba88b2009-10-23 06:20:06 +0000748<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000749<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman52757bf2008-12-17 16:27:23 +0000750<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattner610e89d2008-06-09 06:02:09 +0000751<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattner779593c2008-02-12 02:42:55 +0000752<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner586eb8e2007-09-28 22:50:54 +0000753<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000754<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000755<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000756<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000757<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000758<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000759<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000760<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000761<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000762<li>Release 1.2: <b>RELEASE_12</b></li>
763<li>Release 1.1: <b>RELEASE_11</b></li>
764<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000765</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000766
Reid Spencerdfcf7902004-12-08 16:51:31 +0000767<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 +0000768you get it from the Subversion repository:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000769
770<div class="doc_code">
Reid Spencerdfcf7902004-12-08 16:51:31 +0000771<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000772% cd llvm/projects
Andrew Trick68aa18e42010-09-23 20:26:44 +0000773% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencerdfcf7902004-12-08 16:51:31 +0000774</pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000775</div>
776
Reid Spencerdfcf7902004-12-08 16:51:31 +0000777<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000778configured by the LLVM configure script as well as automatically updated when
John Criswell58594852007-06-29 19:12:31 +0000779you run <tt>svn update</tt>.</p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000780
Chris Lattner40872ad2007-03-06 06:27:34 +0000781<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands551d3e62008-02-14 17:53:22 +0000782and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner40872ad2007-03-06 06:27:34 +0000783instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000784
Misha Brukman560e9892003-11-07 19:43:14 +0000785</div>
786
787<!-- ======================================================================= -->
788<div class="doc_subsection">
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000789 <a name="git_mirror">GIT mirror</a>
790</div>
791
792<div class="doc_text">
793
794<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
795 sync automatically with each Subversion commit and contain all necessary
796 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
797 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
798 read-only GIT clone of LLVM via:
799<pre>
800% git clone http://llvm.org/git/llvm.git
801</pre>
802</p>
803
804</div>
805
806<!-- ======================================================================= -->
807<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000808 <a name="installcf">Install the GCC Front End</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000809</div>
810
811<div class="doc_text">
812
Jim Grosbach67584fe2009-12-17 17:18:11 +0000813<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
814GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trick68aa18e42010-09-23 20:26:44 +0000815It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach67584fe2009-12-17 17:18:11 +0000816you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattner24b71352007-02-14 07:33:00 +0000817main LLVM repository.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000818
Jim Grosbach67584fe2009-12-17 17:18:11 +0000819<p>To install the GCC front end, do the following (on Windows, use an archival tool
820like <a href="http://www.7-zip.org">7-zip</a> that understands gzipped tars):</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000821
822<ol>
823 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukman4050d152008-12-29 19:38:58 +0000824 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman560e9892003-11-07 19:43:14 +0000825 -</tt></li>
826</ol>
827
Jim Grosbach67584fe2009-12-17 17:18:11 +0000828<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
829<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
830Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
831to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
832<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
833
834<p>If you now want to build LLVM from source, when you configure LLVM, it will
835automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trick68aa18e42010-09-23 20:26:44 +0000836use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach67584fe2009-12-17 17:18:11 +0000837point after building the main LLVM repository: just reconfigure llvm and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000838test-suite will pick it up.
Chris Lattner24b71352007-02-14 07:33:00 +0000839</p>
840
Jim Grosbach67584fe2009-12-17 17:18:11 +0000841<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
842versions of the required w32api and mingw-runtime binaries. The last remaining step for
843Windows users is to simply uncompress the binary binutils package from
844<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
845front end installation steps are not quite the same as a typical manual MinGW installation,
846they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000847
Jim Grosbach67584fe2009-12-17 17:18:11 +0000848<p>To install binutils on Windows:</p>
849
850<ol>
851 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
852 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
853 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
854</ol>
855
856<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
857example, the binary distribution may include an old version of a system header
858file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
859libraries not available on your system. In cases like these, you may want to try
860<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
861this is much easier now than it was in the past.</p>
862
863<p>We also do not currently support updating of the GCC front end by manually overlaying
864newer versions of the w32api and mingw-runtime binary packages that may become available
865from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
866a self-contained convenience package that requires Windows users to simply download and
867uncompress the GNU Binutils binary package from the MinGW project.</p>
868
869<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
870binaries is not as easy as previously described, or you would like to suggest improvements,
871please let us know how you would like to see things improved by dropping us a note on our
872<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000873
874</div>
875
876<!-- ======================================================================= -->
877<div class="doc_subsection">
878 <a name="config">Local LLVM Configuration</a>
879</div>
880
881<div class="doc_text">
882
John Criswell58594852007-06-29 19:12:31 +0000883 <p>Once checked out from the Subversion repository, the LLVM suite source
884 code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000885configured via the <tt>configure</tt> script. This script sets variables in the
886various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
887<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
888the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000889
890<p>The following environment variables are used by the <tt>configure</tt>
891script to configure the build system:</p>
892
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000893<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +0000894 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000895 <tr>
896 <td>CC</td>
897 <td>Tells <tt>configure</tt> which C compiler to use. By default,
898 <tt>configure</tt> will look for the first GCC C compiler in
899 <tt>PATH</tt>. Use this variable to override
900 <tt>configure</tt>'s default behavior.</td>
901 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000902 <tr>
903 <td>CXX</td>
904 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
905 <tt>configure</tt> will look for the first GCC C++ compiler in
906 <tt>PATH</tt>. Use this variable to override
907 <tt>configure</tt>'s default behavior.</td>
908 </tr>
909</table>
910
911<p>The following options can be used to set or enable LLVM specific options:</p>
912
Misha Brukmand3de5c62004-01-20 00:20:17 +0000913<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000914 <dt><i>--with-llvmgccdir</i></dt>
915 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
916 The value of this option should specify the full pathname of the C/C++ Front
917 End to be used. If this option is not provided, the PATH will be searched for
918 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
919 be inferred from the path found. If the option is not given, and no llvm-gcc
920 can be found in the path then a warning will be produced by
921 <tt>configure</tt> indicating this situation. LLVM may still be built with
922 the <tt>tools-only</tt> target but attempting to build the runtime libraries
923 will fail as these libraries require llvm-gcc and llvm-g++. See
924 <a href="#installcf">Install the GCC Front End</a> for details on installing
925 the C/C++ Front End. See
Duncan Sands551d3e62008-02-14 17:53:22 +0000926 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000927 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000928 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +0000929 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000930 found. Use this if you have multiple tcl installations on your machine and you
931 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
932 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +0000933 option, the LLVM configure script will search for the tcl 8.4 and 8.3
934 releases.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000935 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000936 </dd>
937 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000938 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000939 Enables optimized compilation (debugging symbols are removed
940 and GCC optimization flags are enabled). Note that this is the default
941 setting if you are using the LLVM distribution. The default behavior
942 of an Subversion checkout is to use an unoptimized build (also known as a
943 debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000944 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000945 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +0000946 <dt><i>--enable-debug-runtime</i></dt>
947 <dd>
948 Enables debug symbols in the runtime libraries. The default is to strip
949 debug symbols from the runtime libraries.
950 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000951 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000952 <dd>
John Criswell86a3a482003-12-18 16:43:17 +0000953 Compile the Just In Time (JIT) compiler functionality. This is not
954 available
Misha Brukman560e9892003-11-07 19:43:14 +0000955 on all platforms. The default is dependent on platform, so it is best
956 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000957 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000958 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000959 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
960 <dd>Controls which targets will be built and linked into llc. The default
961 value for <tt>target_options</tt> is "all" which builds and links all
962 available targets. The value "host-only" can be specified to build only a
963 native compiler (no cross-compiler targets available). The "native" target is
964 selected as the target of the build host. You can also specify a comma
965 separated list of target names that you want available in llc. The target
Misha Brukman21a63702008-12-11 18:23:24 +0000966 names use all lower case. The current set of targets is: <br>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000967 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000968 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000969 <dt><i>--enable-doxygen</i></dt>
970 <dd>Look for the doxygen program and enable construction of doxygen based
971 documentation from the source code. This is disabled by default because
972 generating the documentation can take a long time and producess 100s of
973 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +0000974 <dt><i>--with-udis86</i></dt>
975 <dd>LLVM can use external disassembler library for various purposes (now it's
976 used only for examining code produced by JIT). This option will enable usage
977 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
978 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000979</dl>
980
981<p>To configure LLVM, follow these steps:</p>
982
983<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000984 <li><p>Change directory into the object root directory:</p>
John Criswellf531f312003-10-27 18:18:16 +0000985
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000986 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
987
988 <li><p>Run the <tt>configure</tt> script located in the LLVM source
989 tree:</p>
990
991 <div class="doc_code">
992 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
993 </div></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000994</ol>
John Criswell72989a52003-06-12 19:34:44 +0000995
Misha Brukman560e9892003-11-07 19:43:14 +0000996</div>
John Criswell72989a52003-06-12 19:34:44 +0000997
Misha Brukman560e9892003-11-07 19:43:14 +0000998<!-- ======================================================================= -->
999<div class="doc_subsection">
1000 <a name="compile">Compiling the LLVM Suite Source Code</a>
1001</div>
John Criswell72989a52003-06-12 19:34:44 +00001002
Misha Brukman560e9892003-11-07 19:43:14 +00001003<div class="doc_text">
John Criswell71139f22003-07-08 20:35:59 +00001004
Misha Brukman560e9892003-11-07 19:43:14 +00001005<p>Once you have configured LLVM, you can build it. There are three types of
1006builds:</p>
John Criswell71139f22003-07-08 20:35:59 +00001007
Misha Brukmand3de5c62004-01-20 00:20:17 +00001008<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001009 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001010 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001011 These builds are the default when one is using an Subversion checkout and
1012 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1013 used during configuration). The build system will compile the tools and
1014 libraries with debugging information. To get a Debug Build using the
1015 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1016 to <tt>configure</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001017 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001018
1019 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001020 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001021 These builds are enabled with the <tt>--enable-optimized</tt> option to
1022 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1023 <tt>gmake</tt> command line. For these builds, the build system will
1024 compile the tools and libraries with GCC optimizations enabled and strip
1025 debugging information from the libraries and executables it generates.
Chris Lattner1c1595f2009-04-25 22:24:49 +00001026 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001027 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001028
1029 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001030 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001031 These builds are for use with profiling. They compile profiling
1032 information into the code for use with programs like <tt>gprof</tt>.
1033 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1034 on the <tt>gmake</tt> command line.
1035</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001036
Misha Brukman560e9892003-11-07 19:43:14 +00001037<p>Once you have LLVM configured, you can build it by entering the
1038<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001039
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001040<div class="doc_code"><pre>% gmake</pre></div>
John Criswell38cc2b52003-10-10 14:26:14 +00001041
Chris Lattnere0050f02004-07-18 22:32:22 +00001042<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +00001043are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +00001044
1045<p>
1046If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +00001047the parallel build options provided by GNU Make. For example, you could use the
1048command:</p>
John Criswell72989a52003-06-12 19:34:44 +00001049
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001050<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellc5eb4602003-07-03 16:01:38 +00001051
Misha Brukman560e9892003-11-07 19:43:14 +00001052<p>There are several special targets which are useful when working with the LLVM
1053source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001054
Misha Brukmand3de5c62004-01-20 00:20:17 +00001055<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001056 <dt><tt>gmake clean</tt>
1057 <dd>
1058 Removes all files generated by the build. This includes object files,
1059 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001060 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001061
Reid Spencerdfcf7902004-12-08 16:51:31 +00001062 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001063 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +00001064 Removes everything that <tt>gmake clean</tt> does, but also removes files
1065 generated by <tt>configure</tt>. It attempts to return the source tree to the
1066 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001067 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001068
Misha Brukman62a2c1f2004-08-23 20:25:33 +00001069 <dt><tt>gmake install</tt>
1070 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +00001071 Installs LLVM header files, libraries, tools, and documentation in a
1072 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +00001073 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1074 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001075 <br><br>
1076
Reid Spencerdfcf7902004-12-08 16:51:31 +00001077 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001078 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +00001079 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greifa54634a2007-07-06 22:07:22 +00001080 install bitcode libraries into the GCC front end's bitcode library
1081 directory. If you need to update your bitcode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +00001082 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001083 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001084</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001085
Reid Spencerdfcf7902004-12-08 16:51:31 +00001086<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1087details on these <tt>make</tt> targets and descriptions of other targets
1088available.</p>
1089
Misha Brukman560e9892003-11-07 19:43:14 +00001090<p>It is also possible to override default values from <tt>configure</tt> by
1091declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001092
Misha Brukmand3de5c62004-01-20 00:20:17 +00001093<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001094 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1095 <dd>
1096 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001097 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001098
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001099 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001100 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001101 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001102 <br><br>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001103
1104 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1105 <dd>
1106 Perform a Debug build.
1107 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001108
Misha Brukman560e9892003-11-07 19:43:14 +00001109 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1110 <dd>
1111 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001112 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001113
Misha Brukman560e9892003-11-07 19:43:14 +00001114 <dt><tt>gmake VERBOSE=1</tt>
1115 <dd>
1116 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001117 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001118
1119 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1120 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001121 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001122 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001123</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001124
Misha Brukman560e9892003-11-07 19:43:14 +00001125<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1126it and any subdirectories that it contains. Entering any directory inside the
1127LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1128that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001129
Misha Brukman560e9892003-11-07 19:43:14 +00001130</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001131
Misha Brukman560e9892003-11-07 19:43:14 +00001132<!-- ======================================================================= -->
1133<div class="doc_subsection">
Reid Spencer734b74f2006-07-27 06:41:31 +00001134 <a name="cross-compile">Cross-Compiling LLVM</a>
Reid Spencerd966b242006-07-27 05:43:30 +00001135</div>
1136
1137<div class="doc_text">
Jim Grosbach7da1b902009-04-17 17:25:16 +00001138 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1139 executables and libraries to be hosted on a platform different from the
1140 platform where they are build (a Canadian Cross build). To configure a
1141 cross-compile, supply the configure script with <tt>--build</tt> and
1142 <tt>--host</tt> options that are different. The values of these options must
1143 be legal target triples that your GCC compiler supports.</p>
1144
1145 <p>The result of such a build is executables that are not runnable on
1146 on the build host (--build option) but can be executed on the compile host
Reid Spencer734b74f2006-07-27 06:41:31 +00001147 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001148</div>
1149
1150<!-- ======================================================================= -->
1151<div class="doc_subsection">
Misha Brukman560e9892003-11-07 19:43:14 +00001152 <a name="objfiles">The Location of LLVM Object Files</a>
1153</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001154
Misha Brukman560e9892003-11-07 19:43:14 +00001155<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +00001156
Misha Brukman560e9892003-11-07 19:43:14 +00001157<p>The LLVM build system is capable of sharing a single LLVM source tree among
1158several LLVM builds. Hence, it is possible to build LLVM for several different
1159platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001160
Misha Brukman560e9892003-11-07 19:43:14 +00001161<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001162
Misha Brukman560e9892003-11-07 19:43:14 +00001163<ul>
1164 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001165
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001166 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001167
Misha Brukman560e9892003-11-07 19:43:14 +00001168 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1169 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001170
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001171 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001172</ul>
John Criswell72989a52003-06-12 19:34:44 +00001173
Misha Brukman560e9892003-11-07 19:43:14 +00001174<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1175named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001176
Misha Brukmand3de5c62004-01-20 00:20:17 +00001177<dl>
Duncan Sands1567f0f2010-07-08 08:27:18 +00001178 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman560e9892003-11-07 19:43:14 +00001179 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001180 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001181 <dt>Tools
Duncan Sands1567f0f2010-07-08 08:27:18 +00001182 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001183 <dt>Libraries
Duncan Sands1567f0f2010-07-08 08:27:18 +00001184 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001185 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001186 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001187
Misha Brukman560e9892003-11-07 19:43:14 +00001188 <dt>Release Builds
1189 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001190 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001191 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001192 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001193 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001194 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001195 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001196 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001197
Misha Brukman560e9892003-11-07 19:43:14 +00001198 <dt>Profile Builds
1199 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001200 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001201 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001202 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001203 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001204 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001205 </dl>
1206</dl>
John Criswell72989a52003-06-12 19:34:44 +00001207
Misha Brukman560e9892003-11-07 19:43:14 +00001208</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001209
Chris Lattner998c0672004-03-25 20:38:40 +00001210<!-- ======================================================================= -->
1211<div class="doc_subsection">
1212 <a name="optionalconfig">Optional Configuration Items</a>
1213</div>
1214
1215<div class="doc_text">
1216
1217<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001218If you're running on a Linux system that supports the "<a
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001219href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001220module, and you have root access on the system, you can set your system up to
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001221execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattner998c0672004-03-25 20:38:40 +00001222first command may not be required if you are already using the module):</p>
1223
Misha Brukman20b8a6562005-02-03 22:25:23 +00001224<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001225<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001226$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckyb8c923b2009-11-04 06:15:28 +00001227$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001228$ chmod u+x hello.bc (if needed)
1229$ ./hello.bc
Chris Lattner998c0672004-03-25 20:38:40 +00001230</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001231</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001232
1233<p>
Chris Lattnerb5c11742010-02-17 18:33:13 +00001234This allows you to execute LLVM bitcode files directly. On Debian, you
1235can also use this command instead of the 'echo' command above:</p>
Chris Lattner998c0672004-03-25 20:38:40 +00001236</p>
1237
Chris Lattnerb5c11742010-02-17 18:33:13 +00001238<div class="doc_code">
1239<pre>
1240$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1241</pre>
1242</div>
1243
Chris Lattner998c0672004-03-25 20:38:40 +00001244</div>
1245
Misha Brukman560e9892003-11-07 19:43:14 +00001246<!-- *********************************************************************** -->
1247<div class="doc_section">
1248 <a name="layout"><b>Program Layout</b></a>
1249</div>
1250<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001251
Misha Brukman560e9892003-11-07 19:43:14 +00001252<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001253
Misha Brukman560e9892003-11-07 19:43:14 +00001254<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell64f13ab2004-03-12 20:31:37 +00001255href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001256href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001257The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001258
Misha Brukman560e9892003-11-07 19:43:14 +00001259</div>
John Criswell72989a52003-06-12 19:34:44 +00001260
Misha Brukman560e9892003-11-07 19:43:14 +00001261<!-- ======================================================================= -->
Reid Spencer5be4f042004-12-08 16:18:26 +00001262<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1263<div class="doc_text">
1264 <p>This directory contains some simple examples of how to use the LLVM IR and
1265 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001266</div>
John Criswell72989a52003-06-12 19:34:44 +00001267
Misha Brukman560e9892003-11-07 19:43:14 +00001268<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001269<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001270<div class="doc_text">
1271
1272<p>This directory contains public header files exported from the LLVM
1273library. The three main subdirectories of this directory are:</p>
1274
Reid Spencer075de232004-09-05 20:50:22 +00001275<dl>
1276 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1277 <dd>This directory contains all of the LLVM specific header files. This
1278 directory also has subdirectories for different portions of LLVM:
1279 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1280 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001281
Reid Spencer075de232004-09-05 20:50:22 +00001282 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1283 <dd>This directory contains generic support libraries that are provided with
1284 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1285 and a Command Line option processing library store their header files here.
1286 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001287
Reid Spencer075de232004-09-05 20:50:22 +00001288 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1289 <dd>This directory contains header files configured by the <tt>configure</tt>
1290 script. They wrap "standard" UNIX and C header files. Source code can
1291 include these header files which automatically take care of the conditional
1292 #includes that the <tt>configure</tt> script generates.</dd>
1293</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001294</div>
1295
1296<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001297<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001298<div class="doc_text">
1299
1300<p>This directory contains most of the source files of the LLVM system. In LLVM,
1301almost all code exists in libraries, making it very easy to share code among the
1302different <a href="#tools">tools</a>.</p>
1303
Misha Brukmand3de5c62004-01-20 00:20:17 +00001304<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001305 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1306 <dd> This directory holds the core LLVM source files that implement core
1307 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001308
Reid Spencer075de232004-09-05 20:50:22 +00001309 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1310 <dd>This directory holds the source code for the LLVM assembly language parser
1311 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001312
Gabor Greifa54634a2007-07-06 22:07:22 +00001313 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1314 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001315
Reid Spencer075de232004-09-05 20:50:22 +00001316 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001317 different program analyses, such as Dominator Information, Call Graphs,
1318 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001319 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001320
Reid Spencer075de232004-09-05 20:50:22 +00001321 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1322 <dd> This directory contains the source code for the LLVM to LLVM program
1323 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1324 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1325 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001326
Reid Spencer075de232004-09-05 20:50:22 +00001327 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1328 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001329 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1330 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +00001331 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001332
Reid Spencer075de232004-09-05 20:50:22 +00001333 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1334 <dd> This directory contains the major parts of the code generator: Instruction
1335 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001336
Reid Spencer075de232004-09-05 20:50:22 +00001337 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1338 <dd> This directory contains the source level debugger library that makes
1339 it possible to instrument LLVM programs so that a debugger could identify
1340 source code locations at which the program is executing.</dd>
1341
1342 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001343 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer075de232004-09-05 20:50:22 +00001344 at runtime in both interpreted and JIT compiled fashions.</dd>
1345
1346 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1347 <dd> This directory contains the source code that corresponds to the header
1348 files located in <tt>llvm/include/Support/</tt>.</dd>
1349
1350 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1351 <dd>This directory contains the operating system abstraction layer that
1352 shields LLVM from platform-specific coding.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001353</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001354
Misha Brukman560e9892003-11-07 19:43:14 +00001355</div>
John Criswell72989a52003-06-12 19:34:44 +00001356
Misha Brukman560e9892003-11-07 19:43:14 +00001357<!-- ======================================================================= -->
Reid Spencer5be4f042004-12-08 16:18:26 +00001358<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1359<div class="doc_text">
1360 <p>This directory contains projects that are not strictly part of LLVM but are
1361 shipped with LLVM. This is also the directory where you should create your own
1362 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner7b7b6782008-08-11 06:13:31 +00001363 to set up your own project.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001364</div>
1365
1366<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001367<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001368<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001369
Gabor Greifa54634a2007-07-06 22:07:22 +00001370<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman560e9892003-11-07 19:43:14 +00001371used when linking programs with the GCC front end. Most of these libraries are
1372skeleton versions of real libraries; for example, libc is a stripped down
1373version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001374
Misha Brukman560e9892003-11-07 19:43:14 +00001375<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1376end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001377
Misha Brukman560e9892003-11-07 19:43:14 +00001378</div>
John Criswell72989a52003-06-12 19:34:44 +00001379
Misha Brukman560e9892003-11-07 19:43:14 +00001380<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001381<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001382<div class="doc_text">
Reid Spencer075de232004-09-05 20:50:22 +00001383 <p>This directory contains feature and regression tests and other basic sanity
1384 checks on the LLVM infrastructure. These are intended to run quickly and cover
1385 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001386</div>
John Criswell72989a52003-06-12 19:34:44 +00001387
Misha Brukman560e9892003-11-07 19:43:14 +00001388<!-- ======================================================================= -->
Andrew Trick68aa18e42010-09-23 20:26:44 +00001389<div class="doc_subsection"><a name="test-suite"><tt>test-suite</tt></a></div>
Reid Spencer075de232004-09-05 20:50:22 +00001390<div class="doc_text">
John Criswell58594852007-06-29 19:12:31 +00001391 <p>This is not a directory in the normal llvm module; it is a separate
1392 Subversion
1393 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1394 This
John Criswell6ab273c2004-12-08 17:53:54 +00001395 module contains a comprehensive correctness, performance, and benchmarking
1396 test
John Criswell58594852007-06-29 19:12:31 +00001397 suite for LLVM. It is a separate Subversion module because not every LLVM
1398 user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001399 interested in downloading or building such a comprehensive test suite. For
1400 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001401 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001402</div>
John Criswell72989a52003-06-12 19:34:44 +00001403
Reid Spencer075de232004-09-05 20:50:22 +00001404<!-- ======================================================================= -->
1405<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001406<div class="doc_text">
John Criswell38cc2b52003-10-10 14:26:14 +00001407
Misha Brukman560e9892003-11-07 19:43:14 +00001408<p>The <b>tools</b> directory contains the executables built out of the
1409libraries above, which form the main part of the user interface. You can
Duncan Sands142b9ed2010-02-18 14:08:13 +00001410always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001411following is a brief introduction to the most important tools. More detailed
1412information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001413
Misha Brukmand3de5c62004-01-20 00:20:17 +00001414<dl>
John Criswell72989a52003-06-12 19:34:44 +00001415
Reid Spencer075de232004-09-05 20:50:22 +00001416 <dt><tt><b>bugpoint</b></tt></dt>
1417 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001418 optimization passes or code generation backends by narrowing down the
1419 given test case to the minimum number of passes and/or instructions that
1420 still cause a problem, whether it is a crash or miscompilation. See <a
1421 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001422 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001423
Reid Spencer075de232004-09-05 20:50:22 +00001424 <dt><tt><b>llvmc</b></tt></dt>
1425 <dd>The LLVM Compiler Driver. This program can
1426 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1427 pre-processing, translation, optimization, assembly, and linking of programs
1428 all from one command line. <tt>llvmc</tt> also takes care of processing the
Gabor Greifa54634a2007-07-06 22:07:22 +00001429 dependent libraries found in bitcode. This reduces the need to get the
Reid Spencer92815e52004-12-08 18:00:30 +00001430 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswelle1a81202005-05-18 19:43:33 +00001431 note that this tool, while functional, is still experimental and not feature
1432 complete.</dd>
Reid Spencer075de232004-09-05 20:50:22 +00001433
1434 <dt><tt><b>llvm-ar</b></tt></dt>
1435 <dd>The archiver produces an archive containing
Gabor Greifa54634a2007-07-06 22:07:22 +00001436 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001437 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001438
Reid Spencer075de232004-09-05 20:50:22 +00001439 <dt><tt><b>llvm-as</b></tt></dt>
1440 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001441 bitcode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001442
Reid Spencer075de232004-09-05 20:50:22 +00001443 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001444 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer075de232004-09-05 20:50:22 +00001445 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001446
Reid Spencer92815e52004-12-08 18:00:30 +00001447 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001448 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Andrew Trick68aa18e42010-09-23 20:26:44 +00001449 This is the linker invoked by <tt>llvmc</tt>. It performs standard link time
Reid Spencera7974cc2007-02-09 15:59:08 +00001450 optimizations and allows optimization modules to be loaded and run so that
1451 language specific optimizations can be applied at link time.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +00001452
Reid Spencer075de232004-09-05 20:50:22 +00001453 <dt><tt><b>llvm-link</b></tt></dt>
1454 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1455 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001456
Reid Spencer075de232004-09-05 20:50:22 +00001457 <dt><tt><b>lli</b></tt></dt>
1458 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky97467822007-12-03 01:58:01 +00001459 can directly execute LLVM bitcode (although very slowly...). For architectures
1460 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1461 will function as a Just-In-Time compiler (if the functionality was compiled
1462 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001463
Reid Spencer075de232004-09-05 20:50:22 +00001464 <dt><tt><b>llc</b></tt></dt>
1465 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greifa54634a2007-07-06 22:07:22 +00001466 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001467 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001468
Reid Spencer788b0fd2004-12-22 06:29:07 +00001469 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001470 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1471 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001472 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencera7974cc2007-02-09 15:59:08 +00001473 usual machine code output. It works just like any other GCC compiler,
1474 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1475 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell58594852007-06-29 19:12:31 +00001476 separate Subversion module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001477
Reid Spencer075de232004-09-05 20:50:22 +00001478 <dt><tt><b>opt</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001479 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer80f843d2006-08-28 00:34:19 +00001480 transformations (which are specified on the command line), and then outputs
Duncan Sands142b9ed2010-02-18 14:08:13 +00001481 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukman21a63702008-12-11 18:23:24 +00001482 get a list of the program transformations available in LLVM.<br>
Reid Spencer80f843d2006-08-28 00:34:19 +00001483 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greifa54634a2007-07-06 22:07:22 +00001484 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer80f843d2006-08-28 00:34:19 +00001485 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001486</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001487</div>
John Criswell72989a52003-06-12 19:34:44 +00001488
Misha Brukman560e9892003-11-07 19:43:14 +00001489<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001490<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001491<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001492
Misha Brukman560e9892003-11-07 19:43:14 +00001493<p>This directory contains utilities for working with LLVM source code, and some
1494of the utilities are actually required as part of the build process because they
1495are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001496
Misha Brukmand3de5c62004-01-20 00:20:17 +00001497<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001498 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001499 that finds differences between code that LLC generates and code that LLI
1500 generates. This is a useful tool if you are debugging one of them,
1501 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001502 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001503
Misha Brukmand3de5c62004-01-20 00:20:17 +00001504 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001505 syntax-highlighting files which will work with Emacs and XEmacs editors,
1506 providing syntax highlighting support for LLVM assembly files and TableGen
1507 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001508 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001509
Misha Brukmand3de5c62004-01-20 00:20:17 +00001510 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001511 and outputs all non-generated source files, which is useful if one wishes
1512 to do a lot of development across directories and does not want to
1513 individually find each file. One way to use it is to run, for example:
1514 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001515 tree.<br><br>
1516
Reid Spencer075de232004-09-05 20:50:22 +00001517 <dt><tt><b>llvmgrep</b></tt></dt>
1518 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1519 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1520 line. This is a very efficient way of searching the source base for a
1521 particular regular expression.</dd>
1522
Misha Brukmand3de5c62004-01-20 00:20:17 +00001523 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001524 files in the current directory and then compiles and links the tool that
1525 is the first argument. For example, assuming you are in the directory
1526 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1527 simply running <tt>makellvm llc</tt> will make a build of the current
1528 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001529 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001530
Tanya Lattner3e852072007-05-22 06:12:51 +00001531 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukmand3de5c62004-01-20 00:20:17 +00001532 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman560e9892003-11-07 19:43:14 +00001533 cron script to generate nightly status reports of the functionality of
1534 tools, and the results can be seen by following the appropriate link on
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001535 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001536
Misha Brukmand3de5c62004-01-20 00:20:17 +00001537 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001538 the tool used to generate register descriptions, instruction set
1539 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001540 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001541
Misha Brukmand3de5c62004-01-20 00:20:17 +00001542 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001543 syntax-highlighting files which will work with the VIM editor, providing
1544 syntax highlighting support for LLVM assembly files and TableGen
1545 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001546 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001547
Misha Brukman560e9892003-11-07 19:43:14 +00001548</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001549
Misha Brukman560e9892003-11-07 19:43:14 +00001550</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001551
Misha Brukman560e9892003-11-07 19:43:14 +00001552<!-- *********************************************************************** -->
1553<div class="doc_section">
1554 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1555</div>
1556<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001557
Misha Brukman560e9892003-11-07 19:43:14 +00001558<div class="doc_text">
Chris Lattner424d4dc2007-01-04 07:08:27 +00001559<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
Chris Lattner4c445302009-04-10 15:38:51 +00001560so we only include instructions for llvm-gcc4.
Chris Lattner5b560d92006-08-14 20:45:25 +00001561</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001562
1563<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1564from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
Gabor Greifa54634a2007-07-06 22:07:22 +00001565create bitcode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1566the '--emit-llvm' flag is needed to produce LLVM bitcode output. For <i>makefiles</i> and
1567<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bitcode
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001568output.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001569</div>
1570
1571<!-- ======================================================================= -->
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001572<div class="doc_subsection"><a name="tutorial4">Example with llvm-gcc4</a></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001573
1574<div class="doc_text">
1575
1576<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001577 <li><p>First, create a simple C file, name it 'hello.c':</p>
1578
1579<div class="doc_code">
1580<pre>
1581#include &lt;stdio.h&gt;
1582
1583int main() {
1584 printf("hello world\n");
1585 return 0;
1586}
1587</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001588
1589 <li><p>Next, compile the C file into a native executable:</p>
1590
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001591 <div class="doc_code"><pre>% llvm-gcc hello.c -o hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001592
1593 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1594 -c arguments work as usual (producing a native .s or .o file,
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001595 respectively).</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001596
Gabor Greifa54634a2007-07-06 22:07:22 +00001597 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001598
1599 <div class="doc_code">
1600 <pre>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001601
1602 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1603 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1604 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Gabor Greifa54634a2007-07-06 22:07:22 +00001605 the bitcode file.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001606
1607 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1608 </p></li>
1609
1610 <li><p>Run the program in both forms. To run the program, use:</p>
1611
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001612 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001613
1614 <p>and</p>
1615
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001616 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001617
1618 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001619 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001620
1621 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1622 code:</p>
1623
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001624<div class="doc_code">
1625<pre>llvm-dis &lt; hello.bc | less</pre>
1626</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001627
1628 <li><p>Compile the program to native assembly using the LLC code
1629 generator:</p>
1630
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001631 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001632
1633 <li><p>Assemble the native assembly language file into a program:</p>
1634
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001635<div class="doc_code">
1636<pre>
1637<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1638
1639<b>Others:</b> % gcc hello.s -o hello.native
1640</pre>
1641</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001642
1643 <li><p>Execute the native code program:</p>
1644
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001645 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001646
1647 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1648 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001649 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001650
1651</ol>
1652
1653</div>
1654
John Criswell72989a52003-06-12 19:34:44 +00001655
Misha Brukman560e9892003-11-07 19:43:14 +00001656<!-- *********************************************************************** -->
1657<div class="doc_section">
1658 <a name="problems">Common Problems</a>
1659</div>
1660<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001661
Misha Brukman560e9892003-11-07 19:43:14 +00001662<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +00001663
Misha Brukman560e9892003-11-07 19:43:14 +00001664<p>If you are having problems building or using LLVM, or if you have any other
1665general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1666Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001667
Misha Brukman560e9892003-11-07 19:43:14 +00001668</div>
John Criswell72989a52003-06-12 19:34:44 +00001669
Misha Brukman560e9892003-11-07 19:43:14 +00001670<!-- *********************************************************************** -->
1671<div class="doc_section">
1672 <a name="links">Links</a>
1673</div>
1674<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001675
Misha Brukman560e9892003-11-07 19:43:14 +00001676<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001677
Bill Wendlingcb13d702008-07-22 01:10:25 +00001678<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman560e9892003-11-07 19:43:14 +00001679some simple things... there are many more interesting and complicated things
1680that you can do that aren't documented here (but we'll gladly accept a patch
1681if you want to write something up!). For more information about LLVM, check
1682out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001683
Misha Brukman560e9892003-11-07 19:43:14 +00001684<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001685 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1686 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1687 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001688 that Uses LLVM</a></li>
1689</ul>
1690
1691</div>
1692
1693<!-- *********************************************************************** -->
1694
1695<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001696<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001697 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001698 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001699 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +00001700 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001701
Misha Brukman74d4df82003-11-22 01:30:01 +00001702 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001703 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencerca058542006-03-14 05:39:39 +00001704 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001705 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001706</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001707</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001708</html>