blob: 7360893520f64643bef4205f8c3ca7f699516d2c [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
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000011<h1>
Misha Brukman560e9892003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000013</h1>
John Criswell72989a52003-06-12 19:34:44 +000014
Misha Brukman560e9892003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +000019 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000023 </ol></li>
John Criswell3ef61af2003-06-30 21:59:07 +000024
Misha Brukman560e9892003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell71139f22003-07-08 20:35:59 +000026 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000032 <li><a href="#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>,
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +000065 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner020e1fc2004-05-23 21:07:27 +000066 <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<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000073<h2>
74 <a name="overview">Overview</a>
75</h2>
Misha Brukman560e9892003-11-07 19:43:14 +000076<!-- *********************************************************************** -->
77
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +000078<div>
Misha Brukman560e9892003-11-07 19:43:14 +000079
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<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000105<h2>
106 <a name="quickstart">Getting Started Quickly (A Summary)</a>
107</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000108<!-- *********************************************************************** -->
109
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000110<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000111
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++
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000119 (see <a href="#installcf">Install the GCC Front End</a> for details):
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>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000125 <li>Note: On Windows, use <a href="http://www.7-zip.org/">7-Zip</a> or a similar archiving tool.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000126 <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<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000194<h2>
195 <a name="requirements">Requirements</a>
196</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000197<!-- *********************************************************************** -->
198
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000199<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000200
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
Misha Brukman560e9892003-11-07 19:43:14 +0000205<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000206<h3>
207 <a name="hardware">Hardware</a>
208</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000209
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000210<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000211
212<p>LLVM is known to work on the following platforms:</p>
213
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000214<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000215<tr>
216 <th>OS</th>
217 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000218 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000219</tr>
220<tr>
Chris Lattner6bad1372009-07-22 04:21:40 +0000221 <td>AuroraUX</td>
222 <td>x86<sup><a href="#pf_1">1</a></sup></td>
223 <td>GCC</td>
Chris Lattner3a56ae82009-07-21 22:47:03 +0000224</tr>
225<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000226 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000227 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000228 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000229</tr>
230<tr>
Edward O'Callaghanab8a04c2009-08-04 05:24:28 +0000231 <td>Linux</td>
232 <td>amd64</td>
233 <td>GCC</td>
234</tr>
235<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000236 <td>Solaris</td>
237 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000238 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000239</tr>
240<tr>
241 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000242 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000243 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000244</tr>
245<tr>
Bill Wendling5d32b702010-12-15 01:35:55 +0000246 <td>FreeBSD</td>
247 <td>amd64</td>
248 <td>GCC</td>
249</tr>
250<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000251 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000252 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000253 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000254</tr>
255<tr>
Scott Michel4799ea72008-03-18 23:13:26 +0000256 <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 +0000257 <td>x86</td>
258 <td>GCC</td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000259</tr>
260<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000261 <td>Cygwin/Win32</td>
Anton Korobeynikovd0a0bc32009-12-09 17:26:02 +0000262 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
263 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000264 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000265</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000266<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000267 <td>MinGW/Win32</td>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000268 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000269 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
270 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000271 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000272</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000273</table>
274
275<p>LLVM has partial support for the following platforms:</p>
276
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000277<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000278<tr>
279 <th>OS</th>
280 <th>Arch</th>
281 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000282</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000283<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000284 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000285 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000286 <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 +0000287<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000288 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000289 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000290 <td>GCC</td>
291</tr>
292<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000293 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000294 <td>PowerPC</td>
295 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000296</tr>
John Criswell05990f32005-05-09 16:49:59 +0000297
298<tr>
299 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
300 <td>Alpha</td>
301 <td>GCC</td>
302</tr>
303<tr>
304 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
305 <td>Itanium (IA-64)</td>
306 <td>GCC</td>
307</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000308<tr>
309 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
310 <td>Itanium (IA-64)</td>
311 <td>HP aCC</td>
312</tr>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000313<tr>
314 <td>Windows x64</td>
315 <td>x86-64</td>
316 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
317</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000318</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000319
Misha Brukman77723092005-02-09 21:01:26 +0000320<p><b>Notes:</b></p>
321
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000322<div class="doc_notes">
323<ol>
324<li><a name="pf_1">Code generation supported for Pentium processors and
325up</a></li>
326<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
327<li><a name="pf_3">No native code generation</a></li>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000328<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 +0000329<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattnerb7481cf2009-01-02 07:10:51 +0000330<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell05990f32005-05-09 16:49:59 +0000331<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000332<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
333 generated by LLVM properly.</a></li>
Chris Lattner26c74442008-11-09 17:19:14 +0000334<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 +0000335 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner26c74442008-11-09 17:19:14 +0000336 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
337 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel4799ea72008-03-18 23:13:26 +0000338 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000339<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
340 version of the perl package, and be sure it appears in your path
341 before any Windows-based versions such as Strawberry Perl and
342 ActivePerl, as these have Windows-specifics that will cause the
343 build to fail.</a></li>
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000344<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000345 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000346<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000347 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukman77723092005-02-09 21:01:26 +0000348</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000349</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000350
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000351<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 +0000352mode, depending on the system (it is so large because of all the debugging
353information and the fact that the libraries are statically linked into multiple
Chris Lattner0cb89772009-04-25 22:08:52 +0000354tools). If you do not need many of the tools and you are space-conscious, you
355can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
356requires considerably less space.</p>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000357
Misha Brukman560e9892003-11-07 19:43:14 +0000358<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
359guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greifa54634a2007-07-06 22:07:22 +0000360able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman560e9892003-11-07 19:43:14 +0000361generation should work as well, although the generated native code may not work
362on your platform.</p>
363
364<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 +0000365to work on another platform, you can download a copy of the source and <a
Duncan Sands551d3e62008-02-14 17:53:22 +0000366href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000367
368</div>
369
370<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000371<h3>
372 <a name="software">Software</a>
373</h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000374<div>
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>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000390 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000391 <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>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000396 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000397 <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
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +0000407 <!-- FIXME:
408 Do we support dg?
409 Are DejaGnu and expect obsolete?
410 Shall we mention Python? -->
411
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000412 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000413 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
414 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000415 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000416 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000417
Reid Spencer38fcf302004-11-15 21:15:12 +0000418 <tr>
419 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
420 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000421 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000422 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000423
Reid Spencer38fcf302004-11-15 21:15:12 +0000424 <tr>
425 <td><a href="http://expect.nist.gov/">expect</a></td>
426 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000427 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000428 </tr>
429
430 <tr>
431 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000432 <td>&ge;5.6.0</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000433 <td>Nightly tester, utilities</td>
434 </tr>
435
436 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000437 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
438 <td>1.4</td>
439 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000440 </tr>
441
442 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000443 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000444 <td>2.60</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000445 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
446 </tr>
447
448 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000449 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000450 <td>1.9.6</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000451 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
452 </tr>
453
454 <tr>
455 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000456 <td>1.5.22</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000457 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000458 </tr>
459
460 </table>
461
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000462 <p><b>Notes:</b></p>
463 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000464 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000465 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000466 need to build the other languages for LLVM's purposes.</a> See
467 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell58594852007-06-29 19:12:31 +0000468 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000469 latest LLVM sources. If you're working from a release distribution, you
John Criswell58594852007-06-29 19:12:31 +0000470 don't need Subversion.</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000471 <li><a name="sf3">Only needed if you want to run the automated test
472 suite in the <tt>llvm/test</tt> directory.</a></li>
473 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser4518c862010-05-19 07:00:17 +0000474 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
475 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer098fce42004-12-09 17:55:37 +0000476 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000477 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000478 </div>
479
Reid Spencer38fcf302004-11-15 21:15:12 +0000480 <p>Additionally, your compilation host is expected to have the usual
481 plethora of Unix utilities. Specifically:</p>
482 <ul>
483 <li><b>ar</b> - archive library builder</li>
484 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
485 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
486 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000487 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000488 <li><b>cp</b> - copy files</li>
489 <li><b>date</b> - print the current date/time </li>
490 <li><b>echo</b> - print to standard output</li>
491 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000492 <li><b>find</b> - find files/dirs in a file system</li>
493 <li><b>grep</b> - regular expression search utility</li>
494 <li><b>gzip*</b> - gzip command for distribution generation</li>
495 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
496 <li><b>install</b> - install directories/files </li>
497 <li><b>mkdir</b> - create a directory</li>
498 <li><b>mv</b> - move (rename) files</li>
499 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000500 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000501 <li><b>sed</b> - stream editor for transforming output</li>
502 <li><b>sh</b> - Bourne shell for make build scripts</li>
503 <li><b>tar</b> - tape archive for distribution generation</li>
504 <li><b>test</b> - test things in file system</li>
505 <li><b>unzip*</b> - unzip command for distribution checking</li>
506 <li><b>zip*</b> - zip command for distribution generation</li>
507 </ul>
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<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000511<h3>
Chris Lattner55514822007-06-19 05:52:36 +0000512 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000513</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000514
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000515<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000516
517<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
518bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner29052c82006-06-16 17:20:33 +0000519to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000520successfully with them (however, see important notes below). Other versions
521of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000522here are known to not work. If you are using one of these versions, please try
523to upgrade your GCC to something more recent. If you run into a problem with a
524version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
525us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
526of GCC you are using.
527</p>
528
529<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
530problems in the STL that effectively prevent it from compiling LLVM.
531</p>
532
Chris Lattner419df4e2008-02-13 17:50:24 +0000533<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
534a bogus template error. This was fixed in later GCCs.</p>
John Criswellfd769452004-11-23 22:06:24 +0000535
Chris Lattnere0050f02004-07-18 22:32:22 +0000536<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
537href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
538the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000539
Chris Lattner58247622005-02-13 22:20:49 +0000540<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 +0000541 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner58247622005-02-13 22:20:49 +0000542 to a newer version</a> if possible.</p>
543<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
544 possibly others) does not compile LLVM correctly (it appears that exception
545 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
546 to a newer version of GCC.</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000547<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000548 code generator, causing an infinite loop in the llvm-gcc build when built
549 with optimizations enabled (i.e. a release build).</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000550<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000551 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
552 correctly compiles LLVM at -O2. A work around is to build release LLVM
553 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000554<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 +0000555 miscompiles portions of LLVM</a>.</p>
Chris Lattner059a8df2007-11-01 04:20:16 +0000556<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
557 when building with optimizations enabled. It appears to work with
558 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
559 build.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000560<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
561 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000562<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
563 default with ENABLE_OPTIMIZED=1. To work around this, build with
564 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000565<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
566 compiling some files. At the time of this writing, GCC mainline (4.2)
567 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000568<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
569 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
570 code. LLVM will appear to mostly work but will be buggy, e.g. failing
571 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000572<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
573platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbar2a575452008-10-11 18:40:33 +0000574<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
575to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
576about symbols remaining in the table on destruction.</p>
Nuno Lopes94993852008-12-10 16:11:10 +0000577<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 +0000578as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Anton Korobeynikovdad58712009-05-04 10:24:46 +0000579<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
580 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
581 with link errors when using this GCC version.</p>
Chris Lattnereba6c722009-09-10 16:25:02 +0000582<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 +0000583<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
584when optimizations are turned on. The symptom is an infinite loop in
Chris Lattnereba6c722009-09-10 16:25:02 +0000585FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewyckyabe8c132010-10-07 22:30:47 +0000586<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5871</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
588one symptom of the problem.
Reid Spencer6291ddc2006-11-04 00:33:42 +0000589<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
590long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
591defined in a discarded section. You can safely ignore these messages as they are
592erroneous and the linkage is correct. These messages disappear using ld
5932.17.</p>
Chris Lattner55514822007-06-19 05:52:36 +0000594
595<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
596href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
597causes huge link times (minutes instead of seconds) when building LLVM. We
598recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
599
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000600<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewycky2db07612009-02-25 06:29:47 +0000601<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
602which causes intermittent failures when building LLVM with position independent
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000603code. The symptom is an error about cyclic dependencies. We recommend
604upgrading to a newer version of Gold.</p>
Nick Lewycky2db07612009-02-25 06:29:47 +0000605
Misha Brukman560e9892003-11-07 19:43:14 +0000606</div>
607
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000608</div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000609
Misha Brukman560e9892003-11-07 19:43:14 +0000610<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000611<h2>
612 <a name="starting">Getting Started with LLVM</a>
613</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000614<!-- *********************************************************************** -->
615
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000616<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000617
618<p>The remainder of this guide is meant to get you up and running with
619LLVM and to give you some basic information about the LLVM environment.</p>
620
621<p>The later sections of this guide describe the <a
622href="#layout">general layout</a> of the the LLVM source tree, a <a
623href="#tutorial">simple example</a> using the LLVM tool chain, and <a
624href="#links">links</a> to find more information about LLVM or to get
625help via e-mail.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000626
Misha Brukman560e9892003-11-07 19:43:14 +0000627<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000628<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000629 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000630</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000631
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000632<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000633
634<p>Throughout this manual, the following names are used to denote paths
635specific to the local system and working environment. <i>These are not
636environment variables you need to set but just strings used in the rest
637of this document below</i>. In any of the examples below, simply replace
638each of these names with the appropriate pathname on your local system.
639All these paths are absolute:</p>
640
Misha Brukmand3de5c62004-01-20 00:20:17 +0000641<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000642 <dt>SRC_ROOT
643 <dd>
644 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000645 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000646
Misha Brukman560e9892003-11-07 19:43:14 +0000647 <dt>OBJ_ROOT
648 <dd>
649 This is the top level directory of the LLVM object tree (i.e. the
650 tree where object files and compiled programs will be placed. It
651 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000652 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000653
654 <dt>LLVMGCCDIR
655 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000656 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000657 <p>
658 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000659 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000660</dl>
661
662</div>
663
664<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000665<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000666 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000667</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000668
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000669<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000670
671<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000672In order to compile and use LLVM, you may need to set some environment
673variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000674
Misha Brukmand3de5c62004-01-20 00:20:17 +0000675<dl>
Gabor Greifa54634a2007-07-06 22:07:22 +0000676 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000677 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greifa54634a2007-07-06 22:07:22 +0000678 locations of your bitcode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000679 convenience since you can specify the paths using the -L options of the
Gabor Greifa54634a2007-07-06 22:07:22 +0000680 tools and the C/C++ front-end will automatically use the bitcode files
John Criswelle1a81202005-05-18 19:43:33 +0000681 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000682 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000683</dl>
684
685</div>
686
687<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000688<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000689 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000690</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000691
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000692<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000693
694<p>
695If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000696can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000697suite and the LLVM GCC front end compiled for your platform. There is an
698additional test suite that is optional. Each file is a TAR archive that is
699compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000700</p>
701
Misha Brukmand4528ea2005-02-02 18:01:57 +0000702<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000703<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000704 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukman21a63702008-12-11 18:23:24 +0000705 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000706
Misha Brukmand4528ea2005-02-02 18:01:57 +0000707 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000708 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000709
Misha Brukman4050d152008-12-29 19:38:58 +0000710 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
711 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukman21a63702008-12-11 18:23:24 +0000712 directory for build instructions.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000713
Misha Brukman4050d152008-12-29 19:38:58 +0000714 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
715 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000716
Misha Brukman560e9892003-11-07 19:43:14 +0000717</dl>
718
719</div>
720
721<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000722<h3>
John Criswell58594852007-06-29 19:12:31 +0000723 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000724</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000725
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000726<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000727
John Criswell58594852007-06-29 19:12:31 +0000728<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattner1c1595f2009-04-25 22:24:49 +0000729the entire source code. All you need to do is check it out from Subversion as
Misha Brukman560e9892003-11-07 19:43:14 +0000730follows:</p>
731
732<ul>
John Criswell58594852007-06-29 19:12:31 +0000733 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov4c04a93332007-06-29 20:56:49 +0000734 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
735 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell58594852007-06-29 19:12:31 +0000736 llvm</tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000737</ul>
738
John Criswell58594852007-06-29 19:12:31 +0000739
Misha Brukman560e9892003-11-07 19:43:14 +0000740<p>This will create an '<tt>llvm</tt>' directory in the current
741directory and fully populate it with the LLVM source code, Makefiles,
742test directories, and local copies of documentation files.</p>
743
Misha Brukmand3de5c62004-01-20 00:20:17 +0000744<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikoveaa836b2007-06-29 23:13:42 +0000745revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikov09ca62d2007-06-30 00:00:57 +0000746'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman52757bf2008-12-17 16:27:23 +0000747subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000748
John Criswell86a3a482003-12-18 16:43:17 +0000749<ul>
Bill Wendlingdb624242011-04-04 23:42:51 +0000750<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc4735872010-10-06 23:50:30 +0000751<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner3d7ec7b2010-10-06 05:36:01 +0000752<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattner9d3ba88b2009-10-23 06:20:06 +0000753<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000754<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman52757bf2008-12-17 16:27:23 +0000755<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattner610e89d2008-06-09 06:02:09 +0000756<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattner779593c2008-02-12 02:42:55 +0000757<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner586eb8e2007-09-28 22:50:54 +0000758<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000759<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000760<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000761<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000762<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000763<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000764<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000765<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000766<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000767<li>Release 1.2: <b>RELEASE_12</b></li>
768<li>Release 1.1: <b>RELEASE_11</b></li>
769<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000770</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000771
Reid Spencerdfcf7902004-12-08 16:51:31 +0000772<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 +0000773you get it from the Subversion repository:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000774
775<div class="doc_code">
Reid Spencerdfcf7902004-12-08 16:51:31 +0000776<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000777% cd llvm/projects
Andrew Trick68aa18e42010-09-23 20:26:44 +0000778% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencerdfcf7902004-12-08 16:51:31 +0000779</pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000780</div>
781
Reid Spencerdfcf7902004-12-08 16:51:31 +0000782<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000783configured by the LLVM configure script as well as automatically updated when
John Criswell58594852007-06-29 19:12:31 +0000784you run <tt>svn update</tt>.</p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000785
Chris Lattner40872ad2007-03-06 06:27:34 +0000786<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 +0000787and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner40872ad2007-03-06 06:27:34 +0000788instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000789
Misha Brukman560e9892003-11-07 19:43:14 +0000790</div>
791
792<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000793<h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000794 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000795</h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000796
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000797<div>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000798
799<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
800 sync automatically with each Subversion commit and contain all necessary
801 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
802 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000803 read-only GIT clone of LLVM via:</p>
804
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000805<pre>
806% git clone http://llvm.org/git/llvm.git
807</pre>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000808
809</div>
810
811<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000812<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000813 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000814</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000815
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000816<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000817
Jim Grosbach67584fe2009-12-17 17:18:11 +0000818<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
819GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trick68aa18e42010-09-23 20:26:44 +0000820It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach67584fe2009-12-17 17:18:11 +0000821you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattner24b71352007-02-14 07:33:00 +0000822main LLVM repository.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000823
Jim Grosbach67584fe2009-12-17 17:18:11 +0000824<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000825like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000826
827<ol>
828 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukman4050d152008-12-29 19:38:58 +0000829 <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 +0000830 -</tt></li>
831</ol>
832
Jim Grosbach67584fe2009-12-17 17:18:11 +0000833<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
834<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
835Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
836to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
837<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
838
839<p>If you now want to build LLVM from source, when you configure LLVM, it will
840automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trick68aa18e42010-09-23 20:26:44 +0000841use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach67584fe2009-12-17 17:18:11 +0000842point after building the main LLVM repository: just reconfigure llvm and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000843test-suite will pick it up.
Chris Lattner24b71352007-02-14 07:33:00 +0000844</p>
845
Jim Grosbach67584fe2009-12-17 17:18:11 +0000846<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
847versions of the required w32api and mingw-runtime binaries. The last remaining step for
848Windows users is to simply uncompress the binary binutils package from
849<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
850front end installation steps are not quite the same as a typical manual MinGW installation,
851they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000852
Jim Grosbach67584fe2009-12-17 17:18:11 +0000853<p>To install binutils on Windows:</p>
854
855<ol>
856 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
857 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
858 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
859</ol>
860
861<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
862example, the binary distribution may include an old version of a system header
863file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
864libraries not available on your system. In cases like these, you may want to try
865<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
866this is much easier now than it was in the past.</p>
867
868<p>We also do not currently support updating of the GCC front end by manually overlaying
869newer versions of the w32api and mingw-runtime binary packages that may become available
870from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
871a self-contained convenience package that requires Windows users to simply download and
872uncompress the GNU Binutils binary package from the MinGW project.</p>
873
874<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
875binaries is not as easy as previously described, or you would like to suggest improvements,
876please let us know how you would like to see things improved by dropping us a note on our
877<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000878
879</div>
880
881<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000882<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000883 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000884</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000885
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000886<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000887
John Criswell58594852007-06-29 19:12:31 +0000888 <p>Once checked out from the Subversion repository, the LLVM suite source
889 code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000890configured via the <tt>configure</tt> script. This script sets variables in the
891various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
892<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
893the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000894
895<p>The following environment variables are used by the <tt>configure</tt>
896script to configure the build system:</p>
897
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000898<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +0000899 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000900 <tr>
901 <td>CC</td>
902 <td>Tells <tt>configure</tt> which C compiler to use. By default,
903 <tt>configure</tt> will look for the first GCC C compiler in
904 <tt>PATH</tt>. Use this variable to override
905 <tt>configure</tt>'s default behavior.</td>
906 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000907 <tr>
908 <td>CXX</td>
909 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
910 <tt>configure</tt> will look for the first GCC C++ compiler in
911 <tt>PATH</tt>. Use this variable to override
912 <tt>configure</tt>'s default behavior.</td>
913 </tr>
914</table>
915
916<p>The following options can be used to set or enable LLVM specific options:</p>
917
Misha Brukmand3de5c62004-01-20 00:20:17 +0000918<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000919 <dt><i>--with-llvmgccdir</i></dt>
920 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
921 The value of this option should specify the full pathname of the C/C++ Front
922 End to be used. If this option is not provided, the PATH will be searched for
923 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
924 be inferred from the path found. If the option is not given, and no llvm-gcc
925 can be found in the path then a warning will be produced by
926 <tt>configure</tt> indicating this situation. LLVM may still be built with
927 the <tt>tools-only</tt> target but attempting to build the runtime libraries
928 will fail as these libraries require llvm-gcc and llvm-g++. See
929 <a href="#installcf">Install the GCC Front End</a> for details on installing
930 the C/C++ Front End. See
Duncan Sands551d3e62008-02-14 17:53:22 +0000931 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000932 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000933 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +0000934 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000935 found. Use this if you have multiple tcl installations on your machine and you
936 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
937 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +0000938 option, the LLVM configure script will search for the tcl 8.4 and 8.3
939 releases.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000940 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000941 </dd>
942 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000943 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000944 Enables optimized compilation (debugging symbols are removed
945 and GCC optimization flags are enabled). Note that this is the default
946 setting if you are using the LLVM distribution. The default behavior
947 of an Subversion checkout is to use an unoptimized build (also known as a
948 debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000949 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000950 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +0000951 <dt><i>--enable-debug-runtime</i></dt>
952 <dd>
953 Enables debug symbols in the runtime libraries. The default is to strip
954 debug symbols from the runtime libraries.
955 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000956 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000957 <dd>
John Criswell86a3a482003-12-18 16:43:17 +0000958 Compile the Just In Time (JIT) compiler functionality. This is not
959 available
Misha Brukman560e9892003-11-07 19:43:14 +0000960 on all platforms. The default is dependent on platform, so it is best
961 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000962 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000963 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000964 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
965 <dd>Controls which targets will be built and linked into llc. The default
966 value for <tt>target_options</tt> is "all" which builds and links all
967 available targets. The value "host-only" can be specified to build only a
968 native compiler (no cross-compiler targets available). The "native" target is
969 selected as the target of the build host. You can also specify a comma
970 separated list of target names that you want available in llc. The target
Misha Brukman21a63702008-12-11 18:23:24 +0000971 names use all lower case. The current set of targets is: <br>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000972 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000973 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000974 <dt><i>--enable-doxygen</i></dt>
975 <dd>Look for the doxygen program and enable construction of doxygen based
976 documentation from the source code. This is disabled by default because
977 generating the documentation can take a long time and producess 100s of
978 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +0000979 <dt><i>--with-udis86</i></dt>
980 <dd>LLVM can use external disassembler library for various purposes (now it's
981 used only for examining code produced by JIT). This option will enable usage
982 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
983 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000984</dl>
985
986<p>To configure LLVM, follow these steps:</p>
987
988<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000989 <li><p>Change directory into the object root directory:</p>
John Criswellf531f312003-10-27 18:18:16 +0000990
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000991 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
992
993 <li><p>Run the <tt>configure</tt> script located in the LLVM source
994 tree:</p>
995
996 <div class="doc_code">
997 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
998 </div></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000999</ol>
John Criswell72989a52003-06-12 19:34:44 +00001000
Misha Brukman560e9892003-11-07 19:43:14 +00001001</div>
John Criswell72989a52003-06-12 19:34:44 +00001002
Misha Brukman560e9892003-11-07 19:43:14 +00001003<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001004<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001005 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001006</h3>
John Criswell72989a52003-06-12 19:34:44 +00001007
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001008<div>
John Criswell71139f22003-07-08 20:35:59 +00001009
Misha Brukman560e9892003-11-07 19:43:14 +00001010<p>Once you have configured LLVM, you can build it. There are three types of
1011builds:</p>
John Criswell71139f22003-07-08 20:35:59 +00001012
Misha Brukmand3de5c62004-01-20 00:20:17 +00001013<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001014 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001015 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001016 These builds are the default when one is using an Subversion checkout and
1017 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1018 used during configuration). The build system will compile the tools and
1019 libraries with debugging information. To get a Debug Build using the
1020 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1021 to <tt>configure</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001022 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001023
1024 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001025 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001026 These builds are enabled with the <tt>--enable-optimized</tt> option to
1027 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1028 <tt>gmake</tt> command line. For these builds, the build system will
1029 compile the tools and libraries with GCC optimizations enabled and strip
1030 debugging information from the libraries and executables it generates.
Chris Lattner1c1595f2009-04-25 22:24:49 +00001031 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001032 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001033
1034 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001035 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001036 These builds are for use with profiling. They compile profiling
1037 information into the code for use with programs like <tt>gprof</tt>.
1038 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1039 on the <tt>gmake</tt> command line.
1040</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001041
Misha Brukman560e9892003-11-07 19:43:14 +00001042<p>Once you have LLVM configured, you can build it by entering the
1043<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001044
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001045<div class="doc_code"><pre>% gmake</pre></div>
John Criswell38cc2b52003-10-10 14:26:14 +00001046
Chris Lattnere0050f02004-07-18 22:32:22 +00001047<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +00001048are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +00001049
1050<p>
1051If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +00001052the parallel build options provided by GNU Make. For example, you could use the
1053command:</p>
John Criswell72989a52003-06-12 19:34:44 +00001054
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001055<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellc5eb4602003-07-03 16:01:38 +00001056
Misha Brukman560e9892003-11-07 19:43:14 +00001057<p>There are several special targets which are useful when working with the LLVM
1058source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001059
Misha Brukmand3de5c62004-01-20 00:20:17 +00001060<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001061 <dt><tt>gmake clean</tt>
1062 <dd>
1063 Removes all files generated by the build. This includes object files,
1064 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001065 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001066
Reid Spencerdfcf7902004-12-08 16:51:31 +00001067 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001068 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +00001069 Removes everything that <tt>gmake clean</tt> does, but also removes files
1070 generated by <tt>configure</tt>. It attempts to return the source tree to the
1071 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001072 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001073
Misha Brukman62a2c1f2004-08-23 20:25:33 +00001074 <dt><tt>gmake install</tt>
1075 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +00001076 Installs LLVM header files, libraries, tools, and documentation in a
1077 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +00001078 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1079 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001080 <br><br>
1081
Reid Spencerdfcf7902004-12-08 16:51:31 +00001082 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001083 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +00001084 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greifa54634a2007-07-06 22:07:22 +00001085 install bitcode libraries into the GCC front end's bitcode library
1086 directory. If you need to update your bitcode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +00001087 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001088 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001089</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001090
Reid Spencerdfcf7902004-12-08 16:51:31 +00001091<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1092details on these <tt>make</tt> targets and descriptions of other targets
1093available.</p>
1094
Misha Brukman560e9892003-11-07 19:43:14 +00001095<p>It is also possible to override default values from <tt>configure</tt> by
1096declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001097
Misha Brukmand3de5c62004-01-20 00:20:17 +00001098<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001099 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1100 <dd>
1101 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001102 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001103
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001104 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001105 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001106 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001107 <br><br>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001108
1109 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1110 <dd>
1111 Perform a Debug build.
1112 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001113
Misha Brukman560e9892003-11-07 19:43:14 +00001114 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1115 <dd>
1116 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001117 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001118
Misha Brukman560e9892003-11-07 19:43:14 +00001119 <dt><tt>gmake VERBOSE=1</tt>
1120 <dd>
1121 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001122 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001123
1124 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1125 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001126 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001127 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001128</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001129
Misha Brukman560e9892003-11-07 19:43:14 +00001130<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1131it and any subdirectories that it contains. Entering any directory inside the
1132LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1133that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001134
Misha Brukman560e9892003-11-07 19:43:14 +00001135</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001136
Misha Brukman560e9892003-11-07 19:43:14 +00001137<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001138<h3>
Reid Spencer734b74f2006-07-27 06:41:31 +00001139 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001140</h3>
Reid Spencerd966b242006-07-27 05:43:30 +00001141
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001142<div>
Jim Grosbach7da1b902009-04-17 17:25:16 +00001143 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1144 executables and libraries to be hosted on a platform different from the
1145 platform where they are build (a Canadian Cross build). To configure a
1146 cross-compile, supply the configure script with <tt>--build</tt> and
1147 <tt>--host</tt> options that are different. The values of these options must
1148 be legal target triples that your GCC compiler supports.</p>
1149
1150 <p>The result of such a build is executables that are not runnable on
1151 on the build host (--build option) but can be executed on the compile host
Reid Spencer734b74f2006-07-27 06:41:31 +00001152 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001153</div>
1154
1155<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001156<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001157 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001158</h3>
John Criswell38cc2b52003-10-10 14:26:14 +00001159
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001160<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001161
Misha Brukman560e9892003-11-07 19:43:14 +00001162<p>The LLVM build system is capable of sharing a single LLVM source tree among
1163several LLVM builds. Hence, it is possible to build LLVM for several different
1164platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001165
Misha Brukman560e9892003-11-07 19:43:14 +00001166<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001167
Misha Brukman560e9892003-11-07 19:43:14 +00001168<ul>
1169 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001170
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001171 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001172
Misha Brukman560e9892003-11-07 19:43:14 +00001173 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1174 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001175
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001176 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001177</ul>
John Criswell72989a52003-06-12 19:34:44 +00001178
Misha Brukman560e9892003-11-07 19:43:14 +00001179<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1180named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001181
Misha Brukmand3de5c62004-01-20 00:20:17 +00001182<dl>
Duncan Sands1567f0f2010-07-08 08:27:18 +00001183 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman560e9892003-11-07 19:43:14 +00001184 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001185 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001186 <dt>Tools
Duncan Sands1567f0f2010-07-08 08:27:18 +00001187 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001188 <dt>Libraries
Duncan Sands1567f0f2010-07-08 08:27:18 +00001189 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001190 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001191 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001192
Misha Brukman560e9892003-11-07 19:43:14 +00001193 <dt>Release Builds
1194 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001195 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001196 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001197 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001198 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001199 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001200 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001201 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001202
Misha Brukman560e9892003-11-07 19:43:14 +00001203 <dt>Profile Builds
1204 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001205 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001206 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001207 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001208 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001209 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001210 </dl>
1211</dl>
John Criswell72989a52003-06-12 19:34:44 +00001212
Misha Brukman560e9892003-11-07 19:43:14 +00001213</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001214
Chris Lattner998c0672004-03-25 20:38:40 +00001215<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001216<h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001217 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001218</h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001219
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001220<div>
Chris Lattner998c0672004-03-25 20:38:40 +00001221
1222<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001223If you're running on a Linux system that supports the "<a
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001224href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001225module, and you have root access on the system, you can set your system up to
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001226execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattner998c0672004-03-25 20:38:40 +00001227first command may not be required if you are already using the module):</p>
1228
Misha Brukman20b8a6562005-02-03 22:25:23 +00001229<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001230<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001231$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckyb8c923b2009-11-04 06:15:28 +00001232$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001233$ chmod u+x hello.bc (if needed)
1234$ ./hello.bc
Chris Lattner998c0672004-03-25 20:38:40 +00001235</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001236</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001237
1238<p>
Chris Lattnerb5c11742010-02-17 18:33:13 +00001239This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +00001240can also use this command instead of the 'echo' command above:
Chris Lattner998c0672004-03-25 20:38:40 +00001241</p>
1242
Chris Lattnerb5c11742010-02-17 18:33:13 +00001243<div class="doc_code">
1244<pre>
1245$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1246</pre>
1247</div>
1248
Chris Lattner998c0672004-03-25 20:38:40 +00001249</div>
1250
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001251</div>
1252
Misha Brukman560e9892003-11-07 19:43:14 +00001253<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001254<h2>
1255 <a name="layout">Program Layout</a>
1256</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001257<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001258
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001259<div>
John Criswell72989a52003-06-12 19:34:44 +00001260
Misha Brukman560e9892003-11-07 19:43:14 +00001261<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001262href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001263href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001264The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001265
Misha Brukman560e9892003-11-07 19:43:14 +00001266<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001267<h3>
1268 <a name="examples"><tt>llvm/examples</tt></a>
1269</h3>
1270
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001271<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001272 <p>This directory contains some simple examples of how to use the LLVM IR and
1273 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001274</div>
John Criswell72989a52003-06-12 19:34:44 +00001275
Misha Brukman560e9892003-11-07 19:43:14 +00001276<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001277<h3>
1278 <a name="include"><tt>llvm/include</tt></a>
1279</h3>
1280
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001281<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001282
1283<p>This directory contains public header files exported from the LLVM
1284library. The three main subdirectories of this directory are:</p>
1285
Reid Spencer075de232004-09-05 20:50:22 +00001286<dl>
1287 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1288 <dd>This directory contains all of the LLVM specific header files. This
1289 directory also has subdirectories for different portions of LLVM:
1290 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1291 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001292
Reid Spencer075de232004-09-05 20:50:22 +00001293 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1294 <dd>This directory contains generic support libraries that are provided with
1295 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1296 and a Command Line option processing library store their header files here.
1297 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001298
Reid Spencer075de232004-09-05 20:50:22 +00001299 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1300 <dd>This directory contains header files configured by the <tt>configure</tt>
1301 script. They wrap "standard" UNIX and C header files. Source code can
1302 include these header files which automatically take care of the conditional
1303 #includes that the <tt>configure</tt> script generates.</dd>
1304</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001305</div>
1306
1307<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001308<h3>
1309 <a name="lib"><tt>llvm/lib</tt></a>
1310</h3>
1311
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001312<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001313
1314<p>This directory contains most of the source files of the LLVM system. In LLVM,
1315almost all code exists in libraries, making it very easy to share code among the
1316different <a href="#tools">tools</a>.</p>
1317
Misha Brukmand3de5c62004-01-20 00:20:17 +00001318<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001319 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1320 <dd> This directory holds the core LLVM source files that implement core
1321 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001322
Reid Spencer075de232004-09-05 20:50:22 +00001323 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1324 <dd>This directory holds the source code for the LLVM assembly language parser
1325 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001326
Gabor Greifa54634a2007-07-06 22:07:22 +00001327 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1328 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001329
Reid Spencer075de232004-09-05 20:50:22 +00001330 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001331 different program analyses, such as Dominator Information, Call Graphs,
1332 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001333 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001334
Reid Spencer075de232004-09-05 20:50:22 +00001335 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1336 <dd> This directory contains the source code for the LLVM to LLVM program
1337 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1338 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1339 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001340
Reid Spencer075de232004-09-05 20:50:22 +00001341 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1342 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001343 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1344 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +00001345 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001346
Reid Spencer075de232004-09-05 20:50:22 +00001347 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1348 <dd> This directory contains the major parts of the code generator: Instruction
1349 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001350
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +00001351 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1352 <dd>(FIXME: T.B.D.)</dd>
1353
1354 <!--FIXME: obsoleted -->
Reid Spencer075de232004-09-05 20:50:22 +00001355 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1356 <dd> This directory contains the source level debugger library that makes
1357 it possible to instrument LLVM programs so that a debugger could identify
1358 source code locations at which the program is executing.</dd>
1359
1360 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001361 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer075de232004-09-05 20:50:22 +00001362 at runtime in both interpreted and JIT compiled fashions.</dd>
1363
1364 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1365 <dd> This directory contains the source code that corresponds to the header
1366 files located in <tt>llvm/include/Support/</tt>.</dd>
1367
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +00001368 <!--FIXME: obsoleted -->
Reid Spencer075de232004-09-05 20:50:22 +00001369 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1370 <dd>This directory contains the operating system abstraction layer that
1371 shields LLVM from platform-specific coding.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001372</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001373
Misha Brukman560e9892003-11-07 19:43:14 +00001374</div>
John Criswell72989a52003-06-12 19:34:44 +00001375
Misha Brukman560e9892003-11-07 19:43:14 +00001376<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001377<h3>
1378 <a name="projects"><tt>llvm/projects</tt></a>
1379</h3>
1380
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001381<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001382 <p>This directory contains projects that are not strictly part of LLVM but are
1383 shipped with LLVM. This is also the directory where you should create your own
1384 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner7b7b6782008-08-11 06:13:31 +00001385 to set up your own project.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001386</div>
1387
1388<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001389<h3>
1390 <a name="runtime"><tt>llvm/runtime</tt></a>
1391</h3>
1392
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001393<div>
John Criswell72989a52003-06-12 19:34:44 +00001394
Gabor Greifa54634a2007-07-06 22:07:22 +00001395<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman560e9892003-11-07 19:43:14 +00001396used when linking programs with the GCC front end. Most of these libraries are
1397skeleton versions of real libraries; for example, libc is a stripped down
1398version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001399
Misha Brukman560e9892003-11-07 19:43:14 +00001400<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1401end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001402
Misha Brukman560e9892003-11-07 19:43:14 +00001403</div>
John Criswell72989a52003-06-12 19:34:44 +00001404
Misha Brukman560e9892003-11-07 19:43:14 +00001405<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001406<h3>
1407 <a name="test"><tt>llvm/test</tt></a>
1408</h3>
1409
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001410<div>
Reid Spencer075de232004-09-05 20:50:22 +00001411 <p>This directory contains feature and regression tests and other basic sanity
1412 checks on the LLVM infrastructure. These are intended to run quickly and cover
1413 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001414</div>
John Criswell72989a52003-06-12 19:34:44 +00001415
Misha Brukman560e9892003-11-07 19:43:14 +00001416<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001417<h3>
1418 <a name="test-suite"><tt>test-suite</tt></a>
1419</h3>
1420
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001421<div>
John Criswell58594852007-06-29 19:12:31 +00001422 <p>This is not a directory in the normal llvm module; it is a separate
1423 Subversion
1424 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1425 This
John Criswell6ab273c2004-12-08 17:53:54 +00001426 module contains a comprehensive correctness, performance, and benchmarking
1427 test
John Criswell58594852007-06-29 19:12:31 +00001428 suite for LLVM. It is a separate Subversion module because not every LLVM
1429 user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001430 interested in downloading or building such a comprehensive test suite. For
1431 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001432 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001433</div>
John Criswell72989a52003-06-12 19:34:44 +00001434
Reid Spencer075de232004-09-05 20:50:22 +00001435<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001436<h3>
1437 <a name="tools"><tt>llvm/tools</tt></a>
1438</h3>
1439
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001440<div>
John Criswell38cc2b52003-10-10 14:26:14 +00001441
Misha Brukman560e9892003-11-07 19:43:14 +00001442<p>The <b>tools</b> directory contains the executables built out of the
1443libraries above, which form the main part of the user interface. You can
Duncan Sands142b9ed2010-02-18 14:08:13 +00001444always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001445following is a brief introduction to the most important tools. More detailed
1446information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001447
Misha Brukmand3de5c62004-01-20 00:20:17 +00001448<dl>
John Criswell72989a52003-06-12 19:34:44 +00001449
Reid Spencer075de232004-09-05 20:50:22 +00001450 <dt><tt><b>bugpoint</b></tt></dt>
1451 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001452 optimization passes or code generation backends by narrowing down the
1453 given test case to the minimum number of passes and/or instructions that
1454 still cause a problem, whether it is a crash or miscompilation. See <a
1455 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001456 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001457
Reid Spencer075de232004-09-05 20:50:22 +00001458 <dt><tt><b>llvmc</b></tt></dt>
1459 <dd>The LLVM Compiler Driver. This program can
1460 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1461 pre-processing, translation, optimization, assembly, and linking of programs
1462 all from one command line. <tt>llvmc</tt> also takes care of processing the
Gabor Greifa54634a2007-07-06 22:07:22 +00001463 dependent libraries found in bitcode. This reduces the need to get the
Reid Spencer92815e52004-12-08 18:00:30 +00001464 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswelle1a81202005-05-18 19:43:33 +00001465 note that this tool, while functional, is still experimental and not feature
1466 complete.</dd>
Reid Spencer075de232004-09-05 20:50:22 +00001467
1468 <dt><tt><b>llvm-ar</b></tt></dt>
1469 <dd>The archiver produces an archive containing
Gabor Greifa54634a2007-07-06 22:07:22 +00001470 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001471 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001472
Reid Spencer075de232004-09-05 20:50:22 +00001473 <dt><tt><b>llvm-as</b></tt></dt>
1474 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001475 bitcode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001476
Reid Spencer075de232004-09-05 20:50:22 +00001477 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001478 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer075de232004-09-05 20:50:22 +00001479 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001480
Reid Spencer92815e52004-12-08 18:00:30 +00001481 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001482 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Andrew Trick68aa18e42010-09-23 20:26:44 +00001483 This is the linker invoked by <tt>llvmc</tt>. It performs standard link time
Reid Spencera7974cc2007-02-09 15:59:08 +00001484 optimizations and allows optimization modules to be loaded and run so that
1485 language specific optimizations can be applied at link time.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +00001486
Reid Spencer075de232004-09-05 20:50:22 +00001487 <dt><tt><b>llvm-link</b></tt></dt>
1488 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1489 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001490
Reid Spencer075de232004-09-05 20:50:22 +00001491 <dt><tt><b>lli</b></tt></dt>
1492 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky97467822007-12-03 01:58:01 +00001493 can directly execute LLVM bitcode (although very slowly...). For architectures
1494 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1495 will function as a Just-In-Time compiler (if the functionality was compiled
1496 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001497
Reid Spencer075de232004-09-05 20:50:22 +00001498 <dt><tt><b>llc</b></tt></dt>
1499 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greifa54634a2007-07-06 22:07:22 +00001500 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001501 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001502
Reid Spencer788b0fd2004-12-22 06:29:07 +00001503 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001504 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1505 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001506 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencera7974cc2007-02-09 15:59:08 +00001507 usual machine code output. It works just like any other GCC compiler,
1508 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1509 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell58594852007-06-29 19:12:31 +00001510 separate Subversion module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001511
Reid Spencer075de232004-09-05 20:50:22 +00001512 <dt><tt><b>opt</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001513 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer80f843d2006-08-28 00:34:19 +00001514 transformations (which are specified on the command line), and then outputs
Duncan Sands142b9ed2010-02-18 14:08:13 +00001515 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukman21a63702008-12-11 18:23:24 +00001516 get a list of the program transformations available in LLVM.<br>
Reid Spencer80f843d2006-08-28 00:34:19 +00001517 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greifa54634a2007-07-06 22:07:22 +00001518 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer80f843d2006-08-28 00:34:19 +00001519 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001520</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001521</div>
John Criswell72989a52003-06-12 19:34:44 +00001522
Misha Brukman560e9892003-11-07 19:43:14 +00001523<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001524<h3>
1525 <a name="utils"><tt>llvm/utils</tt></a>
1526</h3>
1527
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001528<div>
John Criswell72989a52003-06-12 19:34:44 +00001529
Misha Brukman560e9892003-11-07 19:43:14 +00001530<p>This directory contains utilities for working with LLVM source code, and some
1531of the utilities are actually required as part of the build process because they
1532are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001533
Misha Brukmand3de5c62004-01-20 00:20:17 +00001534<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001535 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001536 that finds differences between code that LLC generates and code that LLI
1537 generates. This is a useful tool if you are debugging one of them,
1538 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001539 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001540
Misha Brukmand3de5c62004-01-20 00:20:17 +00001541 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001542 syntax-highlighting files which will work with Emacs and XEmacs editors,
1543 providing syntax highlighting support for LLVM assembly files and TableGen
1544 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001545 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001546
Misha Brukmand3de5c62004-01-20 00:20:17 +00001547 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001548 and outputs all non-generated source files, which is useful if one wishes
1549 to do a lot of development across directories and does not want to
1550 individually find each file. One way to use it is to run, for example:
1551 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001552 tree.<br><br>
1553
Reid Spencer075de232004-09-05 20:50:22 +00001554 <dt><tt><b>llvmgrep</b></tt></dt>
1555 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1556 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1557 line. This is a very efficient way of searching the source base for a
1558 particular regular expression.</dd>
1559
Misha Brukmand3de5c62004-01-20 00:20:17 +00001560 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001561 files in the current directory and then compiles and links the tool that
1562 is the first argument. For example, assuming you are in the directory
1563 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1564 simply running <tt>makellvm llc</tt> will make a build of the current
1565 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001566 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001567
Tanya Lattner3e852072007-05-22 06:12:51 +00001568 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukmand3de5c62004-01-20 00:20:17 +00001569 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman560e9892003-11-07 19:43:14 +00001570 cron script to generate nightly status reports of the functionality of
1571 tools, and the results can be seen by following the appropriate link on
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001572 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001573
Misha Brukmand3de5c62004-01-20 00:20:17 +00001574 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001575 the tool used to generate register descriptions, instruction set
1576 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001577 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001578
Misha Brukmand3de5c62004-01-20 00:20:17 +00001579 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001580 syntax-highlighting files which will work with the VIM editor, providing
1581 syntax highlighting support for LLVM assembly files and TableGen
1582 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001583 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001584
Misha Brukman560e9892003-11-07 19:43:14 +00001585</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001586
Misha Brukman560e9892003-11-07 19:43:14 +00001587</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001588
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001589</div>
1590
Misha Brukman560e9892003-11-07 19:43:14 +00001591<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001592<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001593 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001594</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001595<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001596
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001597<div>
Chris Lattner424d4dc2007-01-04 07:08:27 +00001598<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
Chris Lattner4c445302009-04-10 15:38:51 +00001599so we only include instructions for llvm-gcc4.
Chris Lattner5b560d92006-08-14 20:45:25 +00001600</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001601
1602<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1603from 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 +00001604create bitcode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1605the '--emit-llvm' flag is needed to produce LLVM bitcode output. For <i>makefiles</i> and
1606<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bitcode
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001607output.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001608
1609<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001610<h3>
1611 <a name="tutorial4">Example with llvm-gcc4</a>
1612</h3>
Chris Lattner5b560d92006-08-14 20:45:25 +00001613
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001614<div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001615
1616<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001617 <li><p>First, create a simple C file, name it 'hello.c':</p>
1618
1619<div class="doc_code">
1620<pre>
1621#include &lt;stdio.h&gt;
1622
1623int main() {
1624 printf("hello world\n");
1625 return 0;
1626}
1627</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001628
1629 <li><p>Next, compile the C file into a native executable:</p>
1630
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001631 <div class="doc_code"><pre>% llvm-gcc hello.c -o hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001632
1633 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1634 -c arguments work as usual (producing a native .s or .o file,
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001635 respectively).</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001636
Gabor Greifa54634a2007-07-06 22:07:22 +00001637 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001638
1639 <div class="doc_code">
1640 <pre>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001641
1642 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1643 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1644 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Gabor Greifa54634a2007-07-06 22:07:22 +00001645 the bitcode file.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001646
1647 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1648 </p></li>
1649
1650 <li><p>Run the program in both forms. To run the program, use:</p>
1651
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001652 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001653
1654 <p>and</p>
1655
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001656 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001657
1658 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001659 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001660
1661 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1662 code:</p>
1663
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001664<div class="doc_code">
1665<pre>llvm-dis &lt; hello.bc | less</pre>
1666</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001667
1668 <li><p>Compile the program to native assembly using the LLC code
1669 generator:</p>
1670
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001671 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001672
1673 <li><p>Assemble the native assembly language file into a program:</p>
1674
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001675<div class="doc_code">
1676<pre>
1677<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1678
1679<b>Others:</b> % gcc hello.s -o hello.native
1680</pre>
1681</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001682
1683 <li><p>Execute the native code program:</p>
1684
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001685 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001686
1687 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1688 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001689 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001690
1691</ol>
1692
1693</div>
1694
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001695</div>
John Criswell72989a52003-06-12 19:34:44 +00001696
Misha Brukman560e9892003-11-07 19:43:14 +00001697<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001698<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001699 <a name="problems">Common Problems</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001700</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001701<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001702
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001703<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001704
Misha Brukman560e9892003-11-07 19:43:14 +00001705<p>If you are having problems building or using LLVM, or if you have any other
1706general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1707Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001708
Misha Brukman560e9892003-11-07 19:43:14 +00001709</div>
John Criswell72989a52003-06-12 19:34:44 +00001710
Misha Brukman560e9892003-11-07 19:43:14 +00001711<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001712<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001713 <a name="links">Links</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001714</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001715<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001716
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001717<div>
John Criswell72989a52003-06-12 19:34:44 +00001718
Bill Wendlingcb13d702008-07-22 01:10:25 +00001719<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman560e9892003-11-07 19:43:14 +00001720some simple things... there are many more interesting and complicated things
1721that you can do that aren't documented here (but we'll gladly accept a patch
1722if you want to write something up!). For more information about LLVM, check
1723out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001724
Misha Brukman560e9892003-11-07 19:43:14 +00001725<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001726 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1727 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1728 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001729 that Uses LLVM</a></li>
1730</ul>
1731
1732</div>
1733
1734<!-- *********************************************************************** -->
1735
1736<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001737<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001738 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001739 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001740 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +00001741 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001742
Misha Brukman74d4df82003-11-22 01:30:01 +00001743 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001744 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001745 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001746 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001747</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001748</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001749</html>