blob: 72bc9b3e2f7a1954fc8bd79758ecb18f0b54c25c [file] [log] [blame]
Misha Brukman560e9892003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shib65a78e2002-07-17 23:05:56 +00003<html>
Misha Brukman560e9892003-11-07 19:43:14 +00004<head>
Reid Spencer38fcf302004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman560e9892003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +000010
Misha Brukman560e9892003-11-07 19:43:14 +000011<div class="doc_title">
12 Getting Started with the LLVM System
13</div>
John Criswell72989a52003-06-12 19:34:44 +000014
Misha Brukman560e9892003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +000019 <ol>
Misha Brukman560e9892003-11-07 19:43:14 +000020 <li><a href="#hardware">Hardware</a>
21 <li><a href="#software">Software</a>
Chris Lattnere0050f02004-07-18 22:32:22 +000022 <li><a href="#brokengcc">Broken versions of GCC</a>
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>
Misha Brukman560e9892003-11-07 19:43:14 +000027 <li><a href="#terminology">Terminology and Notation</a>
28 <li><a href="#environment">Setting Up Your Environment</a>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a>
30 <li><a href="#checkout">Checkout LLVM from CVS</a>
31 <li><a href="#installcf">Install the GCC Front End</a>
32 <li><a href="#config">Local LLVM Configuration</a>
33 <li><a href="#compile">Compiling the LLVM Suite Source Code</a>
Reid Spencer734b74f2006-07-27 06:41:31 +000034 <li><a href="#cross-compile">Cross-Compiling LLVM</a>
Misha Brukman560e9892003-11-07 19:43:14 +000035 <li><a href="#objfiles">The Location of LLVM Object Files</a>
Chris Lattner998c0672004-03-25 20:38:40 +000036 <li><a href="#optionalconfig">Optional Configuration Items</a>
Misha Brukman560e9892003-11-07 19:43:14 +000037 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +000038
Misha Brukman560e9892003-11-07 19:43:14 +000039 <li><a href="#layout">Program layout</a>
40 <ol>
41 <li><a href="#cvsdir"><tt>CVS</tt> directories</a>
Reid Spencer5be4f042004-12-08 16:18:26 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +000043 <li><a href="#include"><tt>llvm/include</tt></a>
44 <li><a href="#lib"><tt>llvm/lib</tt></a>
Reid Spencer5be4f042004-12-08 16:18:26 +000045 <li><a href="#projects"><tt>llvm/projects</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +000046 <li><a href="#runtime"><tt>llvm/runtime</tt></a>
47 <li><a href="#test"><tt>llvm/test</tt></a>
Reid Spencer075de232004-09-05 20:50:22 +000048 <li><a href="#llvmtest"><tt>llvm-test</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a>
50 <li><a href="#utils"><tt>llvm/utils</tt></a>
Reid Spencer5be4f042004-12-08 16:18:26 +000051 <li><a href="#win32"><tt>llvm/win32</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +000052 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +000053
Misha Brukman560e9892003-11-07 19:43:14 +000054 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000055 <ol>
56 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000057 </ol>
Misha Brukman560e9892003-11-07 19:43:14 +000058 <li><a href="#problems">Common Problems</a>
59 <li><a href="#links">Links</a>
60</ul>
61
Chris Lattner020e1fc2004-05-23 21:07:27 +000062<div class="doc_author">
63 <p>Written by:
64 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
65 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
66 <a href="http://misha.brukman.net">Misha Brukman</a>,
67 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
68 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
69 </p>
70</div>
Misha Brukman560e9892003-11-07 19:43:14 +000071
72
73<!-- *********************************************************************** -->
74<div class="doc_section">
75 <a name="overview"><b>Overview</b></a>
76</div>
77<!-- *********************************************************************** -->
78
79<div class="doc_text">
80
81<p>Welcome to LLVM! In order to get started, you first need to know some
82basic information.</p>
83
84<p>First, LLVM comes in two pieces. The first piece is the LLVM suite. This
85contains all of the tools, libraries, and header files needed to use the low
86level virtual machine. It contains an assembler, disassembler, bytecode
Reid Spencer80f843d2006-08-28 00:34:19 +000087analyzer and bytecode optimizer. It also contains a test suite that can be
Misha Brukman560e9892003-11-07 19:43:14 +000088used to test the LLVM tools and the GCC front end.</p>
89
90<p>The second piece is the GCC front end. This component provides a version of
91GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front
Chris Lattner40872ad2007-03-06 06:27:34 +000092end uses the GCC parser to convert code to LLVM. Once
Misha Brukman560e9892003-11-07 19:43:14 +000093compiled into LLVM bytecode, a program can be manipulated with the LLVM tools
94from the LLVM suite.</p>
95
John Criswell6ab273c2004-12-08 17:53:54 +000096<p>
97There is a third, optional piece called llvm-test. It is a suite of programs
98with a testing harness that can be used to further test LLVM's functionality
99and performance.
100</p>
101
Misha Brukman560e9892003-11-07 19:43:14 +0000102</div>
103
104<!-- *********************************************************************** -->
105<div class="doc_section">
106 <a name="quickstart"><b>Getting Started Quickly (A Summary)</b></a>
107</div>
108<!-- *********************************************************************** -->
109
110<div class="doc_text">
111
112<p>Here's the short story for getting up and running quickly with LLVM:</p>
113
114<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000115 <li>Read the documentation.</li>
116 <li>Read the documentation.</li>
117 <li>Remember that you were warned twice about reading the documentation.</li>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000118 <li>Install the GCC front end if you intend to compile C or C++:
Misha Brukman560e9892003-11-07 19:43:14 +0000119 <ol>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000120 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000121 <li><tt>gunzip --stdout llvm-gcc.<i>platform</i>.tar.gz | tar -xvf -</tt>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000122 </li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000123 <li><tt>cd llvm-gcc3.4/<i>platform</i> (llvm-gcc3.4 only)<br>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000124 ./fixheaders</tt></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000125 <li>Add llvm-gcc's "bin" directory to your PATH variable.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000126 </ol></li>
127
Misha Brukman20b8a6562005-02-03 22:25:23 +0000128 <li>Get the LLVM Source Code
Misha Brukman560e9892003-11-07 19:43:14 +0000129 <ul>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000130 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
Misha Brukman560e9892003-11-07 19:43:14 +0000131 <ol>
132 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell64f13ab2004-03-12 20:31:37 +0000133 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000134 </ol></li>
135
Misha Brukman560e9892003-11-07 19:43:14 +0000136 </ul></li>
137
Misha Brukman20b8a6562005-02-03 22:25:23 +0000138 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswelldfe6a862004-12-10 15:51:16 +0000139 <ul>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000140 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
John Criswelldfe6a862004-12-10 15:51:16 +0000141 <ol>
142 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
143 <li><tt>cd llvm/projects</tt>
144 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
John Criswelldfe6a862004-12-10 15:51:16 +0000145 </ol></li>
146
John Criswelldfe6a862004-12-10 15:51:16 +0000147 </ul></li>
148
149
Misha Brukman560e9892003-11-07 19:43:14 +0000150 <li>Configure the LLVM Build Environment
151 <ol>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000152 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
153 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
154 Some common options:
155
Misha Brukman560e9892003-11-07 19:43:14 +0000156 <ul>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000157 <li><tt>--prefix=<i>directory</i></tt>
158 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000159 want the LLVM tools and libraries to be installed (default
160 <tt>/usr/local</tt>).</p></li>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000161 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
162 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswellcfdeb5c2005-05-09 16:39:27 +0000163 C/C++ front end installation to use with this LLVM configuration. If
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000164 not specified, the PATH will be searched.</p></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000165 <li><tt>--enable-spec2000=<i>directory</i></tt>
166 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
167 benchmarks should be available in
168 <tt><i>directory</i></tt>.</p></li>
169 </ul>
170 </ol></li>
171
172 <li>Build the LLVM Suite:
173 <ol>
Chris Lattnere0050f02004-07-18 22:32:22 +0000174 <li><tt>gmake -k |&amp; tee gnumake.out
175 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner13ce9182007-01-04 07:06:05 +0000176 <li>If you get an "internal compiler error (ICE)" or test failures, see
177 <a href="#brokengcc">below</a>.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000178 </ol>
179
180</ol>
181
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000182<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000183detailed information on configuring and compiling LLVM. See <a
184href="#environment">Setting Up Your Environment</a> for tips that simplify
185working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
186Layout</a> to learn about the layout of the source code tree.</p>
187
188</div>
189
190<!-- *********************************************************************** -->
191<div class="doc_section">
192 <a name="requirements"><b>Requirements</b></a>
193</div>
194<!-- *********************************************************************** -->
195
196<div class="doc_text">
197
198<p>Before you begin to use the LLVM system, review the requirements given below.
199This may save you some trouble by knowing ahead of time what hardware and
200software you will need.</p>
201
202</div>
203
204<!-- ======================================================================= -->
205<div class="doc_subsection">
206 <a name="hardware"><b>Hardware</b></a>
207</div>
208
209<div class="doc_text">
210
211<p>LLVM is known to work on the following platforms:</p>
212
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000213<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000214<tr>
215 <th>OS</th>
216 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000217 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000218</tr>
219<tr>
220 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000221 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000222 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000223</tr>
224<tr>
225 <td>Solaris</td>
226 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000227 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000228</tr>
229<tr>
230 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000231 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000232 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000233</tr>
234<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000235 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000236 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000237 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000238</tr>
239<tr>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000240 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
241 <td>x86</td>
242 <td>GCC</td>
243
244</tr>
245<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000246 <td>Cygwin/Win32</td>
Chris Lattner9a964262006-07-21 00:06:27 +0000247 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a></sup></td>
Reid Spencera8acd822004-12-23 19:39:54 +0000248 <td>GCC 3.4.X, binutils 2.15</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000249</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000250<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000251 <td>MinGW/Win32</td>
Chris Lattner9a964262006-07-21 00:06:27 +0000252 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,<a href="#pf_8">8</a></sup></td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000253 <td>GCC 3.4.X, binutils 2.15</td>
254</tr>
255<tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000256 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000257 <td>amd64<sup><a href="#pf_3">3</a></sup></td>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000258 <td>GCC</td>
259</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000260</table>
261
262<p>LLVM has partial support for the following platforms:</p>
263
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000264<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000265<tr>
266 <th>OS</th>
267 <th>Arch</th>
268 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000269</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000270<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000271 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000272 <td>x86<sup><a href="#pf_1">1</a></sup></td>
273 <td>Visual Studio .NET<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000274<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000275 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000276 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000277 <td>GCC</td>
278</tr>
279<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000280 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000281 <td>PowerPC</td>
282 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000283</tr>
John Criswell05990f32005-05-09 16:49:59 +0000284
285<tr>
286 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
287 <td>Alpha</td>
288 <td>GCC</td>
289</tr>
290<tr>
291 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
292 <td>Itanium (IA-64)</td>
293 <td>GCC</td>
294</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000295<tr>
296 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
297 <td>Itanium (IA-64)</td>
298 <td>HP aCC</td>
299</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000300</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000301
Misha Brukman77723092005-02-09 21:01:26 +0000302<p><b>Notes:</b></p>
303
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000304<div class="doc_notes">
305<ol>
306<li><a name="pf_1">Code generation supported for Pentium processors and
307up</a></li>
308<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
309<li><a name="pf_3">No native code generation</a></li>
310<li><a name="pf_4">Build is not complete: one or more tools don't link</a></li>
311<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner5b560d92006-08-14 20:45:25 +0000312<li><a name="pf_6">The port is done using the MSYS shell.</a>
Misha Brukman77723092005-02-09 21:01:26 +0000313<a href="http://www.mingw.org/MinGWiki/">Download</a> and install
Chris Lattner9a964262006-07-21 00:06:27 +0000314bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source,
Chris Lattner5b560d92006-08-14 20:45:25 +0000315if necessary. Bison &amp; flex can be also grabbed from GNUWin32 sf.net
316project.</li>
John Criswell05990f32005-05-09 16:49:59 +0000317<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Chris Lattner5b560d92006-08-14 20:45:25 +0000318<li><a name="pf_8">Binutils</a> up to post-2.17 has bug in bfd/cofflink.c
Chris Lattner9a964262006-07-21 00:06:27 +0000319 preventing LLVM from building correctly. Several workarounds have been
320 introduced into LLVM build system, but the bug can occur anytime in the
Chris Lattner5b560d92006-08-14 20:45:25 +0000321 future. We highly recommend that you rebuild your current binutils with the
Chris Lattner9a964262006-07-21 00:06:27 +0000322 patch from <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=2659">
Chris Lattner5b560d92006-08-14 20:45:25 +0000323 Binutils bugzilla</a>, if it wasn't already applied.</li>
Misha Brukman77723092005-02-09 21:01:26 +0000324</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000325</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000326
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000327<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 +0000328mode, depending on the system (it is so large because of all the debugging
329information and the fact that the libraries are statically linked into multiple
330tools). If you do not need many of the tools and you are space-conscious,
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000331you can disable them individually in <tt>llvm/tools/Makefile</tt>. The Release
332build requires considerably less space.</p>
333
Misha Brukman560e9892003-11-07 19:43:14 +0000334<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
335guaranteed to do so. If compilation is successful, the LLVM utilities should be
336able to assemble, disassemble, analyze, and optimize LLVM bytecode. Code
337generation should work as well, although the generated native code may not work
338on your platform.</p>
339
340<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 +0000341to work on another platform, you can download a copy of the source and <a
342href="CFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000343
344</div>
345
346<!-- ======================================================================= -->
Reid Spencer38fcf302004-11-15 21:15:12 +0000347<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000348<div class="doc_text">
Reid Spencer38fcf302004-11-15 21:15:12 +0000349 <p>Compiling LLVM requires that you have several software packages
350 installed. The table below lists those required packages. The Package column
351 is the usual name for the software package that LLVM depends on. The Version
352 column provides "known to work" versions of the package. The Notes column
353 describes how LLVM uses the package and provides other details.</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000354 <table summary="Packages required to compile LLVM">
Reid Spencer38fcf302004-11-15 21:15:12 +0000355 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000356
Reid Spencer38fcf302004-11-15 21:15:12 +0000357 <tr>
358 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
359 <td>3.79, 3.79.1</td>
360 <td>Makefile/build processor</td>
361 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000362
Reid Spencer38fcf302004-11-15 21:15:12 +0000363 <tr>
364 <td><a href="http://gcc.gnu.org">GCC</a></td>
365 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000366 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000367 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000368
Reid Spencer38fcf302004-11-15 21:15:12 +0000369 <tr>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000370 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
371 <td>4.5</td>
372 <td>For building the CFE</td>
373 </tr>
374
375 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000376 <td><a href="http://www.gnu.org/software/flex">Flex</a></td>
377 <td>2.5.4</td>
378 <td>LEX compiler</td>
379 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000380
Reid Spencer38fcf302004-11-15 21:15:12 +0000381 <tr>
382 <td><a href="http://www.gnu.org/software/bison/bison.html">Bison</a></td>
Jeff Cohen71201072006-01-04 06:51:22 +0000383 <td>1.28, 1.35, 1.75, 1.875d, 2.0, or 2.1<br>(not 1.85 or 1.875)</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000384 <td>YACC compiler</td>
385 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000386
Reid Spencer38fcf302004-11-15 21:15:12 +0000387 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000388 <td><a href="https://www.cvshome.org/downloads.html">CVS</a></td>
389 <td>&ge;1.11</td>
390 <td>CVS access to LLVM<sup><a href="#sf2">2</a></sup></td>
391 </tr>
392
393 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000394 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
395 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000396 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000397 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000398
Reid Spencer38fcf302004-11-15 21:15:12 +0000399 <tr>
400 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
401 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000402 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000403 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000404
Reid Spencer38fcf302004-11-15 21:15:12 +0000405 <tr>
406 <td><a href="http://expect.nist.gov/">expect</a></td>
407 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000408 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000409 </tr>
410
411 <tr>
412 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000413 <td>&ge;5.6.0</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000414 <td>Nightly tester, utilities</td>
415 </tr>
416
417 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000418 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
419 <td>1.4</td>
420 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000421 </tr>
422
423 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000424 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
425 <td>2.59</td>
426 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
427 </tr>
428
429 <tr>
430 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
431 <td>1.9.2</td>
432 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
433 </tr>
434
435 <tr>
436 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
437 <td>1.5.10</td>
438 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000439 </tr>
440
441 </table>
442
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000443 <p><b>Notes:</b></p>
444 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000445 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000446 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000447 need to build the other languages for LLVM's purposes.</a> See
448 <a href="#brokengcc">below</a> for specific version info.</li>
449 <li><a name="sf2">You only need CVS if you intend to build from the
450 latest LLVM sources. If you're working from a release distribution, you
451 don't need CVS.</a></li>
452 <li><a name="sf3">Only needed if you want to run the automated test
453 suite in the <tt>llvm/test</tt> directory.</a></li>
454 <li><a name="sf4">If you want to make changes to the configure scripts,
Reid Spencer38fcf302004-11-15 21:15:12 +0000455 you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4
Reid Spencer098fce42004-12-09 17:55:37 +0000456 or higher). You will also need automake (1.9.2). We only use aclocal
457 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000458 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000459 </div>
460
Reid Spencer38fcf302004-11-15 21:15:12 +0000461 <p>Additionally, your compilation host is expected to have the usual
462 plethora of Unix utilities. Specifically:</p>
463 <ul>
464 <li><b>ar</b> - archive library builder</li>
465 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
466 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
467 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000468 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000469 <li><b>cp</b> - copy files</li>
470 <li><b>date</b> - print the current date/time </li>
471 <li><b>echo</b> - print to standard output</li>
472 <li><b>egrep</b> - extended regular expression search utility</li>
473 <li><b>etags</b> - C/C++ tag file creator for vim/emacs</li>
474 <li><b>find</b> - find files/dirs in a file system</li>
475 <li><b>grep</b> - regular expression search utility</li>
476 <li><b>gzip*</b> - gzip command for distribution generation</li>
477 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
478 <li><b>install</b> - install directories/files </li>
479 <li><b>mkdir</b> - create a directory</li>
480 <li><b>mv</b> - move (rename) files</li>
481 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000482 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000483 <li><b>sed</b> - stream editor for transforming output</li>
484 <li><b>sh</b> - Bourne shell for make build scripts</li>
485 <li><b>tar</b> - tape archive for distribution generation</li>
486 <li><b>test</b> - test things in file system</li>
487 <li><b>unzip*</b> - unzip command for distribution checking</li>
488 <li><b>zip*</b> - zip command for distribution generation</li>
489 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000490</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000491
Chris Lattnere0050f02004-07-18 22:32:22 +0000492<!-- ======================================================================= -->
493<div class="doc_subsection">
494 <a name="brokengcc">Broken versions of GCC</a>
495</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000496
Chris Lattnere0050f02004-07-18 22:32:22 +0000497<div class="doc_text">
498
499<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
500bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner29052c82006-06-16 17:20:33 +0000501to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000502successfully with them (however, see important notes below). Other versions
503of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000504here are known to not work. If you are using one of these versions, please try
505to upgrade your GCC to something more recent. If you run into a problem with a
506version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
507us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
508of GCC you are using.
509</p>
510
511<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
512problems in the STL that effectively prevent it from compiling LLVM.
513</p>
514
John Criswellfd769452004-11-23 22:06:24 +0000515<p><b>GCC 3.2.2</b>: This version of GCC fails to compile LLVM.</p>
516
Chris Lattnere0050f02004-07-18 22:32:22 +0000517<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
518href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
519the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000520
Chris Lattner58247622005-02-13 22:20:49 +0000521<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
522 Cygwin does not work. Please <a href="CFEBuildInstrs.html#cygwin">upgrade
523 to a newer version</a> if possible.</p>
524<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
525 possibly others) does not compile LLVM correctly (it appears that exception
526 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
527 to a newer version of GCC.</p>
Chris Lattner455563b2007-05-10 05:37:14 +0000528<p><b>GCC 3.4.0</b> on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000529 code generator, causing an infinite loop in the llvm-gcc build when built
530 with optimizations enabled (i.e. a release build).</p>
531<p><b>GCC 3.4.2</b> on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
532 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
533 correctly compiles LLVM at -O2. A work around is to build release LLVM
534 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Chris Lattner489ad332007-04-01 20:14:46 +0000535<p><b>GCC 3.4.x</b> on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
536 miscompiles portions of LLVM</a>.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000537<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
538 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000539<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
540 default with ENABLE_OPTIMIZED=1. To work around this, build with
541 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000542<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
543 compiling some files. At the time of this writing, GCC mainline (4.2)
544 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000545<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
546 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
547 code. LLVM will appear to mostly work but will be buggy, e.g. failing
548 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000549<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
550platforms compiling md5.c gets a mangled constant.</p>
Reid Spencer6291ddc2006-11-04 00:33:42 +0000551<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
552long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
553defined in a discarded section. You can safely ignore these messages as they are
554erroneous and the linkage is correct. These messages disappear using ld
5552.17.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000556</div>
557
Chris Lattnere0050f02004-07-18 22:32:22 +0000558
559
Misha Brukman560e9892003-11-07 19:43:14 +0000560<!-- *********************************************************************** -->
561<div class="doc_section">
562 <a name="starting"><b>Getting Started with LLVM</b></a>
563</div>
564<!-- *********************************************************************** -->
565
Chris Lattnere0050f02004-07-18 22:32:22 +0000566<div class="doc_text">
567
568<p>The remainder of this guide is meant to get you up and running with
569LLVM and to give you some basic information about the LLVM environment.</p>
570
571<p>The later sections of this guide describe the <a
572href="#layout">general layout</a> of the the LLVM source tree, a <a
573href="#tutorial">simple example</a> using the LLVM tool chain, and <a
574href="#links">links</a> to find more information about LLVM or to get
575help via e-mail.</p>
576</div>
577
Misha Brukman560e9892003-11-07 19:43:14 +0000578<!-- ======================================================================= -->
579<div class="doc_subsection">
580 <a name="terminology">Terminology and Notation</a>
581</div>
582
583<div class="doc_text">
584
585<p>Throughout this manual, the following names are used to denote paths
586specific to the local system and working environment. <i>These are not
587environment variables you need to set but just strings used in the rest
588of this document below</i>. In any of the examples below, simply replace
589each of these names with the appropriate pathname on your local system.
590All these paths are absolute:</p>
591
Misha Brukmand3de5c62004-01-20 00:20:17 +0000592<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000593 <dt>SRC_ROOT
594 <dd>
595 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000596 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000597
Misha Brukman560e9892003-11-07 19:43:14 +0000598 <dt>OBJ_ROOT
599 <dd>
600 This is the top level directory of the LLVM object tree (i.e. the
601 tree where object files and compiled programs will be placed. It
602 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000603 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000604
605 <dt>LLVMGCCDIR
606 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000607 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000608 <p>
609 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000610 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000611</dl>
612
613</div>
614
615<!-- ======================================================================= -->
616<div class="doc_subsection">
617 <a name="environment">Setting Up Your Environment</a>
618</div>
619
620<div class="doc_text">
621
622<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000623In order to compile and use LLVM, you may need to set some environment
624variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000625
Misha Brukmand3de5c62004-01-20 00:20:17 +0000626<dl>
Reid Spencer360d6b72004-12-15 00:14:01 +0000627 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000628 <dd>[Optional] This environment variable helps LLVM linking tools find the
John Criswelle1a81202005-05-18 19:43:33 +0000629 locations of your bytecode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000630 convenience since you can specify the paths using the -L options of the
John Criswelle1a81202005-05-18 19:43:33 +0000631 tools and the C/C++ front-end will automatically use the bytecode files
632 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000633 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000634</dl>
635
636</div>
637
638<!-- ======================================================================= -->
639<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000640 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000641</div>
642
643<div class="doc_text">
644
645<p>
646If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000647can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000648suite and the LLVM GCC front end compiled for your platform. There is an
649additional test suite that is optional. Each file is a TAR archive that is
650compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000651</p>
652
Misha Brukmand4528ea2005-02-02 18:01:57 +0000653<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000654<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000655 <dt><tt>llvm-x.y.tar.gz</tt></dt>
656 <dd>Source release for the LLVM libraries and tools.<br/></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000657
Misha Brukmand4528ea2005-02-02 18:01:57 +0000658 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Chris Lattnerac648f52005-02-09 21:15:51 +0000659 <dd>Source release for the LLVM test suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000660
Chris Lattner499abb52006-04-20 05:08:23 +0000661 <dt><tt>llvm-gcc4-x.y.source.tar.gz</tt></dt>
662 <dd>Source release of the llvm-gcc4 front end. See README.LLVM in the root
663 directory for build instructions.<br/></dd>
664
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000665 <dt><tt>llvm-gcc4-x.y-platform.tar.gz</tt></dt>
666 <dd>Binary release of the llvm-gcc4 front end for a specific platform.<br/></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000667
Misha Brukman560e9892003-11-07 19:43:14 +0000668</dl>
669
Jim Laskeyb4c03472006-07-31 21:37:55 +0000670<p>It is also possible to download the sources of the llvm-gcc4 front end from a
671read-only subversion mirror at
672svn://anonsvn.opensource.apple.com/svn/llvm/trunk. </p>
Jim Laskey34ea26a2006-06-16 23:20:21 +0000673
Misha Brukman560e9892003-11-07 19:43:14 +0000674</div>
675
676<!-- ======================================================================= -->
677<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000678 <a name="checkout">Checkout LLVM from CVS</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000679</div>
680
681<div class="doc_text">
682
683<p>If you have access to our CVS repository, you can get a fresh copy of
684the entire source code. All you need to do is check it out from CVS as
685follows:</p>
686
687<ul>
688<li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
Chris Lattnerc4774272006-08-03 22:14:43 +0000689 <li><tt>cvs -d :pserver:anon@llvm.org:/var/cvs/llvm login</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000690 <li>Hit the return key when prompted for the password.
Chris Lattnerc4774272006-08-03 22:14:43 +0000691 <li><tt>cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co
Misha Brukman560e9892003-11-07 19:43:14 +0000692 llvm</tt>
693</ul>
694
695<p>This will create an '<tt>llvm</tt>' directory in the current
696directory and fully populate it with the LLVM source code, Makefiles,
697test directories, and local copies of documentation files.</p>
698
Misha Brukmand3de5c62004-01-20 00:20:17 +0000699<p>If you want to get a specific release (as opposed to the most recent
700revision), you can specify a label. The following releases have the following
Misha Brukmand4528ea2005-02-02 18:01:57 +0000701labels:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000702
John Criswell86a3a482003-12-18 16:43:17 +0000703<ul>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000704<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000705<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000706<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000707<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000708<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000709<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000710<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000711<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000712<li>Release 1.2: <b>RELEASE_12</b></li>
713<li>Release 1.1: <b>RELEASE_11</b></li>
714<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000715</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000716
Reid Spencerdfcf7902004-12-08 16:51:31 +0000717<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
718you get it from the CVS repository:</p>
719<pre>
720 cd llvm/projects
Chris Lattnerc4774272006-08-03 22:14:43 +0000721 cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co llvm-test
Reid Spencerdfcf7902004-12-08 16:51:31 +0000722</pre>
723<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000724configured by the LLVM configure script as well as automatically updated when
Reid Spencerdfcf7902004-12-08 16:51:31 +0000725you run <tt>cvs update</tt>.</p>
726
Chris Lattner40872ad2007-03-06 06:27:34 +0000727<p>If you would like to get the GCC front end source code, you can also get it
728and build it yourself. Please follow <a href="CFEBuildInstrs.html">these
729instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000730
Misha Brukman560e9892003-11-07 19:43:14 +0000731</div>
732
733<!-- ======================================================================= -->
734<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000735 <a name="installcf">Install the GCC Front End</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000736</div>
737
738<div class="doc_text">
739
Chris Lattner24b71352007-02-14 07:33:00 +0000740<p>Before configuring and compiling the LLVM suite, you can optionally extract the
741LLVM GCC front end from the binary distribution. It is used for running the
742llvm-test testsuite and for compiling C/C++ programs. Note that you can optionally
743<a href="CFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
744main LLVM repository.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000745
746<p>To install the GCC front end, do the following:</p>
747
748<ol>
749 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000750 <li><tt>gunzip --stdout llvmgcc-<i>version</i>.<i>platform</i>.tar.gz | tar -xvf
Misha Brukman560e9892003-11-07 19:43:14 +0000751 -</tt></li>
752</ol>
753
Chris Lattner24b71352007-02-14 07:33:00 +0000754<p>Once the binary is uncompressed, you should add a symlink for llvm-gcc and
755llvm-g++ to some directory in your path. When you configure LLVM, it will
756automatically detect llvm-gcc's presence (if it is in your path) enabling its
757use in llvm-test. Note that you can always build or install llvm-gcc at any
758pointer after building the main LLVM repository: just reconfigure llvm and
759llvm-test will pick it up.
760</p>
761
Misha Brukman560e9892003-11-07 19:43:14 +0000762<p>The binary versions of the GCC front end may not suit all of your needs. For
763example, the binary distribution may include an old version of a system header
764file, not "fix" a header file that needs to be fixed for GCC, or it may be
765linked with libraries not available on your system.</p>
766
767<p>In cases like these, you may want to try <a
768href="CFEBuildInstrs.html">building the GCC front end from source.</a> This is
Chris Lattnercba64662007-02-14 07:34:22 +0000769much easier now than it was in the past.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000770
771</div>
772
773<!-- ======================================================================= -->
774<div class="doc_subsection">
775 <a name="config">Local LLVM Configuration</a>
776</div>
777
778<div class="doc_text">
779
780<p>Once checked out from the CVS repository, the LLVM suite source code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000781configured via the <tt>configure</tt> script. This script sets variables in the
782various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
783<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
784the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000785
786<p>The following environment variables are used by the <tt>configure</tt>
787script to configure the build system:</p>
788
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000789<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +0000790 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000791 <tr>
792 <td>CC</td>
793 <td>Tells <tt>configure</tt> which C compiler to use. By default,
794 <tt>configure</tt> will look for the first GCC C compiler in
795 <tt>PATH</tt>. Use this variable to override
796 <tt>configure</tt>'s default behavior.</td>
797 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000798 <tr>
799 <td>CXX</td>
800 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
801 <tt>configure</tt> will look for the first GCC C++ compiler in
802 <tt>PATH</tt>. Use this variable to override
803 <tt>configure</tt>'s default behavior.</td>
804 </tr>
805</table>
806
807<p>The following options can be used to set or enable LLVM specific options:</p>
808
Misha Brukmand3de5c62004-01-20 00:20:17 +0000809<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000810 <dt><i>--with-llvmgccdir</i></dt>
811 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
812 The value of this option should specify the full pathname of the C/C++ Front
813 End to be used. If this option is not provided, the PATH will be searched for
814 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
815 be inferred from the path found. If the option is not given, and no llvm-gcc
816 can be found in the path then a warning will be produced by
817 <tt>configure</tt> indicating this situation. LLVM may still be built with
818 the <tt>tools-only</tt> target but attempting to build the runtime libraries
819 will fail as these libraries require llvm-gcc and llvm-g++. See
820 <a href="#installcf">Install the GCC Front End</a> for details on installing
821 the C/C++ Front End. See
822 <a href="CFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
823 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000824 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +0000825 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000826 found. Use this if you have multiple tcl installations on your machine and you
827 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
828 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +0000829 option, the LLVM configure script will search for the tcl 8.4 and 8.3
830 releases.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000831 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000832 </dd>
833 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000834 <dd>
835 Enables optimized compilation by default (debugging symbols are removed
836 and GCC optimization flags are enabled). The default is to use an
837 unoptimized build (also known as a debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000838 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000839 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +0000840 <dt><i>--enable-debug-runtime</i></dt>
841 <dd>
842 Enables debug symbols in the runtime libraries. The default is to strip
843 debug symbols from the runtime libraries.
844 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000845 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000846 <dd>
John Criswell86a3a482003-12-18 16:43:17 +0000847 Compile the Just In Time (JIT) compiler functionality. This is not
848 available
Misha Brukman560e9892003-11-07 19:43:14 +0000849 on all platforms. The default is dependent on platform, so it is best
850 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000851 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000852 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000853 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
854 <dd>Controls which targets will be built and linked into llc. The default
855 value for <tt>target_options</tt> is "all" which builds and links all
856 available targets. The value "host-only" can be specified to build only a
857 native compiler (no cross-compiler targets available). The "native" target is
858 selected as the target of the build host. You can also specify a comma
859 separated list of target names that you want available in llc. The target
John Criswelle1a81202005-05-18 19:43:33 +0000860 names use all lower case. The current set of targets is: <br/>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000861 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000862 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000863 <dt><i>--enable-doxygen</i></dt>
864 <dd>Look for the doxygen program and enable construction of doxygen based
865 documentation from the source code. This is disabled by default because
866 generating the documentation can take a long time and producess 100s of
867 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +0000868 <dt><i>--with-udis86</i></dt>
869 <dd>LLVM can use external disassembler library for various purposes (now it's
870 used only for examining code produced by JIT). This option will enable usage
871 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
872 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000873</dl>
874
875<p>To configure LLVM, follow these steps:</p>
876
877<ol>
878 <li>Change directory into the object root directory:
John Criswellf531f312003-10-27 18:18:16 +0000879 <br>
Misha Brukman560e9892003-11-07 19:43:14 +0000880 <tt>cd <i>OBJ_ROOT</i></tt>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000881 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000882
Misha Brukman560e9892003-11-07 19:43:14 +0000883 <li>Run the <tt>configure</tt> script located in the LLVM source tree:
884 <br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000885 <tt><i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</tt>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000886 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000887</ol>
John Criswell72989a52003-06-12 19:34:44 +0000888
Misha Brukman560e9892003-11-07 19:43:14 +0000889</div>
John Criswell72989a52003-06-12 19:34:44 +0000890
Misha Brukman560e9892003-11-07 19:43:14 +0000891<!-- ======================================================================= -->
892<div class="doc_subsection">
893 <a name="compile">Compiling the LLVM Suite Source Code</a>
894</div>
John Criswell72989a52003-06-12 19:34:44 +0000895
Misha Brukman560e9892003-11-07 19:43:14 +0000896<div class="doc_text">
John Criswell71139f22003-07-08 20:35:59 +0000897
Misha Brukman560e9892003-11-07 19:43:14 +0000898<p>Once you have configured LLVM, you can build it. There are three types of
899builds:</p>
John Criswell71139f22003-07-08 20:35:59 +0000900
Misha Brukmand3de5c62004-01-20 00:20:17 +0000901<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000902 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000903 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000904 These builds are the default when one types <tt>gmake</tt> (unless the
905 <tt>--enable-optimized</tt> option was used during configuration). The
906 build system will compile the tools and libraries with debugging
907 information.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000908 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000909
910 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000911 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000912 These builds are enabled with the <tt>--enable-optimized</tt> option to
913 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
914 <tt>gmake</tt> command line. For these builds, the build system will
915 compile the tools and libraries with GCC optimizations enabled and strip
916 debugging information from the libraries and executables it generates.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000917 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000918
919 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000920 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000921 These builds are for use with profiling. They compile profiling
922 information into the code for use with programs like <tt>gprof</tt>.
923 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
924 on the <tt>gmake</tt> command line.
925</dl>
John Criswell3ef61af2003-06-30 21:59:07 +0000926
Misha Brukman560e9892003-11-07 19:43:14 +0000927<p>Once you have LLVM configured, you can build it by entering the
928<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +0000929
Misha Brukman560e9892003-11-07 19:43:14 +0000930<p><tt>gmake</tt></p>
John Criswell38cc2b52003-10-10 14:26:14 +0000931
Chris Lattnere0050f02004-07-18 22:32:22 +0000932<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +0000933are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000934
935<p>
936If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +0000937the parallel build options provided by GNU Make. For example, you could use the
938command:</p>
John Criswell72989a52003-06-12 19:34:44 +0000939
Misha Brukman560e9892003-11-07 19:43:14 +0000940<p><tt>gmake -j2</tt></p>
John Criswellc5eb4602003-07-03 16:01:38 +0000941
Misha Brukman560e9892003-11-07 19:43:14 +0000942<p>There are several special targets which are useful when working with the LLVM
943source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000944
Misha Brukmand3de5c62004-01-20 00:20:17 +0000945<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000946 <dt><tt>gmake clean</tt>
947 <dd>
948 Removes all files generated by the build. This includes object files,
949 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000950 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +0000951
Reid Spencerdfcf7902004-12-08 16:51:31 +0000952 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000953 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +0000954 Removes everything that <tt>gmake clean</tt> does, but also removes files
955 generated by <tt>configure</tt>. It attempts to return the source tree to the
956 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000957 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +0000958
Misha Brukman62a2c1f2004-08-23 20:25:33 +0000959 <dt><tt>gmake install</tt>
960 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +0000961 Installs LLVM header files, libraries, tools, and documentation in a
962 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +0000963 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
964 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000965 <br><br>
966
Reid Spencerdfcf7902004-12-08 16:51:31 +0000967 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000968 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +0000969 Assuming you built LLVM into $OBJDIR, when this command is run, it will
970 install bytecode libraries into the GCC front end's bytecode library
971 directory. If you need to update your bytecode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +0000972 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000973 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000974</dl>
John Criswellc5eb4602003-07-03 16:01:38 +0000975
Reid Spencerdfcf7902004-12-08 16:51:31 +0000976<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
977details on these <tt>make</tt> targets and descriptions of other targets
978available.</p>
979
Misha Brukman560e9892003-11-07 19:43:14 +0000980<p>It is also possible to override default values from <tt>configure</tt> by
981declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000982
Misha Brukmand3de5c62004-01-20 00:20:17 +0000983<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000984 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
985 <dd>
986 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000987 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +0000988
Reid Spencer3dc3ea72006-04-09 23:45:38 +0000989 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +0000990 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +0000991 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000992 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +0000993
Misha Brukman560e9892003-11-07 19:43:14 +0000994 <dt><tt>gmake ENABLE_PROFILING=1</tt>
995 <dd>
996 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000997 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +0000998
Misha Brukman560e9892003-11-07 19:43:14 +0000999 <dt><tt>gmake VERBOSE=1</tt>
1000 <dd>
1001 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001002 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001003
1004 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1005 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001006 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001007 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001008</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001009
Misha Brukman560e9892003-11-07 19:43:14 +00001010<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1011it and any subdirectories that it contains. Entering any directory inside the
1012LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1013that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001014
Misha Brukman560e9892003-11-07 19:43:14 +00001015</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001016
Misha Brukman560e9892003-11-07 19:43:14 +00001017<!-- ======================================================================= -->
1018<div class="doc_subsection">
Reid Spencer734b74f2006-07-27 06:41:31 +00001019 <a name="cross-compile">Cross-Compiling LLVM</a>
Reid Spencerd966b242006-07-27 05:43:30 +00001020</div>
1021
1022<div class="doc_text">
Reid Spencer734b74f2006-07-27 06:41:31 +00001023 <p>It is possible to cross-compile LLVM. That is, you can create LLVM
1024 executables and libraries for a platform different than the one one which you
1025 are compiling. To do this, a few additional steps are
1026 required. <sup><a href="#ccn_1">1</a></sup> To cross-compile LLVM, use
Reid Spencerd966b242006-07-27 05:43:30 +00001027 these instructions:</p>
1028 <ol>
Reid Spencer734b74f2006-07-27 06:41:31 +00001029 <li>Configure and build LLVM as a native compiler. You will need
Reid Spencerd966b242006-07-27 05:43:30 +00001030 just <tt>TableGen</tt> from that build.
1031 <ul>
1032 <li>If you have <tt>$LLVM_OBJ_ROOT=$LLVM_SRC_ROOT</tt> just execute
1033 <tt>make -C utils/TableGen</tt> after configuring.</li>
1034 <li>Otherwise you will need to monitor building process and terminate
1035 it just after <tt>TableGen</tt> was built.</li>
1036 </ul>
1037 </li>
1038 <li>Copy the TableGen binary to somewhere safe (out of your build tree).
1039 </li>
Reid Spencer734b74f2006-07-27 06:41:31 +00001040 <li>Configure LLVM to build with a cross-compiler. To do this, supply the
Reid Spencerd966b242006-07-27 05:43:30 +00001041 configure script with <tt>--build</tt> and <tt>--host</tt> options that
Reid Spencer734b74f2006-07-27 06:41:31 +00001042 are different. The values of these options must be legal target triples
1043 that your GCC compiler supports.</li>
Reid Spencerd966b242006-07-27 05:43:30 +00001044 <li>Put the saved <tt>TableGen</tt> executable into the
1045 into <tt>$LLVM_OBJ_ROOT/{BUILD_TYPE}/bin</tt> directory (e.g. into
1046 <tt>.../Release/bin</tt> for a Release build).</li>
1047 <li>Build LLVM as usual.</li>
1048 </ol>
Reid Spencer734b74f2006-07-27 06:41:31 +00001049 <p>The result of such a build will produce executables that are not executable
1050 on your build host (--build option) but can be executed on your compile host
1051 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001052 <p><b>Notes:</b></p>
1053 <div class="doc_notes">
1054 <ol>
1055 <li><a name="ccn_1">Cross-compiling</a> was tested only with Linux as
1056 build platform and Windows as host using mingw32 cross-compiler. Other
1057 combinations have not been tested.</li>
1058 </ol>
1059 </div>
1060</div>
1061
1062<!-- ======================================================================= -->
1063<div class="doc_subsection">
Misha Brukman560e9892003-11-07 19:43:14 +00001064 <a name="objfiles">The Location of LLVM Object Files</a>
1065</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001066
Misha Brukman560e9892003-11-07 19:43:14 +00001067<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +00001068
Misha Brukman560e9892003-11-07 19:43:14 +00001069<p>The LLVM build system is capable of sharing a single LLVM source tree among
1070several LLVM builds. Hence, it is possible to build LLVM for several different
1071platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001072
Misha Brukman560e9892003-11-07 19:43:14 +00001073<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001074
Misha Brukman560e9892003-11-07 19:43:14 +00001075<ul>
1076 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001077
Misha Brukman560e9892003-11-07 19:43:14 +00001078 <p><tt>cd <i>OBJ_ROOT</i></tt></p></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001079
Misha Brukman560e9892003-11-07 19:43:14 +00001080 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1081 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001082
Misha Brukman560e9892003-11-07 19:43:14 +00001083 <p><tt><i>SRC_ROOT</i>/configure</tt></p></li>
1084</ul>
John Criswell72989a52003-06-12 19:34:44 +00001085
Misha Brukman560e9892003-11-07 19:43:14 +00001086<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1087named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001088
Misha Brukmand3de5c62004-01-20 00:20:17 +00001089<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001090 <dt>Debug Builds
1091 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001092 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001093 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001094 <dd><tt><i>OBJ_ROOT</i>/Debug/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001095 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001096 <dd><tt><i>OBJ_ROOT</i>/Debug/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001097 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001098 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001099
Misha Brukman560e9892003-11-07 19:43:14 +00001100 <dt>Release Builds
1101 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001102 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001103 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001104 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001105 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001106 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001107 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001108 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001109
Misha Brukman560e9892003-11-07 19:43:14 +00001110 <dt>Profile Builds
1111 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001112 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001113 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001114 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001115 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001116 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001117 </dl>
1118</dl>
John Criswell72989a52003-06-12 19:34:44 +00001119
Misha Brukman560e9892003-11-07 19:43:14 +00001120</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001121
Chris Lattner998c0672004-03-25 20:38:40 +00001122<!-- ======================================================================= -->
1123<div class="doc_subsection">
1124 <a name="optionalconfig">Optional Configuration Items</a>
1125</div>
1126
1127<div class="doc_text">
1128
1129<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001130If you're running on a Linux system that supports the "<a
Reid Spencerdfcf7902004-12-08 16:51:31 +00001131 href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">
1132 binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001133module, and you have root access on the system, you can set your system up to
1134execute LLVM bytecode files directly. To do this, use commands like this (the
1135first command may not be required if you are already using the module):</p>
1136
Misha Brukman20b8a6562005-02-03 22:25:23 +00001137<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001138<pre>
1139 $ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Misha Brukman20b8a6562005-02-03 22:25:23 +00001140 $ echo ':llvm:M::llvm::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Chris Lattner998c0672004-03-25 20:38:40 +00001141 $ chmod u+x hello.bc (if needed)
1142 $ ./hello.bc
1143</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001144</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001145
1146<p>
1147This allows you to execute LLVM bytecode files directly. Thanks to Jack
1148Cummings for pointing this out!
1149</p>
1150
1151</div>
1152
1153
Misha Brukman560e9892003-11-07 19:43:14 +00001154<!-- *********************************************************************** -->
1155<div class="doc_section">
1156 <a name="layout"><b>Program Layout</b></a>
1157</div>
1158<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001159
Misha Brukman560e9892003-11-07 19:43:14 +00001160<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001161
Misha Brukman560e9892003-11-07 19:43:14 +00001162<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell64f13ab2004-03-12 20:31:37 +00001163href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001164href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001165The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001166
Misha Brukman560e9892003-11-07 19:43:14 +00001167</div>
John Criswell72989a52003-06-12 19:34:44 +00001168
Misha Brukman560e9892003-11-07 19:43:14 +00001169<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001170<div class="doc_subsection"><a name="cvsdir"><tt>CVS</tt> directories</a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001171<div class="doc_text">
Misha Brukman560e9892003-11-07 19:43:14 +00001172<p>Every directory checked out of CVS will contain a <tt>CVS</tt> directory; for
1173the most part these can just be ignored.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001174</div>
John Criswell72989a52003-06-12 19:34:44 +00001175
Reid Spencer5be4f042004-12-08 16:18:26 +00001176<!-- ======================================================================= -->
1177<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1178<div class="doc_text">
1179 <p>This directory contains some simple examples of how to use the LLVM IR and
1180 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001181</div>
John Criswell72989a52003-06-12 19:34:44 +00001182
Misha Brukman560e9892003-11-07 19:43:14 +00001183<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001184<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001185<div class="doc_text">
1186
1187<p>This directory contains public header files exported from the LLVM
1188library. The three main subdirectories of this directory are:</p>
1189
Reid Spencer075de232004-09-05 20:50:22 +00001190<dl>
1191 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1192 <dd>This directory contains all of the LLVM specific header files. This
1193 directory also has subdirectories for different portions of LLVM:
1194 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1195 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001196
Reid Spencer075de232004-09-05 20:50:22 +00001197 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1198 <dd>This directory contains generic support libraries that are provided with
1199 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1200 and a Command Line option processing library store their header files here.
1201 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001202
Reid Spencer075de232004-09-05 20:50:22 +00001203 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1204 <dd>This directory contains header files configured by the <tt>configure</tt>
1205 script. They wrap "standard" UNIX and C header files. Source code can
1206 include these header files which automatically take care of the conditional
1207 #includes that the <tt>configure</tt> script generates.</dd>
1208</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001209</div>
1210
1211<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001212<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001213<div class="doc_text">
1214
1215<p>This directory contains most of the source files of the LLVM system. In LLVM,
1216almost all code exists in libraries, making it very easy to share code among the
1217different <a href="#tools">tools</a>.</p>
1218
Misha Brukmand3de5c62004-01-20 00:20:17 +00001219<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001220 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1221 <dd> This directory holds the core LLVM source files that implement core
1222 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001223
Reid Spencer075de232004-09-05 20:50:22 +00001224 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1225 <dd>This directory holds the source code for the LLVM assembly language parser
1226 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001227
Reid Spencer075de232004-09-05 20:50:22 +00001228 <dt><tt><b>llvm/lib/ByteCode/</b></tt></dt>
1229 <dd>This directory holds code for reading and write LLVM bytecode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001230
Reid Spencer075de232004-09-05 20:50:22 +00001231 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001232 different program analyses, such as Dominator Information, Call Graphs,
1233 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001234 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001235
Reid Spencer075de232004-09-05 20:50:22 +00001236 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1237 <dd> This directory contains the source code for the LLVM to LLVM program
1238 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1239 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1240 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001241
Reid Spencer075de232004-09-05 20:50:22 +00001242 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1243 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001244 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1245 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +00001246 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001247
Reid Spencer075de232004-09-05 20:50:22 +00001248 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1249 <dd> This directory contains the major parts of the code generator: Instruction
1250 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001251
Reid Spencer075de232004-09-05 20:50:22 +00001252 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1253 <dd> This directory contains the source level debugger library that makes
1254 it possible to instrument LLVM programs so that a debugger could identify
1255 source code locations at which the program is executing.</dd>
1256
1257 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
1258 <dd> This directory contains libraries for executing LLVM bytecode directly
1259 at runtime in both interpreted and JIT compiled fashions.</dd>
1260
1261 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1262 <dd> This directory contains the source code that corresponds to the header
1263 files located in <tt>llvm/include/Support/</tt>.</dd>
1264
1265 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1266 <dd>This directory contains the operating system abstraction layer that
1267 shields LLVM from platform-specific coding.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001268</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001269
Misha Brukman560e9892003-11-07 19:43:14 +00001270</div>
John Criswell72989a52003-06-12 19:34:44 +00001271
Misha Brukman560e9892003-11-07 19:43:14 +00001272<!-- ======================================================================= -->
Reid Spencer5be4f042004-12-08 16:18:26 +00001273<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1274<div class="doc_text">
1275 <p>This directory contains projects that are not strictly part of LLVM but are
1276 shipped with LLVM. This is also the directory where you should create your own
1277 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
1278 to set up your own project. See <tt>llvm/projects/Stacker</tt> for a fully
1279 functional example of a compiler front end.</p>
1280</div>
1281
1282<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001283<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001284<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001285
Misha Brukman560e9892003-11-07 19:43:14 +00001286<p>This directory contains libraries which are compiled into LLVM bytecode and
1287used when linking programs with the GCC front end. Most of these libraries are
1288skeleton versions of real libraries; for example, libc is a stripped down
1289version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001290
Misha Brukman560e9892003-11-07 19:43:14 +00001291<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1292end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001293
Misha Brukman560e9892003-11-07 19:43:14 +00001294</div>
John Criswell72989a52003-06-12 19:34:44 +00001295
Misha Brukman560e9892003-11-07 19:43:14 +00001296<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001297<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001298<div class="doc_text">
Reid Spencer075de232004-09-05 20:50:22 +00001299 <p>This directory contains feature and regression tests and other basic sanity
1300 checks on the LLVM infrastructure. These are intended to run quickly and cover
1301 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001302</div>
John Criswell72989a52003-06-12 19:34:44 +00001303
Misha Brukman560e9892003-11-07 19:43:14 +00001304<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001305<div class="doc_subsection"><a name="llvmtest"><tt>llvm-test</tt></a></div>
1306<div class="doc_text">
John Criswell6ab273c2004-12-08 17:53:54 +00001307 <p>This is not a directory in the normal llvm module; it is a separate CVS
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001308 module that must be checked out (usually to <tt>projects/llvm-test</tt>). This
John Criswell6ab273c2004-12-08 17:53:54 +00001309 module contains a comprehensive correctness, performance, and benchmarking
1310 test
Reid Spencer075de232004-09-05 20:50:22 +00001311 suite for LLVM. It is a separate CVS module because not every LLVM user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001312 interested in downloading or building such a comprehensive test suite. For
1313 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001314 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001315</div>
John Criswell72989a52003-06-12 19:34:44 +00001316
Reid Spencer075de232004-09-05 20:50:22 +00001317<!-- ======================================================================= -->
1318<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001319<div class="doc_text">
John Criswell38cc2b52003-10-10 14:26:14 +00001320
Misha Brukman560e9892003-11-07 19:43:14 +00001321<p>The <b>tools</b> directory contains the executables built out of the
1322libraries above, which form the main part of the user interface. You can
1323always get help for a tool by typing <tt>tool_name --help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001324following is a brief introduction to the most important tools. More detailed
1325information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001326
Misha Brukmand3de5c62004-01-20 00:20:17 +00001327<dl>
John Criswell72989a52003-06-12 19:34:44 +00001328
Reid Spencer075de232004-09-05 20:50:22 +00001329 <dt><tt><b>bugpoint</b></tt></dt>
1330 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001331 optimization passes or code generation backends by narrowing down the
1332 given test case to the minimum number of passes and/or instructions that
1333 still cause a problem, whether it is a crash or miscompilation. See <a
1334 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001335 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001336
Reid Spencer075de232004-09-05 20:50:22 +00001337 <dt><tt><b>llvmc</b></tt></dt>
1338 <dd>The LLVM Compiler Driver. This program can
1339 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1340 pre-processing, translation, optimization, assembly, and linking of programs
1341 all from one command line. <tt>llvmc</tt> also takes care of processing the
1342 dependent libraries found in bytecode. This reduces the need to get the
Reid Spencer92815e52004-12-08 18:00:30 +00001343 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswelle1a81202005-05-18 19:43:33 +00001344 note that this tool, while functional, is still experimental and not feature
1345 complete.</dd>
Reid Spencer075de232004-09-05 20:50:22 +00001346
1347 <dt><tt><b>llvm-ar</b></tt></dt>
1348 <dd>The archiver produces an archive containing
Misha Brukman560e9892003-11-07 19:43:14 +00001349 the given LLVM bytecode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001350 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001351
Reid Spencer075de232004-09-05 20:50:22 +00001352 <dt><tt><b>llvm-as</b></tt></dt>
1353 <dd>The assembler transforms the human readable LLVM assembly to LLVM
1354 bytecode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001355
Reid Spencer075de232004-09-05 20:50:22 +00001356 <dt><tt><b>llvm-dis</b></tt></dt>
1357 <dd>The disassembler transforms the LLVM bytecode to human readable
1358 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001359
Reid Spencer92815e52004-12-08 18:00:30 +00001360 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001361 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
1362 This is the linker invoked by <tt>llvmc</tt>. It performsn standard link time
1363 optimizations and allows optimization modules to be loaded and run so that
1364 language specific optimizations can be applied at link time.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +00001365
Reid Spencer075de232004-09-05 20:50:22 +00001366 <dt><tt><b>llvm-link</b></tt></dt>
1367 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1368 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001369
Reid Spencer075de232004-09-05 20:50:22 +00001370 <dt><tt><b>lli</b></tt></dt>
1371 <dd><tt>lli</tt> is the LLVM interpreter, which
Misha Brukman560e9892003-11-07 19:43:14 +00001372 can directly execute LLVM bytecode (although very slowly...). In addition
1373 to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
1374 specifying <tt>-trace</tt> on the command line). Finally, for
John Criswell945f8022004-12-08 18:04:14 +00001375 architectures that support it (currently x86, Sparc, and PowerPC), by default,
Misha Brukman560e9892003-11-07 19:43:14 +00001376 <tt>lli</tt> will function as a Just-In-Time compiler (if the
1377 functionality was compiled in), and will execute the code <i>much</i>
Reid Spencer075de232004-09-05 20:50:22 +00001378 faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001379
Reid Spencer075de232004-09-05 20:50:22 +00001380 <dt><tt><b>llc</b></tt></dt>
1381 <dd> <tt>llc</tt> is the LLVM backend compiler, which
John Criswelle1a81202005-05-18 19:43:33 +00001382 translates LLVM bytecode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001383 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001384
Reid Spencer788b0fd2004-12-22 06:29:07 +00001385 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001386 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1387 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
1388 byte code or assembly (with the <tt>-emit-llvm</tt> option) instead of the
1389 usual machine code output. It works just like any other GCC compiler,
1390 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1391 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
1392 separate CVS module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001393
Reid Spencer075de232004-09-05 20:50:22 +00001394 <dt><tt><b>opt</b></tt></dt>
Reid Spencer80f843d2006-08-28 00:34:19 +00001395 <dd><tt>opt</tt> reads LLVM bytecode, applies a series of LLVM to LLVM
1396 transformations (which are specified on the command line), and then outputs
1397 the resultant bytecode. The '<tt>opt --help</tt>' command is a good way to
1398 get a list of the program transformations available in LLVM.<br/>
1399 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
1400 LLVM bytecode file and print out the results. It is primarily useful for
1401 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001402</dl>
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<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +00001406<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +00001407<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001408
Misha Brukman560e9892003-11-07 19:43:14 +00001409<p>This directory contains utilities for working with LLVM source code, and some
1410of the utilities are actually required as part of the build process because they
1411are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001412
Misha Brukmand3de5c62004-01-20 00:20:17 +00001413<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001414 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001415 that finds differences between code that LLC generates and code that LLI
1416 generates. This is a useful tool if you are debugging one of them,
1417 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001418 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001419
Misha Brukmand3de5c62004-01-20 00:20:17 +00001420 <dt><tt><b>cvsupdate</b></tt> <dd><tt>cvsupdate</tt> is a script that will
Misha Brukman560e9892003-11-07 19:43:14 +00001421 update your CVS tree, but produce a much cleaner and more organized output
1422 than simply running <tt>`cvs -z3 up -dP'</tt> will. For example, it will group
1423 together all the new and updated files and modified files in separate
1424 sections, so you can see at a glance what has changed. If you are at the
1425 top of your LLVM CVS tree, running <tt>utils/cvsupdate</tt> is the
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001426 preferred way of updating the tree.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001427
Misha Brukmand3de5c62004-01-20 00:20:17 +00001428 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001429 syntax-highlighting files which will work with Emacs and XEmacs editors,
1430 providing syntax highlighting support for LLVM assembly files and TableGen
1431 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001432 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001433
Misha Brukmand3de5c62004-01-20 00:20:17 +00001434 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001435 and outputs all non-generated source files, which is useful if one wishes
1436 to do a lot of development across directories and does not want to
1437 individually find each file. One way to use it is to run, for example:
1438 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001439 tree.<br><br>
1440
Reid Spencer075de232004-09-05 20:50:22 +00001441 <dt><tt><b>llvmgrep</b></tt></dt>
1442 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1443 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1444 line. This is a very efficient way of searching the source base for a
1445 particular regular expression.</dd>
1446
Misha Brukmand3de5c62004-01-20 00:20:17 +00001447 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001448 files in the current directory and then compiles and links the tool that
1449 is the first argument. For example, assuming you are in the directory
1450 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1451 simply running <tt>makellvm llc</tt> will make a build of the current
1452 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001453 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001454
Tanya Lattner3e852072007-05-22 06:12:51 +00001455 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukmand3de5c62004-01-20 00:20:17 +00001456 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman560e9892003-11-07 19:43:14 +00001457 cron script to generate nightly status reports of the functionality of
1458 tools, and the results can be seen by following the appropriate link on
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001459 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001460
Misha Brukmand3de5c62004-01-20 00:20:17 +00001461 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001462 the tool used to generate register descriptions, instruction set
1463 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001464 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001465
Misha Brukmand3de5c62004-01-20 00:20:17 +00001466 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001467 syntax-highlighting files which will work with the VIM editor, providing
1468 syntax highlighting support for LLVM assembly files and TableGen
1469 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001470 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001471
Misha Brukman560e9892003-11-07 19:43:14 +00001472</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001473
Misha Brukman560e9892003-11-07 19:43:14 +00001474</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001475
Reid Spencer5be4f042004-12-08 16:18:26 +00001476<!-- ======================================================================= -->
1477<div class="doc_subsection"><a name="win32"><tt>llvm/win32</tt></a></div>
1478<div class="doc_text">
1479 <p>This directory contains build scripts and project files for use with
1480 Visual C++. This allows developers on Windows to build LLVM without the need
John Criswell6ab273c2004-12-08 17:53:54 +00001481 for Cygwin. The contents of this directory should be considered experimental
Reid Spencer5be4f042004-12-08 16:18:26 +00001482 at this time.
1483 </p>
1484</div>
Misha Brukman560e9892003-11-07 19:43:14 +00001485<!-- *********************************************************************** -->
1486<div class="doc_section">
1487 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1488</div>
1489<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001490
Misha Brukman560e9892003-11-07 19:43:14 +00001491<div class="doc_text">
Chris Lattner424d4dc2007-01-04 07:08:27 +00001492<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
1493so we only include instructiosn for llvm-gcc4.
Chris Lattner5b560d92006-08-14 20:45:25 +00001494</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001495
1496<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1497from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
1498create bytecode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1499the '--emit-llvm' flag is needed to produce LLVM bytecode output. For <i>makefiles</i> and
1500<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bytecode
1501output.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001502</div>
1503
1504<!-- ======================================================================= -->
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001505<div class="doc_subsection"><a name="tutorial4">Example with llvm-gcc4</a></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001506
1507<div class="doc_text">
1508
1509<ol>
1510 <li>First, create a simple C file, name it 'hello.c':
1511 <pre>
1512 #include &lt;stdio.h&gt;
1513 int main() {
1514 printf("hello world\n");
1515 return 0;
1516 }
1517 </pre></li>
1518
1519 <li><p>Next, compile the C file into a native executable:</p>
1520
1521 <p><tt>% llvm-gcc hello.c -o hello</tt></p>
1522
1523 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1524 -c arguments work as usual (producing a native .s or .o file,
1525 respectively). </p>
1526
1527 <li><p>Next, compile the C file into a LLVM bytecode file:</p>
1528 <p><tt>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</tt></p>
1529
1530 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1531 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1532 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
1533 the bytecode file.</p>
1534
1535 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1536 </p></li>
1537
1538 <li><p>Run the program in both forms. To run the program, use:</p>
1539
1540 <p><tt>% ./hello</tt></p>
1541
1542 <p>and</p>
1543
Chris Lattnerc7443af2006-08-14 20:51:35 +00001544 <p><tt>% lli hello.bc</tt></p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001545
1546 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001547 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001548
1549 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1550 code:</p>
1551
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001552 <p><tt>% llvm-dis &lt; hello.bc | less</tt><br><br></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001553
1554 <li><p>Compile the program to native assembly using the LLC code
1555 generator:</p>
1556
1557 <p><tt>% llc hello.bc -o hello.s</tt></p>
1558
1559 <li><p>Assemble the native assembly language file into a program:</p>
1560
1561 <p><b>Solaris:</b><tt>% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native</tt></p>
1562 <p><b>Others:</b><tt>% gcc hello.s -o hello.native</tt></p>
1563
1564 <li><p>Execute the native code program:</p>
1565
Chris Lattnerc7443af2006-08-14 20:51:35 +00001566 <p><tt>% ./hello.native</tt></p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001567
1568 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1569 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001570 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001571
1572</ol>
1573
1574</div>
1575
John Criswell72989a52003-06-12 19:34:44 +00001576
Misha Brukman560e9892003-11-07 19:43:14 +00001577<!-- *********************************************************************** -->
1578<div class="doc_section">
1579 <a name="problems">Common Problems</a>
1580</div>
1581<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001582
Misha Brukman560e9892003-11-07 19:43:14 +00001583<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +00001584
Misha Brukman560e9892003-11-07 19:43:14 +00001585<p>If you are having problems building or using LLVM, or if you have any other
1586general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1587Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001588
Misha Brukman560e9892003-11-07 19:43:14 +00001589</div>
John Criswell72989a52003-06-12 19:34:44 +00001590
Misha Brukman560e9892003-11-07 19:43:14 +00001591<!-- *********************************************************************** -->
1592<div class="doc_section">
1593 <a name="links">Links</a>
1594</div>
1595<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001596
Misha Brukman560e9892003-11-07 19:43:14 +00001597<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +00001598
Misha Brukman560e9892003-11-07 19:43:14 +00001599<p>This document is just an <b>introduction</b> to how to use LLVM to do
1600some simple things... there are many more interesting and complicated things
1601that you can do that aren't documented here (but we'll gladly accept a patch
1602if you want to write something up!). For more information about LLVM, check
1603out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001604
Misha Brukman560e9892003-11-07 19:43:14 +00001605<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001606 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1607 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1608 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001609 that Uses LLVM</a></li>
1610</ul>
1611
1612</div>
1613
1614<!-- *********************************************************************** -->
1615
1616<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001617<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001618 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1619 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1620 <a href="http://validator.w3.org/check/referer"><img
1621 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
1622
Misha Brukman74d4df82003-11-22 01:30:01 +00001623 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001624 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencerca058542006-03-14 05:39:39 +00001625 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001626 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001627</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001628</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001629</html>