blob: 69510e85be6c434986a7727a03db23219426c323 [file] [log] [blame]
Misha Brukman00c73d22003-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 Shif4688a82002-07-17 23:05:56 +00003<html>
Misha Brukman00c73d22003-11-07 19:43:14 +00004<head>
Reid Spencer748d82e2004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman00c73d22003-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 Criswell85ed3612003-06-12 19:34:44 +000010
Misha Brukman00c73d22003-11-07 19:43:14 +000011<div class="doc_title">
12 Getting Started with the LLVM System
13</div>
John Criswell85ed3612003-06-12 19:34:44 +000014
Misha Brukman00c73d22003-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 Lattner96768ea2003-02-14 04:22:13 +000019 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000023 </ol></li>
John Criswell7a73b802003-06-30 21:59:07 +000024
Misha Brukman00c73d22003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell0b459202003-07-08 20:35:59 +000026 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
31 <li><a href="#installcf">Install the GCC Front End</a></li>
32 <li><a href="#config">Local LLVM Configuration</a></li>
33 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
34 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
35 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
36 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000037 </ol></li>
John Criswell0b459202003-07-08 20:35:59 +000038
Misha Brukman00c73d22003-11-07 19:43:14 +000039 <li><a href="#layout">Program layout</a>
40 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000041 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
42 <li><a href="#include"><tt>llvm/include</tt></a></li>
43 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
44 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
45 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
46 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trickbcf01162010-09-23 20:26:44 +000047 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner269f80c2007-11-01 04:20:16 +000048 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
49 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000050 </ol></li>
John Criswell0f6d7c02003-10-27 18:18:16 +000051
Misha Brukman00c73d22003-11-07 19:43:14 +000052 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner9abd8af2006-09-07 04:19:09 +000053 <ol>
54 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner9abd8af2006-09-07 04:19:09 +000055 </ol>
Misha Brukman00c73d22003-11-07 19:43:14 +000056 <li><a href="#problems">Common Problems</a>
57 <li><a href="#links">Links</a>
58</ul>
59
Chris Lattner7911ce22004-05-23 21:07:27 +000060<div class="doc_author">
61 <p>Written by:
62 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
63 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
64 <a href="http://misha.brukman.net">Misha Brukman</a>,
65 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
66 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
67 </p>
68</div>
Misha Brukman00c73d22003-11-07 19:43:14 +000069
70
71<!-- *********************************************************************** -->
72<div class="doc_section">
73 <a name="overview"><b>Overview</b></a>
74</div>
75<!-- *********************************************************************** -->
76
77<div class="doc_text">
78
79<p>Welcome to LLVM! In order to get started, you first need to know some
80basic information.</p>
81
Andrew Trickbcf01162010-09-23 20:26:44 +000082<p>First, LLVM comes in three pieces. The first piece is the LLVM
83suite. This contains all of the tools, libraries, and header files
84needed to use the low level virtual machine. It contains an
85assembler, disassembler, bitcode analyzer and bitcode optimizer. It
86also contains basic regression tests that can be used to test the LLVM
87tools and the GCC front end.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000088
89<p>The second piece is the GCC front end. This component provides a version of
Gabor Greif04367bf2007-07-06 22:07:22 +000090GCC that compiles C and C++ code into LLVM bitcode. Currently, the GCC front
Chris Lattner82ad9f12007-03-06 06:27:34 +000091end uses the GCC parser to convert code to LLVM. Once
Gabor Greif04367bf2007-07-06 22:07:22 +000092compiled into LLVM bitcode, a program can be manipulated with the LLVM tools
Misha Brukman00c73d22003-11-07 19:43:14 +000093from the LLVM suite.</p>
94
John Criswell3d8ba512004-12-08 17:53:54 +000095<p>
Andrew Trickbcf01162010-09-23 20:26:44 +000096There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell3d8ba512004-12-08 17:53:54 +000097with a testing harness that can be used to further test LLVM's functionality
98and performance.
99</p>
100
Misha Brukman00c73d22003-11-07 19:43:14 +0000101</div>
102
103<!-- *********************************************************************** -->
104<div class="doc_section">
105 <a name="quickstart"><b>Getting Started Quickly (A Summary)</b></a>
106</div>
107<!-- *********************************************************************** -->
108
109<div class="doc_text">
110
111<p>Here's the short story for getting up and running quickly with LLVM:</p>
112
113<ol>
Reid Spencer9f547912004-11-08 00:29:22 +0000114 <li>Read the documentation.</li>
115 <li>Read the documentation.</li>
116 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000117 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
118 (see <a href="#installcf">Install the GCC Front End</a> for details):</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000119 <ol>
Reid Spencerd4694f92004-12-22 06:29:07 +0000120 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000121 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
122 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
123 <li>Note: If the binary extension is "<tt>.bz</tt>" use <tt>bunzip2</tt> instead of <tt>gunzip</tt>.</li>
124 <li>Note: On Windows, use <a href="http://www.7-zip.org">7-Zip</a> or a similar archiving tool.</li>
125 <li>Add <tt>llvm-gcc</tt>'s "<tt>bin</tt>" directory to your <tt>PATH</tt> environment variable.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000126 </ol></li>
127
Misha Brukman9106eca2005-02-03 22:25:23 +0000128 <li>Get the LLVM Source Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000129 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000130 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman00c73d22003-11-07 19:43:14 +0000131 <ol>
132 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell364cec42004-03-12 20:31:37 +0000133 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000134 </ol></li>
135
Misha Brukman00c73d22003-11-07 19:43:14 +0000136 </ul></li>
137
Misha Brukman9106eca2005-02-03 22:25:23 +0000138 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswell9e2485c2004-12-10 15:51:16 +0000139 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000140 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswell9e2485c2004-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>
Andrew Trickbcf01162010-09-23 20:26:44 +0000145 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswell9e2485c2004-12-10 15:51:16 +0000146 </ol></li>
147
John Criswell9e2485c2004-12-10 15:51:16 +0000148 </ul></li>
149
150
Misha Brukman00c73d22003-11-07 19:43:14 +0000151 <li>Configure the LLVM Build Environment
152 <ol>
Misha Brukman9106eca2005-02-03 22:25:23 +0000153 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
154 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
155 Some common options:
156
Misha Brukman00c73d22003-11-07 19:43:14 +0000157 <ul>
Reid Spencerd4694f92004-12-22 06:29:07 +0000158 <li><tt>--prefix=<i>directory</i></tt>
159 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000160 want the LLVM tools and libraries to be installed (default
161 <tt>/usr/local</tt>).</p></li>
Reid Spencerfef93b72004-12-26 05:47:26 +0000162 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
163 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswell838bce52005-05-09 16:39:27 +0000164 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sandsdc223762009-04-18 12:40:19 +0000165 not specified, the PATH will be searched. This is only needed if you
Andrew Trickbcf01162010-09-23 20:26:44 +0000166 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000167 <li><tt>--enable-spec2000=<i>directory</i></tt>
168 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
169 benchmarks should be available in
170 <tt><i>directory</i></tt>.</p></li>
171 </ul>
172 </ol></li>
173
174 <li>Build the LLVM Suite:
175 <ol>
Chris Lattner95e92582004-07-18 22:32:22 +0000176 <li><tt>gmake -k |&amp; tee gnumake.out
177 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000178 <li>If you get an "internal compiler error (ICE)" or test failures, see
179 <a href="#brokengcc">below</a>.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000180 </ol>
181
182</ol>
183
Chris Lattnerfcd37252004-06-21 22:52:48 +0000184<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000185detailed information on configuring and compiling LLVM. See <a
186href="#environment">Setting Up Your Environment</a> for tips that simplify
187working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
188Layout</a> to learn about the layout of the source code tree.</p>
189
190</div>
191
192<!-- *********************************************************************** -->
193<div class="doc_section">
194 <a name="requirements"><b>Requirements</b></a>
195</div>
196<!-- *********************************************************************** -->
197
198<div class="doc_text">
199
200<p>Before you begin to use the LLVM system, review the requirements given below.
201This may save you some trouble by knowing ahead of time what hardware and
202software you will need.</p>
203
204</div>
205
206<!-- ======================================================================= -->
207<div class="doc_subsection">
208 <a name="hardware"><b>Hardware</b></a>
209</div>
210
211<div class="doc_text">
212
213<p>LLVM is known to work on the following platforms:</p>
214
Chris Lattner9abd8af2006-09-07 04:19:09 +0000215<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000216<tr>
217 <th>OS</th>
218 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000219 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000220</tr>
221<tr>
Chris Lattnerd8afc462009-07-22 04:21:40 +0000222 <td>AuroraUX</td>
223 <td>x86<sup><a href="#pf_1">1</a></sup></td>
224 <td>GCC</td>
Chris Lattner3e7b5ca2009-07-21 22:47:03 +0000225</tr>
226<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000227 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000228 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000229 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000230</tr>
231<tr>
Edward O'Callaghan37442b72009-08-04 05:24:28 +0000232 <td>Linux</td>
233 <td>amd64</td>
234 <td>GCC</td>
235</tr>
236<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000237 <td>Solaris</td>
238 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000239 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000240</tr>
241<tr>
242 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000243 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000244 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000245</tr>
246<tr>
Bill Wendlingf7226992010-12-15 01:35:55 +0000247 <td>FreeBSD</td>
248 <td>amd64</td>
249 <td>GCC</td>
250</tr>
251<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000252 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000253 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000254 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000255</tr>
256<tr>
Scott Michel050bc812008-03-18 23:13:26 +0000257 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000258 <td>x86</td>
259 <td>GCC</td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000260</tr>
261<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000262 <td>Cygwin/Win32</td>
Anton Korobeynikov16f16922009-12-09 17:26:02 +0000263 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
264 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000265 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman69def742004-11-19 21:53:22 +0000266</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000267<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000268 <td>MinGW/Win32</td>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000269 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
270 <a href="#pf_8">8</a>, <a href="#pf_10">10</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000271 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000272</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000273</table>
274
275<p>LLVM has partial support for the following platforms:</p>
276
Chris Lattner9abd8af2006-09-07 04:19:09 +0000277<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000278<tr>
279 <th>OS</th>
280 <th>Arch</th>
281 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000282</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000283<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000284 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000285 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Nick Lewycky28ea4f62008-12-08 00:45:02 +0000286 <td>Visual Studio 2005 SP1 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000287<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000288 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000289 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000290 <td>GCC</td>
291</tr>
292<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000293 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000294 <td>PowerPC</td>
295 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000296</tr>
John Criswell75162552005-05-09 16:49:59 +0000297
298<tr>
299 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
300 <td>Alpha</td>
301 <td>GCC</td>
302</tr>
303<tr>
304 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
305 <td>Itanium (IA-64)</td>
306 <td>GCC</td>
307</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000308<tr>
309 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
310 <td>Itanium (IA-64)</td>
311 <td>HP aCC</td>
312</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000313</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000314
Misha Brukmana892ead2005-02-09 21:01:26 +0000315<p><b>Notes:</b></p>
316
Misha Brukman6d8e1532005-02-09 22:38:47 +0000317<div class="doc_notes">
318<ol>
319<li><a name="pf_1">Code generation supported for Pentium processors and
320up</a></li>
321<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
322<li><a name="pf_3">No native code generation</a></li>
Nick Lewycky28ea4f62008-12-08 00:45:02 +0000323<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000324<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner01bb8b02009-01-02 07:10:51 +0000325<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell75162552005-05-09 16:49:59 +0000326<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000327<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
328 generated by LLVM properly.</a></li>
Chris Lattner22b91d72008-11-09 17:19:14 +0000329<li><a name="pf_9">XCode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel050bc812008-03-18 23:13:26 +0000330 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner22b91d72008-11-09 17:19:14 +0000331 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
332 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel050bc812008-03-18 23:13:26 +0000333 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000334<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
335 version of the perl package, and be sure it appears in your path
336 before any Windows-based versions such as Strawberry Perl and
337 ActivePerl, as these have Windows-specifics that will cause the
338 build to fail.</a></li>
Anton Korobeynikov16f16922009-12-09 17:26:02 +0000339<li><a name="pf_11">In general, LLVM modules requiring dynamic linking can
340 not be built on Windows. However, you can build LLVM tools using
341 <i>"make tools-only"</i>.</li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000342</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000343</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000344
Misha Brukman69def742004-11-19 21:53:22 +0000345<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswell8bfe6a72005-05-18 19:43:33 +0000346mode, depending on the system (it is so large because of all the debugging
347information and the fact that the libraries are statically linked into multiple
Chris Lattner06942902009-04-25 22:08:52 +0000348tools). If you do not need many of the tools and you are space-conscious, you
349can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
350requires considerably less space.</p>
Misha Brukman69def742004-11-19 21:53:22 +0000351
Misha Brukman00c73d22003-11-07 19:43:14 +0000352<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
353guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greif04367bf2007-07-06 22:07:22 +0000354able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000355generation should work as well, although the generated native code may not work
356on your platform.</p>
357
358<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman22e9e332004-08-09 19:57:01 +0000359to work on another platform, you can download a copy of the source and <a
Duncan Sands8655b152008-02-14 17:53:22 +0000360href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000361
362</div>
363
364<!-- ======================================================================= -->
Reid Spencer748d82e2004-11-15 21:15:12 +0000365<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000366<div class="doc_text">
Reid Spencer748d82e2004-11-15 21:15:12 +0000367 <p>Compiling LLVM requires that you have several software packages
368 installed. The table below lists those required packages. The Package column
369 is the usual name for the software package that LLVM depends on. The Version
370 column provides "known to work" versions of the package. The Notes column
371 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000372 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000373 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000374
Reid Spencer748d82e2004-11-15 21:15:12 +0000375 <tr>
376 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
377 <td>3.79, 3.79.1</td>
378 <td>Makefile/build processor</td>
379 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000380
Reid Spencer748d82e2004-11-15 21:15:12 +0000381 <tr>
382 <td><a href="http://gcc.gnu.org">GCC</a></td>
383 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000384 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000385 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000386
Reid Spencer748d82e2004-11-15 21:15:12 +0000387 <tr>
Chris Lattner2286cab2005-09-06 04:07:15 +0000388 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
389 <td>4.5</td>
390 <td>For building the CFE</td>
391 </tr>
392
393 <tr>
John Criswell9c29bfb2007-06-29 19:12:31 +0000394 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
395 <td>&ge;1.3</td>
396 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000397 </tr>
398
399 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000400 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
401 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000402 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000403 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000404
Reid Spencer748d82e2004-11-15 21:15:12 +0000405 <tr>
406 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
407 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000408 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000409 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000410
Reid Spencer748d82e2004-11-15 21:15:12 +0000411 <tr>
412 <td><a href="http://expect.nist.gov/">expect</a></td>
413 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000414 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000415 </tr>
416
417 <tr>
418 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000419 <td>&ge;5.6.0</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000420 <td>Nightly tester, utilities</td>
421 </tr>
422
423 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000424 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
425 <td>1.4</td>
426 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000427 </tr>
428
429 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000430 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000431 <td>2.60</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000432 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
433 </tr>
434
435 <tr>
436 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000437 <td>1.9.6</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000438 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
439 </tr>
440
441 <tr>
442 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000443 <td>1.5.22</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000444 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000445 </tr>
446
447 </table>
448
Misha Brukman6d8e1532005-02-09 22:38:47 +0000449 <p><b>Notes:</b></p>
450 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000451 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000452 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000453 need to build the other languages for LLVM's purposes.</a> See
454 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell9c29bfb2007-06-29 19:12:31 +0000455 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman6d8e1532005-02-09 22:38:47 +0000456 latest LLVM sources. If you're working from a release distribution, you
John Criswell9c29bfb2007-06-29 19:12:31 +0000457 don't need Subversion.</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000458 <li><a name="sf3">Only needed if you want to run the automated test
459 suite in the <tt>llvm/test</tt> directory.</a></li>
460 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser0560ce42010-05-19 07:00:17 +0000461 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
462 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer200d93b2004-12-09 17:55:37 +0000463 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000464 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000465 </div>
466
Reid Spencer748d82e2004-11-15 21:15:12 +0000467 <p>Additionally, your compilation host is expected to have the usual
468 plethora of Unix utilities. Specifically:</p>
469 <ul>
470 <li><b>ar</b> - archive library builder</li>
471 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
472 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
473 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000474 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000475 <li><b>cp</b> - copy files</li>
476 <li><b>date</b> - print the current date/time </li>
477 <li><b>echo</b> - print to standard output</li>
478 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000479 <li><b>find</b> - find files/dirs in a file system</li>
480 <li><b>grep</b> - regular expression search utility</li>
481 <li><b>gzip*</b> - gzip command for distribution generation</li>
482 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
483 <li><b>install</b> - install directories/files </li>
484 <li><b>mkdir</b> - create a directory</li>
485 <li><b>mv</b> - move (rename) files</li>
486 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000487 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000488 <li><b>sed</b> - stream editor for transforming output</li>
489 <li><b>sh</b> - Bourne shell for make build scripts</li>
490 <li><b>tar</b> - tape archive for distribution generation</li>
491 <li><b>test</b> - test things in file system</li>
492 <li><b>unzip*</b> - unzip command for distribution checking</li>
493 <li><b>zip*</b> - zip command for distribution generation</li>
494 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000495</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000496
Chris Lattner95e92582004-07-18 22:32:22 +0000497<!-- ======================================================================= -->
498<div class="doc_subsection">
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000499 <a name="brokengcc">Broken versions of GCC and other tools</a>
Chris Lattner95e92582004-07-18 22:32:22 +0000500</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000501
Chris Lattner95e92582004-07-18 22:32:22 +0000502<div class="doc_text">
503
504<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
505bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner6557f182006-06-16 17:20:33 +0000506to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
Chris Lattner36117ac2007-05-10 06:42:21 +0000507successfully with them (however, see important notes below). Other versions
508of GCC will probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000509here are known to not work. If you are using one of these versions, please try
510to upgrade your GCC to something more recent. If you run into a problem with a
511version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
512us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
513of GCC you are using.
514</p>
515
516<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
517problems in the STL that effectively prevent it from compiling LLVM.
518</p>
519
Chris Lattner82f0a092008-02-13 17:50:24 +0000520<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
521a bogus template error. This was fixed in later GCCs.</p>
John Criswell294ba022004-11-23 22:06:24 +0000522
Chris Lattner95e92582004-07-18 22:32:22 +0000523<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
524href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
525the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000526
Chris Lattner8e64f152005-02-13 22:20:49 +0000527<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands8655b152008-02-14 17:53:22 +0000528 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner8e64f152005-02-13 22:20:49 +0000529 to a newer version</a> if possible.</p>
530<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
531 possibly others) does not compile LLVM correctly (it appears that exception
532 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
533 to a newer version of GCC.</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000534<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000535 code generator, causing an infinite loop in the llvm-gcc build when built
536 with optimizations enabled (i.e. a release build).</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000537<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000538 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
539 correctly compiles LLVM at -O2. A work around is to build release LLVM
540 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000541<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner77c2af62007-04-01 20:14:46 +0000542 miscompiles portions of LLVM</a>.</p>
Chris Lattner269f80c2007-11-01 04:20:16 +0000543<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
544 when building with optimizations enabled. It appears to work with
545 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
546 build.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000547<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
548 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000549<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
550 default with ENABLE_OPTIMIZED=1. To work around this, build with
551 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000552<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
553 compiling some files. At the time of this writing, GCC mainline (4.2)
554 did not share the problem.</p>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000555<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
556 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
557 code. LLVM will appear to mostly work but will be buggy, e.g. failing
558 portions of its testsuite.</p>
Reid Spencer72f92f02007-04-11 21:28:31 +0000559<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
560platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbarb7dfaf92008-10-11 18:40:33 +0000561<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
562to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
563about symbols remaining in the table on destruction.</p>
Nuno Lopesf82242d2008-12-10 16:11:10 +0000564<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes58dc0b52008-12-10 16:01:22 +0000565as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Mike Stumpfe095f32009-05-04 18:40:41 +0000566<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
567 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
568 with link errors when using this GCC version.</p>
Chris Lattner478e71d2009-09-10 16:25:02 +0000569<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewycky3bf2d032009-07-17 06:32:10 +0000570<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
571when optimizations are turned on. The symptom is an infinite loop in
Chris Lattner478e71d2009-09-10 16:25:02 +0000572FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewycky256f9602010-10-07 22:30:47 +0000573<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5741</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
575one symptom of the problem.
Reid Spencer7a119082006-11-04 00:33:42 +0000576<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
577long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
578defined in a discarded section. You can safely ignore these messages as they are
579erroneous and the linkage is correct. These messages disappear using ld
5802.17.</p>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000581
582<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
583href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
584causes huge link times (minutes instead of seconds) when building LLVM. We
585recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
586
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000587<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000588<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
589which causes intermittent failures when building LLVM with position independent
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000590code. The symptom is an error about cyclic dependencies. We recommend
591upgrading to a newer version of Gold.</p>
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000592
Misha Brukman00c73d22003-11-07 19:43:14 +0000593</div>
594
Chris Lattner95e92582004-07-18 22:32:22 +0000595
596
Misha Brukman00c73d22003-11-07 19:43:14 +0000597<!-- *********************************************************************** -->
598<div class="doc_section">
599 <a name="starting"><b>Getting Started with LLVM</b></a>
600</div>
601<!-- *********************************************************************** -->
602
Chris Lattner95e92582004-07-18 22:32:22 +0000603<div class="doc_text">
604
605<p>The remainder of this guide is meant to get you up and running with
606LLVM and to give you some basic information about the LLVM environment.</p>
607
608<p>The later sections of this guide describe the <a
609href="#layout">general layout</a> of the the LLVM source tree, a <a
610href="#tutorial">simple example</a> using the LLVM tool chain, and <a
611href="#links">links</a> to find more information about LLVM or to get
612help via e-mail.</p>
613</div>
614
Misha Brukman00c73d22003-11-07 19:43:14 +0000615<!-- ======================================================================= -->
616<div class="doc_subsection">
617 <a name="terminology">Terminology and Notation</a>
618</div>
619
620<div class="doc_text">
621
622<p>Throughout this manual, the following names are used to denote paths
623specific to the local system and working environment. <i>These are not
624environment variables you need to set but just strings used in the rest
625of this document below</i>. In any of the examples below, simply replace
626each of these names with the appropriate pathname on your local system.
627All these paths are absolute:</p>
628
Misha Brukman54111c42004-01-20 00:20:17 +0000629<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000630 <dt>SRC_ROOT
631 <dd>
632 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000633 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000634
Misha Brukman00c73d22003-11-07 19:43:14 +0000635 <dt>OBJ_ROOT
636 <dd>
637 This is the top level directory of the LLVM object tree (i.e. the
638 tree where object files and compiled programs will be placed. It
639 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000640 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000641
642 <dt>LLVMGCCDIR
643 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000644 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000645 <p>
646 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000647 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +0000648</dl>
649
650</div>
651
652<!-- ======================================================================= -->
653<div class="doc_subsection">
654 <a name="environment">Setting Up Your Environment</a>
655</div>
656
657<div class="doc_text">
658
659<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000660In order to compile and use LLVM, you may need to set some environment
661variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000662
Misha Brukman54111c42004-01-20 00:20:17 +0000663<dl>
Gabor Greif04367bf2007-07-06 22:07:22 +0000664 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000665 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greif04367bf2007-07-06 22:07:22 +0000666 locations of your bitcode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000667 convenience since you can specify the paths using the -L options of the
Gabor Greif04367bf2007-07-06 22:07:22 +0000668 tools and the C/C++ front-end will automatically use the bitcode files
John Criswell8bfe6a72005-05-18 19:43:33 +0000669 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000670 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000671</dl>
672
673</div>
674
675<!-- ======================================================================= -->
676<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000677 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000678</div>
679
680<div class="doc_text">
681
682<p>
683If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000684can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000685suite and the LLVM GCC front end compiled for your platform. There is an
686additional test suite that is optional. Each file is a TAR archive that is
687compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000688</p>
689
Misha Brukman3ce11032005-02-02 18:01:57 +0000690<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000691<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000692 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000693 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000694
Misha Brukman3ce11032005-02-02 18:01:57 +0000695 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000696 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000697
Misha Brukmanccd02952008-12-29 19:38:58 +0000698 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
699 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000700 directory for build instructions.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000701
Misha Brukmanccd02952008-12-29 19:38:58 +0000702 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
703 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000704
Misha Brukman00c73d22003-11-07 19:43:14 +0000705</dl>
706
707</div>
708
709<!-- ======================================================================= -->
710<div class="doc_subsection">
John Criswell9c29bfb2007-06-29 19:12:31 +0000711 <a name="checkout">Checkout LLVM from Subversion</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000712</div>
713
714<div class="doc_text">
715
John Criswell9c29bfb2007-06-29 19:12:31 +0000716<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000717the entire source code. All you need to do is check it out from Subversion as
Misha Brukman00c73d22003-11-07 19:43:14 +0000718follows:</p>
719
720<ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000721 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov98044e42007-06-29 20:56:49 +0000722 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
723 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell9c29bfb2007-06-29 19:12:31 +0000724 llvm</tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000725</ul>
726
John Criswell9c29bfb2007-06-29 19:12:31 +0000727
Misha Brukman00c73d22003-11-07 19:43:14 +0000728<p>This will create an '<tt>llvm</tt>' directory in the current
729directory and fully populate it with the LLVM source code, Makefiles,
730test directories, and local copies of documentation files.</p>
731
Misha Brukman54111c42004-01-20 00:20:17 +0000732<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikovd933fa92007-06-29 23:13:42 +0000733revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikovd724dc82007-06-30 00:00:57 +0000734'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman9474d012008-12-17 16:27:23 +0000735subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000736
John Criswelld000e1d2003-12-18 16:43:17 +0000737<ul>
Bill Wendlingc44c2452010-10-06 23:50:30 +0000738<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner994526c2010-10-06 05:36:01 +0000739<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattnerf08803b2009-10-23 06:20:06 +0000740<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000741<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman9474d012008-12-17 16:27:23 +0000742<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattnerb37ef512008-06-09 06:02:09 +0000743<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattnerdd50f0f2008-02-12 02:42:55 +0000744<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner76385652007-09-28 22:50:54 +0000745<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattner1dcadec2007-05-22 06:06:22 +0000746<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner134693a2006-11-20 06:07:10 +0000747<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000748<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattner993b9802006-04-20 04:35:34 +0000749<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000750<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000751<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000752<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000753<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000754<li>Release 1.2: <b>RELEASE_12</b></li>
755<li>Release 1.1: <b>RELEASE_11</b></li>
756<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000757</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000758
Reid Spencer66db92e2004-12-08 16:51:31 +0000759<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell9c29bfb2007-06-29 19:12:31 +0000760you get it from the Subversion repository:</p>
Bill Wendling77f74692007-07-16 08:44:39 +0000761
762<div class="doc_code">
Reid Spencer66db92e2004-12-08 16:51:31 +0000763<pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000764% cd llvm/projects
Andrew Trickbcf01162010-09-23 20:26:44 +0000765% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencer66db92e2004-12-08 16:51:31 +0000766</pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000767</div>
768
Reid Spencer66db92e2004-12-08 16:51:31 +0000769<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000770configured by the LLVM configure script as well as automatically updated when
John Criswell9c29bfb2007-06-29 19:12:31 +0000771you run <tt>svn update</tt>.</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000772
Chris Lattner82ad9f12007-03-06 06:27:34 +0000773<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands8655b152008-02-14 17:53:22 +0000774and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner82ad9f12007-03-06 06:27:34 +0000775instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000776
Misha Brukman00c73d22003-11-07 19:43:14 +0000777</div>
778
779<!-- ======================================================================= -->
780<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000781 <a name="installcf">Install the GCC Front End</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000782</div>
783
784<div class="doc_text">
785
Jim Grosbach18df1d42009-12-17 17:18:11 +0000786<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
787GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trickbcf01162010-09-23 20:26:44 +0000788It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach18df1d42009-12-17 17:18:11 +0000789you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000790main LLVM repository.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000791
Jim Grosbach18df1d42009-12-17 17:18:11 +0000792<p>To install the GCC front end, do the following (on Windows, use an archival tool
793like <a href="http://www.7-zip.org">7-zip</a> that understands gzipped tars):</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000794
795<ol>
796 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukmanccd02952008-12-29 19:38:58 +0000797 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman00c73d22003-11-07 19:43:14 +0000798 -</tt></li>
799</ol>
800
Jim Grosbach18df1d42009-12-17 17:18:11 +0000801<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
802<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
803Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
804to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
805<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
806
807<p>If you now want to build LLVM from source, when you configure LLVM, it will
808automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trickbcf01162010-09-23 20:26:44 +0000809use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach18df1d42009-12-17 17:18:11 +0000810point after building the main LLVM repository: just reconfigure llvm and
Andrew Trickbcf01162010-09-23 20:26:44 +0000811test-suite will pick it up.
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000812</p>
813
Jim Grosbach18df1d42009-12-17 17:18:11 +0000814<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
815versions of the required w32api and mingw-runtime binaries. The last remaining step for
816Windows users is to simply uncompress the binary binutils package from
817<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
818front end installation steps are not quite the same as a typical manual MinGW installation,
819they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000820
Jim Grosbach18df1d42009-12-17 17:18:11 +0000821<p>To install binutils on Windows:</p>
822
823<ol>
824 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
825 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
826 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
827</ol>
828
829<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
830example, the binary distribution may include an old version of a system header
831file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
832libraries not available on your system. In cases like these, you may want to try
833<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
834this is much easier now than it was in the past.</p>
835
836<p>We also do not currently support updating of the GCC front end by manually overlaying
837newer versions of the w32api and mingw-runtime binary packages that may become available
838from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
839a self-contained convenience package that requires Windows users to simply download and
840uncompress the GNU Binutils binary package from the MinGW project.</p>
841
842<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
843binaries is not as easy as previously described, or you would like to suggest improvements,
844please let us know how you would like to see things improved by dropping us a note on our
845<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000846
847</div>
848
849<!-- ======================================================================= -->
850<div class="doc_subsection">
851 <a name="config">Local LLVM Configuration</a>
852</div>
853
854<div class="doc_text">
855
John Criswell9c29bfb2007-06-29 19:12:31 +0000856 <p>Once checked out from the Subversion repository, the LLVM suite source
857 code must be
Reid Spencer66db92e2004-12-08 16:51:31 +0000858configured via the <tt>configure</tt> script. This script sets variables in the
859various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
860<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
861the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000862
863<p>The following environment variables are used by the <tt>configure</tt>
864script to configure the build system:</p>
865
Chris Lattner9abd8af2006-09-07 04:19:09 +0000866<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +0000867 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000868 <tr>
869 <td>CC</td>
870 <td>Tells <tt>configure</tt> which C compiler to use. By default,
871 <tt>configure</tt> will look for the first GCC C compiler in
872 <tt>PATH</tt>. Use this variable to override
873 <tt>configure</tt>'s default behavior.</td>
874 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000875 <tr>
876 <td>CXX</td>
877 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
878 <tt>configure</tt> will look for the first GCC C++ compiler in
879 <tt>PATH</tt>. Use this variable to override
880 <tt>configure</tt>'s default behavior.</td>
881 </tr>
882</table>
883
884<p>The following options can be used to set or enable LLVM specific options:</p>
885
Misha Brukman54111c42004-01-20 00:20:17 +0000886<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +0000887 <dt><i>--with-llvmgccdir</i></dt>
888 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
889 The value of this option should specify the full pathname of the C/C++ Front
890 End to be used. If this option is not provided, the PATH will be searched for
891 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
892 be inferred from the path found. If the option is not given, and no llvm-gcc
893 can be found in the path then a warning will be produced by
894 <tt>configure</tt> indicating this situation. LLVM may still be built with
895 the <tt>tools-only</tt> target but attempting to build the runtime libraries
896 will fail as these libraries require llvm-gcc and llvm-g++. See
897 <a href="#installcf">Install the GCC Front End</a> for details on installing
898 the C/C++ Front End. See
Duncan Sands8655b152008-02-14 17:53:22 +0000899 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencerfef93b72004-12-26 05:47:26 +0000900 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000901 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +0000902 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +0000903 found. Use this if you have multiple tcl installations on your machine and you
904 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
905 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +0000906 option, the LLVM configure script will search for the tcl 8.4 and 8.3
907 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000908 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000909 </dd>
910 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000911 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000912 Enables optimized compilation (debugging symbols are removed
913 and GCC optimization flags are enabled). Note that this is the default
914 setting if you are using the LLVM distribution. The default behavior
915 of an Subversion checkout is to use an unoptimized build (also known as a
916 debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000917 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000918 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +0000919 <dt><i>--enable-debug-runtime</i></dt>
920 <dd>
921 Enables debug symbols in the runtime libraries. The default is to strip
922 debug symbols from the runtime libraries.
923 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000924 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000925 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +0000926 Compile the Just In Time (JIT) compiler functionality. This is not
927 available
Misha Brukman00c73d22003-11-07 19:43:14 +0000928 on all platforms. The default is dependent on platform, so it is best
929 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000930 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000931 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000932 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
933 <dd>Controls which targets will be built and linked into llc. The default
934 value for <tt>target_options</tt> is "all" which builds and links all
935 available targets. The value "host-only" can be specified to build only a
936 native compiler (no cross-compiler targets available). The "native" target is
937 selected as the target of the build host. You can also specify a comma
938 separated list of target names that you want available in llc. The target
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000939 names use all lower case. The current set of targets is: <br>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000940 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000941 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000942 <dt><i>--enable-doxygen</i></dt>
943 <dd>Look for the doxygen program and enable construction of doxygen based
944 documentation from the source code. This is disabled by default because
945 generating the documentation can take a long time and producess 100s of
946 megabytes of output.</dd>
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +0000947 <dt><i>--with-udis86</i></dt>
948 <dd>LLVM can use external disassembler library for various purposes (now it's
949 used only for examining code produced by JIT). This option will enable usage
950 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
951 bits) disassembler library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000952</dl>
953
954<p>To configure LLVM, follow these steps:</p>
955
956<ol>
Bill Wendling77f74692007-07-16 08:44:39 +0000957 <li><p>Change directory into the object root directory:</p>
John Criswell0f6d7c02003-10-27 18:18:16 +0000958
Bill Wendling77f74692007-07-16 08:44:39 +0000959 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
960
961 <li><p>Run the <tt>configure</tt> script located in the LLVM source
962 tree:</p>
963
964 <div class="doc_code">
965 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
966 </div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000967</ol>
John Criswell85ed3612003-06-12 19:34:44 +0000968
Misha Brukman00c73d22003-11-07 19:43:14 +0000969</div>
John Criswell85ed3612003-06-12 19:34:44 +0000970
Misha Brukman00c73d22003-11-07 19:43:14 +0000971<!-- ======================================================================= -->
972<div class="doc_subsection">
973 <a name="compile">Compiling the LLVM Suite Source Code</a>
974</div>
John Criswell85ed3612003-06-12 19:34:44 +0000975
Misha Brukman00c73d22003-11-07 19:43:14 +0000976<div class="doc_text">
John Criswell0b459202003-07-08 20:35:59 +0000977
Misha Brukman00c73d22003-11-07 19:43:14 +0000978<p>Once you have configured LLVM, you can build it. There are three types of
979builds:</p>
John Criswell0b459202003-07-08 20:35:59 +0000980
Misha Brukman54111c42004-01-20 00:20:17 +0000981<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000982 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +0000983 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000984 These builds are the default when one is using an Subversion checkout and
985 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
986 used during configuration). The build system will compile the tools and
987 libraries with debugging information. To get a Debug Build using the
988 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
989 to <tt>configure</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000990 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000991
992 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +0000993 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000994 These builds are enabled with the <tt>--enable-optimized</tt> option to
995 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
996 <tt>gmake</tt> command line. For these builds, the build system will
997 compile the tools and libraries with GCC optimizations enabled and strip
998 debugging information from the libraries and executables it generates.
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000999 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001000 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001001
1002 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +00001003 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001004 These builds are for use with profiling. They compile profiling
1005 information into the code for use with programs like <tt>gprof</tt>.
1006 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1007 on the <tt>gmake</tt> command line.
1008</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001009
Misha Brukman00c73d22003-11-07 19:43:14 +00001010<p>Once you have LLVM configured, you can build it by entering the
1011<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001012
Bill Wendling77f74692007-07-16 08:44:39 +00001013<div class="doc_code"><pre>% gmake</pre></div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001014
Chris Lattner95e92582004-07-18 22:32:22 +00001015<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +00001016are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +00001017
1018<p>
1019If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +00001020the parallel build options provided by GNU Make. For example, you could use the
1021command:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001022
Bill Wendling77f74692007-07-16 08:44:39 +00001023<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellce760f62003-07-03 16:01:38 +00001024
Misha Brukman00c73d22003-11-07 19:43:14 +00001025<p>There are several special targets which are useful when working with the LLVM
1026source code:</p>
John Criswellce760f62003-07-03 16:01:38 +00001027
Misha Brukman54111c42004-01-20 00:20:17 +00001028<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001029 <dt><tt>gmake clean</tt>
1030 <dd>
1031 Removes all files generated by the build. This includes object files,
1032 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001033 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001034
Reid Spencer66db92e2004-12-08 16:51:31 +00001035 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001036 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +00001037 Removes everything that <tt>gmake clean</tt> does, but also removes files
1038 generated by <tt>configure</tt>. It attempts to return the source tree to the
1039 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001040 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001041
Misha Brukmane51c3562004-08-23 20:25:33 +00001042 <dt><tt>gmake install</tt>
1043 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +00001044 Installs LLVM header files, libraries, tools, and documentation in a
1045 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +00001046 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1047 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001048 <br><br>
1049
Reid Spencer66db92e2004-12-08 16:51:31 +00001050 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001051 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +00001052 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greif04367bf2007-07-06 22:07:22 +00001053 install bitcode libraries into the GCC front end's bitcode library
1054 directory. If you need to update your bitcode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +00001055 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001056 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001057</dl>
John Criswellce760f62003-07-03 16:01:38 +00001058
Reid Spencer66db92e2004-12-08 16:51:31 +00001059<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1060details on these <tt>make</tt> targets and descriptions of other targets
1061available.</p>
1062
Misha Brukman00c73d22003-11-07 19:43:14 +00001063<p>It is also possible to override default values from <tt>configure</tt> by
1064declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +00001065
Misha Brukman54111c42004-01-20 00:20:17 +00001066<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001067 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1068 <dd>
1069 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001070 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001071
Reid Spencer004ba032006-04-09 23:45:38 +00001072 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +00001073 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +00001074 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001075 <br><br>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001076
1077 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1078 <dd>
1079 Perform a Debug build.
1080 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +00001081
Misha Brukman00c73d22003-11-07 19:43:14 +00001082 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1083 <dd>
1084 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001085 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001086
Misha Brukman00c73d22003-11-07 19:43:14 +00001087 <dt><tt>gmake VERBOSE=1</tt>
1088 <dd>
1089 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001090 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001091
1092 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1093 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +00001094 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001095 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001096</dl>
John Criswellce760f62003-07-03 16:01:38 +00001097
Misha Brukman00c73d22003-11-07 19:43:14 +00001098<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1099it and any subdirectories that it contains. Entering any directory inside the
1100LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1101that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +00001102
Misha Brukman00c73d22003-11-07 19:43:14 +00001103</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001104
Misha Brukman00c73d22003-11-07 19:43:14 +00001105<!-- ======================================================================= -->
1106<div class="doc_subsection">
Reid Spencerd30a9712006-07-27 06:41:31 +00001107 <a name="cross-compile">Cross-Compiling LLVM</a>
Reid Spencer17850ef2006-07-27 05:43:30 +00001108</div>
1109
1110<div class="doc_text">
Jim Grosbach5bea8222009-04-17 17:25:16 +00001111 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1112 executables and libraries to be hosted on a platform different from the
1113 platform where they are build (a Canadian Cross build). To configure a
1114 cross-compile, supply the configure script with <tt>--build</tt> and
1115 <tt>--host</tt> options that are different. The values of these options must
1116 be legal target triples that your GCC compiler supports.</p>
1117
1118 <p>The result of such a build is executables that are not runnable on
1119 on the build host (--build option) but can be executed on the compile host
Reid Spencerd30a9712006-07-27 06:41:31 +00001120 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001121</div>
1122
1123<!-- ======================================================================= -->
1124<div class="doc_subsection">
Misha Brukman00c73d22003-11-07 19:43:14 +00001125 <a name="objfiles">The Location of LLVM Object Files</a>
1126</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001127
Misha Brukman00c73d22003-11-07 19:43:14 +00001128<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001129
Misha Brukman00c73d22003-11-07 19:43:14 +00001130<p>The LLVM build system is capable of sharing a single LLVM source tree among
1131several LLVM builds. Hence, it is possible to build LLVM for several different
1132platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001133
Misha Brukman00c73d22003-11-07 19:43:14 +00001134<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001135
Misha Brukman00c73d22003-11-07 19:43:14 +00001136<ul>
1137 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001138
Bill Wendling77f74692007-07-16 08:44:39 +00001139 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellce760f62003-07-03 16:01:38 +00001140
Misha Brukman00c73d22003-11-07 19:43:14 +00001141 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1142 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001143
Bill Wendling77f74692007-07-16 08:44:39 +00001144 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001145</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001146
Misha Brukman00c73d22003-11-07 19:43:14 +00001147<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1148named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001149
Misha Brukman54111c42004-01-20 00:20:17 +00001150<dl>
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001151 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman00c73d22003-11-07 19:43:14 +00001152 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001153 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001154 <dt>Tools
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001155 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001156 <dt>Libraries
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001157 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001158 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001159 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001160
Misha Brukman00c73d22003-11-07 19:43:14 +00001161 <dt>Release Builds
1162 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001163 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001164 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001165 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001166 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001167 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001168 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001169 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001170
Misha Brukman00c73d22003-11-07 19:43:14 +00001171 <dt>Profile Builds
1172 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001173 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001174 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001175 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001176 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001177 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001178 </dl>
1179</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001180
Misha Brukman00c73d22003-11-07 19:43:14 +00001181</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001182
Chris Lattnera553f622004-03-25 20:38:40 +00001183<!-- ======================================================================= -->
1184<div class="doc_subsection">
1185 <a name="optionalconfig">Optional Configuration Items</a>
1186</div>
1187
1188<div class="doc_text">
1189
1190<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001191If you're running on a Linux system that supports the "<a
Bill Wendling22e37c32007-07-16 08:46:40 +00001192href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001193module, and you have root access on the system, you can set your system up to
Bill Wendling22e37c32007-07-16 08:46:40 +00001194execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattnera553f622004-03-25 20:38:40 +00001195first command may not be required if you are already using the module):</p>
1196
Misha Brukman9106eca2005-02-03 22:25:23 +00001197<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001198<pre>
Bill Wendling77f74692007-07-16 08:44:39 +00001199$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckye6b5a522009-11-04 06:15:28 +00001200$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendling77f74692007-07-16 08:44:39 +00001201$ chmod u+x hello.bc (if needed)
1202$ ./hello.bc
Chris Lattnera553f622004-03-25 20:38:40 +00001203</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001204</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001205
1206<p>
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001207This allows you to execute LLVM bitcode files directly. On Debian, you
1208can also use this command instead of the 'echo' command above:</p>
Chris Lattnera553f622004-03-25 20:38:40 +00001209</p>
1210
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001211<div class="doc_code">
1212<pre>
1213$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1214</pre>
1215</div>
1216
Chris Lattnera553f622004-03-25 20:38:40 +00001217</div>
1218
Misha Brukman00c73d22003-11-07 19:43:14 +00001219<!-- *********************************************************************** -->
1220<div class="doc_section">
1221 <a name="layout"><b>Program Layout</b></a>
1222</div>
1223<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001224
Misha Brukman00c73d22003-11-07 19:43:14 +00001225<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001226
Misha Brukman00c73d22003-11-07 19:43:14 +00001227<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell364cec42004-03-12 20:31:37 +00001228href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001229href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001230The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001231
Misha Brukman00c73d22003-11-07 19:43:14 +00001232</div>
John Criswell85ed3612003-06-12 19:34:44 +00001233
Misha Brukman00c73d22003-11-07 19:43:14 +00001234<!-- ======================================================================= -->
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001235<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1236<div class="doc_text">
1237 <p>This directory contains some simple examples of how to use the LLVM IR and
1238 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001239</div>
John Criswell85ed3612003-06-12 19:34:44 +00001240
Misha Brukman00c73d22003-11-07 19:43:14 +00001241<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001242<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001243<div class="doc_text">
1244
1245<p>This directory contains public header files exported from the LLVM
1246library. The three main subdirectories of this directory are:</p>
1247
Reid Spencer77d90192004-09-05 20:50:22 +00001248<dl>
1249 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1250 <dd>This directory contains all of the LLVM specific header files. This
1251 directory also has subdirectories for different portions of LLVM:
1252 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1253 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001254
Reid Spencer77d90192004-09-05 20:50:22 +00001255 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1256 <dd>This directory contains generic support libraries that are provided with
1257 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1258 and a Command Line option processing library store their header files here.
1259 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001260
Reid Spencer77d90192004-09-05 20:50:22 +00001261 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1262 <dd>This directory contains header files configured by the <tt>configure</tt>
1263 script. They wrap "standard" UNIX and C header files. Source code can
1264 include these header files which automatically take care of the conditional
1265 #includes that the <tt>configure</tt> script generates.</dd>
1266</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001267</div>
1268
1269<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001270<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001271<div class="doc_text">
1272
1273<p>This directory contains most of the source files of the LLVM system. In LLVM,
1274almost all code exists in libraries, making it very easy to share code among the
1275different <a href="#tools">tools</a>.</p>
1276
Misha Brukman54111c42004-01-20 00:20:17 +00001277<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001278 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1279 <dd> This directory holds the core LLVM source files that implement core
1280 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001281
Reid Spencer77d90192004-09-05 20:50:22 +00001282 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1283 <dd>This directory holds the source code for the LLVM assembly language parser
1284 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001285
Gabor Greif04367bf2007-07-06 22:07:22 +00001286 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1287 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001288
Reid Spencer77d90192004-09-05 20:50:22 +00001289 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001290 different program analyses, such as Dominator Information, Call Graphs,
1291 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001292 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001293
Reid Spencer77d90192004-09-05 20:50:22 +00001294 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1295 <dd> This directory contains the source code for the LLVM to LLVM program
1296 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1297 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1298 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001299
Reid Spencer77d90192004-09-05 20:50:22 +00001300 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1301 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001302 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1303 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001304 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001305
Reid Spencer77d90192004-09-05 20:50:22 +00001306 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1307 <dd> This directory contains the major parts of the code generator: Instruction
1308 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001309
Reid Spencer77d90192004-09-05 20:50:22 +00001310 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1311 <dd> This directory contains the source level debugger library that makes
1312 it possible to instrument LLVM programs so that a debugger could identify
1313 source code locations at which the program is executing.</dd>
1314
1315 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001316 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer77d90192004-09-05 20:50:22 +00001317 at runtime in both interpreted and JIT compiled fashions.</dd>
1318
1319 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1320 <dd> This directory contains the source code that corresponds to the header
1321 files located in <tt>llvm/include/Support/</tt>.</dd>
1322
1323 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1324 <dd>This directory contains the operating system abstraction layer that
1325 shields LLVM from platform-specific coding.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001326</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001327
Misha Brukman00c73d22003-11-07 19:43:14 +00001328</div>
John Criswell85ed3612003-06-12 19:34:44 +00001329
Misha Brukman00c73d22003-11-07 19:43:14 +00001330<!-- ======================================================================= -->
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001331<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1332<div class="doc_text">
1333 <p>This directory contains projects that are not strictly part of LLVM but are
1334 shipped with LLVM. This is also the directory where you should create your own
1335 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner4630e4d2008-08-11 06:13:31 +00001336 to set up your own project.</p>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001337</div>
1338
1339<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001340<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001341<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001342
Gabor Greif04367bf2007-07-06 22:07:22 +00001343<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman00c73d22003-11-07 19:43:14 +00001344used when linking programs with the GCC front end. Most of these libraries are
1345skeleton versions of real libraries; for example, libc is a stripped down
1346version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001347
Misha Brukman00c73d22003-11-07 19:43:14 +00001348<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1349end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001350
Misha Brukman00c73d22003-11-07 19:43:14 +00001351</div>
John Criswell85ed3612003-06-12 19:34:44 +00001352
Misha Brukman00c73d22003-11-07 19:43:14 +00001353<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001354<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001355<div class="doc_text">
Reid Spencer77d90192004-09-05 20:50:22 +00001356 <p>This directory contains feature and regression tests and other basic sanity
1357 checks on the LLVM infrastructure. These are intended to run quickly and cover
1358 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001359</div>
John Criswell85ed3612003-06-12 19:34:44 +00001360
Misha Brukman00c73d22003-11-07 19:43:14 +00001361<!-- ======================================================================= -->
Andrew Trickbcf01162010-09-23 20:26:44 +00001362<div class="doc_subsection"><a name="test-suite"><tt>test-suite</tt></a></div>
Reid Spencer77d90192004-09-05 20:50:22 +00001363<div class="doc_text">
John Criswell9c29bfb2007-06-29 19:12:31 +00001364 <p>This is not a directory in the normal llvm module; it is a separate
1365 Subversion
1366 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1367 This
John Criswell3d8ba512004-12-08 17:53:54 +00001368 module contains a comprehensive correctness, performance, and benchmarking
1369 test
John Criswell9c29bfb2007-06-29 19:12:31 +00001370 suite for LLVM. It is a separate Subversion module because not every LLVM
1371 user is
John Criswell838bce52005-05-09 16:39:27 +00001372 interested in downloading or building such a comprehensive test suite. For
1373 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001374 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001375</div>
John Criswell85ed3612003-06-12 19:34:44 +00001376
Reid Spencer77d90192004-09-05 20:50:22 +00001377<!-- ======================================================================= -->
1378<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001379<div class="doc_text">
John Criswell20d2d3e2003-10-10 14:26:14 +00001380
Misha Brukman00c73d22003-11-07 19:43:14 +00001381<p>The <b>tools</b> directory contains the executables built out of the
1382libraries above, which form the main part of the user interface. You can
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001383always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001384following is a brief introduction to the most important tools. More detailed
1385information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001386
Misha Brukman54111c42004-01-20 00:20:17 +00001387<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001388
Reid Spencer77d90192004-09-05 20:50:22 +00001389 <dt><tt><b>bugpoint</b></tt></dt>
1390 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001391 optimization passes or code generation backends by narrowing down the
1392 given test case to the minimum number of passes and/or instructions that
1393 still cause a problem, whether it is a crash or miscompilation. See <a
1394 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001395 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001396
Reid Spencer77d90192004-09-05 20:50:22 +00001397 <dt><tt><b>llvmc</b></tt></dt>
1398 <dd>The LLVM Compiler Driver. This program can
1399 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1400 pre-processing, translation, optimization, assembly, and linking of programs
1401 all from one command line. <tt>llvmc</tt> also takes care of processing the
Gabor Greif04367bf2007-07-06 22:07:22 +00001402 dependent libraries found in bitcode. This reduces the need to get the
Reid Spencer079e9452004-12-08 18:00:30 +00001403 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswell8bfe6a72005-05-18 19:43:33 +00001404 note that this tool, while functional, is still experimental and not feature
1405 complete.</dd>
Reid Spencer77d90192004-09-05 20:50:22 +00001406
1407 <dt><tt><b>llvm-ar</b></tt></dt>
1408 <dd>The archiver produces an archive containing
Gabor Greif04367bf2007-07-06 22:07:22 +00001409 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001410 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001411
Reid Spencer77d90192004-09-05 20:50:22 +00001412 <dt><tt><b>llvm-as</b></tt></dt>
1413 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001414 bitcode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001415
Reid Spencer77d90192004-09-05 20:50:22 +00001416 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001417 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer77d90192004-09-05 20:50:22 +00001418 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001419
Reid Spencer079e9452004-12-08 18:00:30 +00001420 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001421 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Andrew Trickbcf01162010-09-23 20:26:44 +00001422 This is the linker invoked by <tt>llvmc</tt>. It performs standard link time
Reid Spencer434262a2007-02-09 15:59:08 +00001423 optimizations and allows optimization modules to be loaded and run so that
1424 language specific optimizations can be applied at link time.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001425
Reid Spencer77d90192004-09-05 20:50:22 +00001426 <dt><tt><b>llvm-link</b></tt></dt>
1427 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1428 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001429
Reid Spencer77d90192004-09-05 20:50:22 +00001430 <dt><tt><b>lli</b></tt></dt>
1431 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky64270d52007-12-03 01:58:01 +00001432 can directly execute LLVM bitcode (although very slowly...). For architectures
1433 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1434 will function as a Just-In-Time compiler (if the functionality was compiled
1435 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001436
Reid Spencer77d90192004-09-05 20:50:22 +00001437 <dt><tt><b>llc</b></tt></dt>
1438 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greif04367bf2007-07-06 22:07:22 +00001439 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001440 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001441
Reid Spencerd4694f92004-12-22 06:29:07 +00001442 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001443 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1444 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001445 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencer434262a2007-02-09 15:59:08 +00001446 usual machine code output. It works just like any other GCC compiler,
1447 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1448 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell9c29bfb2007-06-29 19:12:31 +00001449 separate Subversion module.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001450
Reid Spencer77d90192004-09-05 20:50:22 +00001451 <dt><tt><b>opt</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001452 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer84f82f72006-08-28 00:34:19 +00001453 transformations (which are specified on the command line), and then outputs
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001454 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001455 get a list of the program transformations available in LLVM.<br>
Reid Spencer84f82f72006-08-28 00:34:19 +00001456 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greif04367bf2007-07-06 22:07:22 +00001457 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer84f82f72006-08-28 00:34:19 +00001458 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001459</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001460</div>
John Criswell85ed3612003-06-12 19:34:44 +00001461
Misha Brukman00c73d22003-11-07 19:43:14 +00001462<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001463<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001464<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001465
Misha Brukman00c73d22003-11-07 19:43:14 +00001466<p>This directory contains utilities for working with LLVM source code, and some
1467of the utilities are actually required as part of the build process because they
1468are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001469
Misha Brukman54111c42004-01-20 00:20:17 +00001470<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001471 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001472 that finds differences between code that LLC generates and code that LLI
1473 generates. This is a useful tool if you are debugging one of them,
1474 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001475 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001476
Misha Brukman54111c42004-01-20 00:20:17 +00001477 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001478 syntax-highlighting files which will work with Emacs and XEmacs editors,
1479 providing syntax highlighting support for LLVM assembly files and TableGen
1480 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001481 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001482
Misha Brukman54111c42004-01-20 00:20:17 +00001483 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001484 and outputs all non-generated source files, which is useful if one wishes
1485 to do a lot of development across directories and does not want to
1486 individually find each file. One way to use it is to run, for example:
1487 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001488 tree.<br><br>
1489
Reid Spencer77d90192004-09-05 20:50:22 +00001490 <dt><tt><b>llvmgrep</b></tt></dt>
1491 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1492 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1493 line. This is a very efficient way of searching the source base for a
1494 particular regular expression.</dd>
1495
Misha Brukman54111c42004-01-20 00:20:17 +00001496 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001497 files in the current directory and then compiles and links the tool that
1498 is the first argument. For example, assuming you are in the directory
1499 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1500 simply running <tt>makellvm llc</tt> will make a build of the current
1501 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001502 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001503
Tanya Lattner7a857dd2007-05-22 06:12:51 +00001504 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukman54111c42004-01-20 00:20:17 +00001505 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman00c73d22003-11-07 19:43:14 +00001506 cron script to generate nightly status reports of the functionality of
1507 tools, and the results can be seen by following the appropriate link on
Chris Lattner9abd8af2006-09-07 04:19:09 +00001508 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001509
Misha Brukman54111c42004-01-20 00:20:17 +00001510 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001511 the tool used to generate register descriptions, instruction set
1512 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001513 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001514
Misha Brukman54111c42004-01-20 00:20:17 +00001515 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001516 syntax-highlighting files which will work with the VIM editor, providing
1517 syntax highlighting support for LLVM assembly files and TableGen
1518 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001519 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001520
Misha Brukman00c73d22003-11-07 19:43:14 +00001521</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001522
Misha Brukman00c73d22003-11-07 19:43:14 +00001523</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001524
Misha Brukman00c73d22003-11-07 19:43:14 +00001525<!-- *********************************************************************** -->
1526<div class="doc_section">
1527 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1528</div>
1529<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001530
Misha Brukman00c73d22003-11-07 19:43:14 +00001531<div class="doc_text">
Chris Lattner59075882007-01-04 07:08:27 +00001532<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
Chris Lattnerb357f042009-04-10 15:38:51 +00001533so we only include instructions for llvm-gcc4.
Chris Lattner5907d402006-08-14 20:45:25 +00001534</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001535
1536<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1537from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
Gabor Greif04367bf2007-07-06 22:07:22 +00001538create bitcode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1539the '--emit-llvm' flag is needed to produce LLVM bitcode output. For <i>makefiles</i> and
1540<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bitcode
Chris Lattner9abd8af2006-09-07 04:19:09 +00001541output.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001542</div>
1543
1544<!-- ======================================================================= -->
Chris Lattner9abd8af2006-09-07 04:19:09 +00001545<div class="doc_subsection"><a name="tutorial4">Example with llvm-gcc4</a></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001546
1547<div class="doc_text">
1548
1549<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001550 <li><p>First, create a simple C file, name it 'hello.c':</p>
1551
1552<div class="doc_code">
1553<pre>
1554#include &lt;stdio.h&gt;
1555
1556int main() {
1557 printf("hello world\n");
1558 return 0;
1559}
1560</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001561
1562 <li><p>Next, compile the C file into a native executable:</p>
1563
Bill Wendling77f74692007-07-16 08:44:39 +00001564 <div class="doc_code"><pre>% llvm-gcc hello.c -o hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001565
1566 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1567 -c arguments work as usual (producing a native .s or .o file,
Bill Wendling77f74692007-07-16 08:44:39 +00001568 respectively).</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001569
Gabor Greif04367bf2007-07-06 22:07:22 +00001570 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendling77f74692007-07-16 08:44:39 +00001571
1572 <div class="doc_code">
1573 <pre>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001574
1575 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1576 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1577 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Gabor Greif04367bf2007-07-06 22:07:22 +00001578 the bitcode file.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001579
1580 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1581 </p></li>
1582
1583 <li><p>Run the program in both forms. To run the program, use:</p>
1584
Bill Wendling77f74692007-07-16 08:44:39 +00001585 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001586
1587 <p>and</p>
1588
Bill Wendling77f74692007-07-16 08:44:39 +00001589 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001590
1591 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001592 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001593
1594 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1595 code:</p>
1596
Bill Wendling77f74692007-07-16 08:44:39 +00001597<div class="doc_code">
1598<pre>llvm-dis &lt; hello.bc | less</pre>
1599</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001600
1601 <li><p>Compile the program to native assembly using the LLC code
1602 generator:</p>
1603
Bill Wendling77f74692007-07-16 08:44:39 +00001604 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001605
1606 <li><p>Assemble the native assembly language file into a program:</p>
1607
Bill Wendling77f74692007-07-16 08:44:39 +00001608<div class="doc_code">
1609<pre>
1610<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1611
1612<b>Others:</b> % gcc hello.s -o hello.native
1613</pre>
1614</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001615
1616 <li><p>Execute the native code program:</p>
1617
Bill Wendling77f74692007-07-16 08:44:39 +00001618 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001619
1620 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1621 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001622 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001623
1624</ol>
1625
1626</div>
1627
John Criswell85ed3612003-06-12 19:34:44 +00001628
Misha Brukman00c73d22003-11-07 19:43:14 +00001629<!-- *********************************************************************** -->
1630<div class="doc_section">
1631 <a name="problems">Common Problems</a>
1632</div>
1633<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001634
Misha Brukman00c73d22003-11-07 19:43:14 +00001635<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001636
Misha Brukman00c73d22003-11-07 19:43:14 +00001637<p>If you are having problems building or using LLVM, or if you have any other
1638general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1639Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001640
Misha Brukman00c73d22003-11-07 19:43:14 +00001641</div>
John Criswell85ed3612003-06-12 19:34:44 +00001642
Misha Brukman00c73d22003-11-07 19:43:14 +00001643<!-- *********************************************************************** -->
1644<div class="doc_section">
1645 <a name="links">Links</a>
1646</div>
1647<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001648
Misha Brukman00c73d22003-11-07 19:43:14 +00001649<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001650
Bill Wendling2d4c2152008-07-22 01:10:25 +00001651<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman00c73d22003-11-07 19:43:14 +00001652some simple things... there are many more interesting and complicated things
1653that you can do that aren't documented here (but we'll gladly accept a patch
1654if you want to write something up!). For more information about LLVM, check
1655out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001656
Misha Brukman00c73d22003-11-07 19:43:14 +00001657<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001658 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1659 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1660 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001661 that Uses LLVM</a></li>
1662</ul>
1663
1664</div>
1665
1666<!-- *********************************************************************** -->
1667
1668<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001669<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001670 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001671 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001672 <a href="http://validator.w3.org/check/referer"><img
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001673 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001674
Misha Brukman142207b2003-11-22 01:30:01 +00001675 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001676 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001677 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001678 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001679</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001680</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001681</html>