blob: d062f25ef218320736e99e92990687330f0780d4 [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>
Misha Brukman00c73d22003-11-07 19:43:14 +000020 <li><a href="#hardware">Hardware</a>
21 <li><a href="#software">Software</a>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +000022 <li><a href="#brokengcc">Broken versions of GCC and other tools</a>
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>
Misha Brukman00c73d22003-11-07 19:43:14 +000027 <li><a href="#terminology">Terminology and Notation</a>
28 <li><a href="#environment">Setting Up Your Environment</a>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a>
John Criswell9c29bfb2007-06-29 19:12:31 +000030 <li><a href="#checkout">Checkout LLVM from Subversion</a>
Misha Brukman00c73d22003-11-07 19:43:14 +000031 <li><a href="#installcf">Install the GCC Front End</a>
32 <li><a href="#config">Local LLVM Configuration</a>
33 <li><a href="#compile">Compiling the LLVM Suite Source Code</a>
Reid Spencerd30a9712006-07-27 06:41:31 +000034 <li><a href="#cross-compile">Cross-Compiling LLVM</a>
Misha Brukman00c73d22003-11-07 19:43:14 +000035 <li><a href="#objfiles">The Location of LLVM Object Files</a>
Chris Lattnera553f622004-03-25 20:38:40 +000036 <li><a href="#optionalconfig">Optional Configuration Items</a>
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>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000041 <li><a href="#examples"><tt>llvm/examples</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000042 <li><a href="#include"><tt>llvm/include</tt></a>
43 <li><a href="#lib"><tt>llvm/lib</tt></a>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000044 <li><a href="#projects"><tt>llvm/projects</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000045 <li><a href="#runtime"><tt>llvm/runtime</tt></a>
46 <li><a href="#test"><tt>llvm/test</tt></a>
Reid Spencer77d90192004-09-05 20:50:22 +000047 <li><a href="#llvmtest"><tt>llvm-test</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000048 <li><a href="#tools"><tt>llvm/tools</tt></a>
49 <li><a href="#utils"><tt>llvm/utils</tt></a>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000050 <li><a href="#win32"><tt>llvm/win32</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000051 </ol></li>
John Criswell0f6d7c02003-10-27 18:18:16 +000052
Misha Brukman00c73d22003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner9abd8af2006-09-07 04:19:09 +000054 <ol>
55 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner9abd8af2006-09-07 04:19:09 +000056 </ol>
Misha Brukman00c73d22003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner7911ce22004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
65 <a href="http://misha.brukman.net">Misha Brukman</a>,
66 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
67 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
68 </p>
69</div>
Misha Brukman00c73d22003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
73<div class="doc_section">
74 <a name="overview"><b>Overview</b></a>
75</div>
76<!-- *********************************************************************** -->
77
78<div class="doc_text">
79
80<p>Welcome to LLVM! In order to get started, you first need to know some
81basic information.</p>
82
83<p>First, LLVM comes in two pieces. The first piece is the LLVM suite. This
84contains all of the tools, libraries, and header files needed to use the low
85level virtual machine. It contains an assembler, disassembler, bytecode
Reid Spencer84f82f72006-08-28 00:34:19 +000086analyzer and bytecode optimizer. It also contains a test suite that can be
Misha Brukman00c73d22003-11-07 19:43:14 +000087used to test the LLVM tools and the GCC front end.</p>
88
89<p>The second piece is the GCC front end. This component provides a version of
90GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front
Chris Lattner82ad9f12007-03-06 06:27:34 +000091end uses the GCC parser to convert code to LLVM. Once
Misha Brukman00c73d22003-11-07 19:43:14 +000092compiled into LLVM bytecode, a program can be manipulated with the LLVM tools
93from the LLVM suite.</p>
94
John Criswell3d8ba512004-12-08 17:53:54 +000095<p>
96There is a third, optional piece called llvm-test. It is a suite of programs
97with 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>
Misha Brukman9106eca2005-02-03 22:25:23 +0000117 <li>Install the GCC front end if you intend to compile C or C++:
Misha Brukman00c73d22003-11-07 19:43:14 +0000118 <ol>
Reid Spencerd4694f92004-12-22 06:29:07 +0000119 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000120 <li><tt>gunzip --stdout llvm-gcc.<i>platform</i>.tar.gz | tar -xvf -</tt>
Reid Spencerd4694f92004-12-22 06:29:07 +0000121 </li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000122 <li><tt>cd llvm-gcc3.4/<i>platform</i> (llvm-gcc3.4 only)<br>
Reid Spencerd4694f92004-12-22 06:29:07 +0000123 ./fixheaders</tt></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000124 <li>Add llvm-gcc's "bin" directory to your PATH variable.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000125 </ol></li>
126
Misha Brukman9106eca2005-02-03 22:25:23 +0000127 <li>Get the LLVM Source Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000128 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000129 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman00c73d22003-11-07 19:43:14 +0000130 <ol>
131 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell364cec42004-03-12 20:31:37 +0000132 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000133 </ol></li>
134
Misha Brukman00c73d22003-11-07 19:43:14 +0000135 </ul></li>
136
Misha Brukman9106eca2005-02-03 22:25:23 +0000137 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswell9e2485c2004-12-10 15:51:16 +0000138 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000139 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswell9e2485c2004-12-10 15:51:16 +0000140 <ol>
141 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
142 <li><tt>cd llvm/projects</tt>
143 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
John Criswell9e2485c2004-12-10 15:51:16 +0000144 </ol></li>
145
John Criswell9e2485c2004-12-10 15:51:16 +0000146 </ul></li>
147
148
Misha Brukman00c73d22003-11-07 19:43:14 +0000149 <li>Configure the LLVM Build Environment
150 <ol>
Misha Brukman9106eca2005-02-03 22:25:23 +0000151 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
152 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
153 Some common options:
154
Misha Brukman00c73d22003-11-07 19:43:14 +0000155 <ul>
Reid Spencerd4694f92004-12-22 06:29:07 +0000156 <li><tt>--prefix=<i>directory</i></tt>
157 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000158 want the LLVM tools and libraries to be installed (default
159 <tt>/usr/local</tt>).</p></li>
Reid Spencerfef93b72004-12-26 05:47:26 +0000160 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
161 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswell838bce52005-05-09 16:39:27 +0000162 C/C++ front end installation to use with this LLVM configuration. If
Reid Spencerfef93b72004-12-26 05:47:26 +0000163 not specified, the PATH will be searched.</p></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000164 <li><tt>--enable-spec2000=<i>directory</i></tt>
165 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
166 benchmarks should be available in
167 <tt><i>directory</i></tt>.</p></li>
168 </ul>
169 </ol></li>
170
171 <li>Build the LLVM Suite:
172 <ol>
Chris Lattner95e92582004-07-18 22:32:22 +0000173 <li><tt>gmake -k |&amp; tee gnumake.out
174 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000175 <li>If you get an "internal compiler error (ICE)" or test failures, see
176 <a href="#brokengcc">below</a>.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000177 </ol>
178
179</ol>
180
Chris Lattnerfcd37252004-06-21 22:52:48 +0000181<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000182detailed information on configuring and compiling LLVM. See <a
183href="#environment">Setting Up Your Environment</a> for tips that simplify
184working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
185Layout</a> to learn about the layout of the source code tree.</p>
186
187</div>
188
189<!-- *********************************************************************** -->
190<div class="doc_section">
191 <a name="requirements"><b>Requirements</b></a>
192</div>
193<!-- *********************************************************************** -->
194
195<div class="doc_text">
196
197<p>Before you begin to use the LLVM system, review the requirements given below.
198This may save you some trouble by knowing ahead of time what hardware and
199software you will need.</p>
200
201</div>
202
203<!-- ======================================================================= -->
204<div class="doc_subsection">
205 <a name="hardware"><b>Hardware</b></a>
206</div>
207
208<div class="doc_text">
209
210<p>LLVM is known to work on the following platforms:</p>
211
Chris Lattner9abd8af2006-09-07 04:19:09 +0000212<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000213<tr>
214 <th>OS</th>
215 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000216 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000217</tr>
218<tr>
219 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000220 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000221 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000222</tr>
223<tr>
224 <td>Solaris</td>
225 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000226 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000227</tr>
228<tr>
229 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000230 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000231 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000232</tr>
233<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000234 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000235 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000236 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000237</tr>
238<tr>
Tanya Lattner993b9802006-04-20 04:35:34 +0000239 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
240 <td>x86</td>
241 <td>GCC</td>
242
243</tr>
244<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000245 <td>Cygwin/Win32</td>
Chris Lattner6947e552006-07-21 00:06:27 +0000246 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a></sup></td>
Reid Spencer65e8f5b2004-12-23 19:39:54 +0000247 <td>GCC 3.4.X, binutils 2.15</td>
Misha Brukman69def742004-11-19 21:53:22 +0000248</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000249<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000250 <td>MinGW/Win32</td>
Chris Lattner6947e552006-07-21 00:06:27 +0000251 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,<a href="#pf_8">8</a></sup></td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000252 <td>GCC 3.4.X, binutils 2.15</td>
253</tr>
254<tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000255 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000256 <td>amd64<sup><a href="#pf_3">3</a></sup></td>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000257 <td>GCC</td>
258</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000259</table>
260
261<p>LLVM has partial support for the following platforms:</p>
262
Chris Lattner9abd8af2006-09-07 04:19:09 +0000263<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000264<tr>
265 <th>OS</th>
266 <th>Arch</th>
267 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000268</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000269<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000270 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000271 <td>x86<sup><a href="#pf_1">1</a></sup></td>
272 <td>Visual Studio .NET<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000273<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000274 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000275 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000276 <td>GCC</td>
277</tr>
278<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000279 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000280 <td>PowerPC</td>
281 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000282</tr>
John Criswell75162552005-05-09 16:49:59 +0000283
284<tr>
285 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
286 <td>Alpha</td>
287 <td>GCC</td>
288</tr>
289<tr>
290 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
291 <td>Itanium (IA-64)</td>
292 <td>GCC</td>
293</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000294<tr>
295 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
296 <td>Itanium (IA-64)</td>
297 <td>HP aCC</td>
298</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000299</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000300
Misha Brukmana892ead2005-02-09 21:01:26 +0000301<p><b>Notes:</b></p>
302
Misha Brukman6d8e1532005-02-09 22:38:47 +0000303<div class="doc_notes">
304<ol>
305<li><a name="pf_1">Code generation supported for Pentium processors and
306up</a></li>
307<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
308<li><a name="pf_3">No native code generation</a></li>
309<li><a name="pf_4">Build is not complete: one or more tools don't link</a></li>
310<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner5907d402006-08-14 20:45:25 +0000311<li><a name="pf_6">The port is done using the MSYS shell.</a>
Misha Brukmana892ead2005-02-09 21:01:26 +0000312<a href="http://www.mingw.org/MinGWiki/">Download</a> and install
Chris Lattner6947e552006-07-21 00:06:27 +0000313bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source,
Chris Lattner5907d402006-08-14 20:45:25 +0000314if necessary. Bison &amp; flex can be also grabbed from GNUWin32 sf.net
315project.</li>
John Criswell75162552005-05-09 16:49:59 +0000316<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Chris Lattner5907d402006-08-14 20:45:25 +0000317<li><a name="pf_8">Binutils</a> up to post-2.17 has bug in bfd/cofflink.c
Chris Lattner6947e552006-07-21 00:06:27 +0000318 preventing LLVM from building correctly. Several workarounds have been
319 introduced into LLVM build system, but the bug can occur anytime in the
Chris Lattner5907d402006-08-14 20:45:25 +0000320 future. We highly recommend that you rebuild your current binutils with the
Chris Lattner6947e552006-07-21 00:06:27 +0000321 patch from <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=2659">
Chris Lattner5907d402006-08-14 20:45:25 +0000322 Binutils bugzilla</a>, if it wasn't already applied.</li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000323</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000324</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000325
Misha Brukman69def742004-11-19 21:53:22 +0000326<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 +0000327mode, depending on the system (it is so large because of all the debugging
328information and the fact that the libraries are statically linked into multiple
329tools). If you do not need many of the tools and you are space-conscious,
Misha Brukman69def742004-11-19 21:53:22 +0000330you can disable them individually in <tt>llvm/tools/Makefile</tt>. The Release
331build requires considerably less space.</p>
332
Misha Brukman00c73d22003-11-07 19:43:14 +0000333<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
334guaranteed to do so. If compilation is successful, the LLVM utilities should be
335able to assemble, disassemble, analyze, and optimize LLVM bytecode. Code
336generation should work as well, although the generated native code may not work
337on your platform.</p>
338
339<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 +0000340to work on another platform, you can download a copy of the source and <a
341href="CFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000342
343</div>
344
345<!-- ======================================================================= -->
Reid Spencer748d82e2004-11-15 21:15:12 +0000346<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000347<div class="doc_text">
Reid Spencer748d82e2004-11-15 21:15:12 +0000348 <p>Compiling LLVM requires that you have several software packages
349 installed. The table below lists those required packages. The Package column
350 is the usual name for the software package that LLVM depends on. The Version
351 column provides "known to work" versions of the package. The Notes column
352 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000353 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000354 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000355
Reid Spencer748d82e2004-11-15 21:15:12 +0000356 <tr>
357 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
358 <td>3.79, 3.79.1</td>
359 <td>Makefile/build processor</td>
360 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000361
Reid Spencer748d82e2004-11-15 21:15:12 +0000362 <tr>
363 <td><a href="http://gcc.gnu.org">GCC</a></td>
364 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000365 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000366 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000367
Reid Spencer748d82e2004-11-15 21:15:12 +0000368 <tr>
Chris Lattner2286cab2005-09-06 04:07:15 +0000369 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
370 <td>4.5</td>
371 <td>For building the CFE</td>
372 </tr>
373
374 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000375 <td><a href="http://www.gnu.org/software/flex">Flex</a></td>
376 <td>2.5.4</td>
377 <td>LEX compiler</td>
378 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000379
Reid Spencer748d82e2004-11-15 21:15:12 +0000380 <tr>
381 <td><a href="http://www.gnu.org/software/bison/bison.html">Bison</a></td>
Jeff Cohen4896c5d2006-01-04 06:51:22 +0000382 <td>1.28, 1.35, 1.75, 1.875d, 2.0, or 2.1<br>(not 1.85 or 1.875)</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000383 <td>YACC compiler</td>
384 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000385
Reid Spencer748d82e2004-11-15 21:15:12 +0000386 <tr>
John Criswell9c29bfb2007-06-29 19:12:31 +0000387 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
388 <td>&ge;1.3</td>
389 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000390 </tr>
391
392 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000393 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
394 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000395 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000396 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000397
Reid Spencer748d82e2004-11-15 21:15:12 +0000398 <tr>
399 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
400 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000401 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000402 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000403
Reid Spencer748d82e2004-11-15 21:15:12 +0000404 <tr>
405 <td><a href="http://expect.nist.gov/">expect</a></td>
406 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000407 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000408 </tr>
409
410 <tr>
411 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000412 <td>&ge;5.6.0</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000413 <td>Nightly tester, utilities</td>
414 </tr>
415
416 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000417 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
418 <td>1.4</td>
419 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000420 </tr>
421
422 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000423 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
424 <td>2.59</td>
425 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
426 </tr>
427
428 <tr>
429 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
430 <td>1.9.2</td>
431 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
432 </tr>
433
434 <tr>
435 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
436 <td>1.5.10</td>
437 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000438 </tr>
439
440 </table>
441
Misha Brukman6d8e1532005-02-09 22:38:47 +0000442 <p><b>Notes:</b></p>
443 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000444 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000445 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000446 need to build the other languages for LLVM's purposes.</a> See
447 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell9c29bfb2007-06-29 19:12:31 +0000448 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman6d8e1532005-02-09 22:38:47 +0000449 latest LLVM sources. If you're working from a release distribution, you
John Criswell9c29bfb2007-06-29 19:12:31 +0000450 don't need Subversion.</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000451 <li><a name="sf3">Only needed if you want to run the automated test
452 suite in the <tt>llvm/test</tt> directory.</a></li>
453 <li><a name="sf4">If you want to make changes to the configure scripts,
Reid Spencer748d82e2004-11-15 21:15:12 +0000454 you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4
Reid Spencer200d93b2004-12-09 17:55:37 +0000455 or higher). You will also need automake (1.9.2). We only use aclocal
456 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000457 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000458 </div>
459
Reid Spencer748d82e2004-11-15 21:15:12 +0000460 <p>Additionally, your compilation host is expected to have the usual
461 plethora of Unix utilities. Specifically:</p>
462 <ul>
463 <li><b>ar</b> - archive library builder</li>
464 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
465 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
466 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000467 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000468 <li><b>cp</b> - copy files</li>
469 <li><b>date</b> - print the current date/time </li>
470 <li><b>echo</b> - print to standard output</li>
471 <li><b>egrep</b> - extended regular expression search utility</li>
472 <li><b>etags</b> - C/C++ tag file creator for vim/emacs</li>
473 <li><b>find</b> - find files/dirs in a file system</li>
474 <li><b>grep</b> - regular expression search utility</li>
475 <li><b>gzip*</b> - gzip command for distribution generation</li>
476 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
477 <li><b>install</b> - install directories/files </li>
478 <li><b>mkdir</b> - create a directory</li>
479 <li><b>mv</b> - move (rename) files</li>
480 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000481 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000482 <li><b>sed</b> - stream editor for transforming output</li>
483 <li><b>sh</b> - Bourne shell for make build scripts</li>
484 <li><b>tar</b> - tape archive for distribution generation</li>
485 <li><b>test</b> - test things in file system</li>
486 <li><b>unzip*</b> - unzip command for distribution checking</li>
487 <li><b>zip*</b> - zip command for distribution generation</li>
488 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000489</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000490
Chris Lattner95e92582004-07-18 22:32:22 +0000491<!-- ======================================================================= -->
492<div class="doc_subsection">
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000493 <a name="brokengcc">Broken versions of GCC and other tools</a>
Chris Lattner95e92582004-07-18 22:32:22 +0000494</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000495
Chris Lattner95e92582004-07-18 22:32:22 +0000496<div class="doc_text">
497
498<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
499bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner6557f182006-06-16 17:20:33 +0000500to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
Chris Lattner36117ac2007-05-10 06:42:21 +0000501successfully with them (however, see important notes below). Other versions
502of GCC will probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000503here are known to not work. If you are using one of these versions, please try
504to upgrade your GCC to something more recent. If you run into a problem with a
505version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
506us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
507of GCC you are using.
508</p>
509
510<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
511problems in the STL that effectively prevent it from compiling LLVM.
512</p>
513
John Criswell294ba022004-11-23 22:06:24 +0000514<p><b>GCC 3.2.2</b>: This version of GCC fails to compile LLVM.</p>
515
Chris Lattner95e92582004-07-18 22:32:22 +0000516<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
517href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
518the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000519
Chris Lattner8e64f152005-02-13 22:20:49 +0000520<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
521 Cygwin does not work. Please <a href="CFEBuildInstrs.html#cygwin">upgrade
522 to a newer version</a> if possible.</p>
523<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
524 possibly others) does not compile LLVM correctly (it appears that exception
525 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
526 to a newer version of GCC.</p>
Chris Lattner3213a3a2007-05-10 05:37:14 +0000527<p><b>GCC 3.4.0</b> on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000528 code generator, causing an infinite loop in the llvm-gcc build when built
529 with optimizations enabled (i.e. a release build).</p>
530<p><b>GCC 3.4.2</b> on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
531 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
532 correctly compiles LLVM at -O2. A work around is to build release LLVM
533 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Chris Lattner77c2af62007-04-01 20:14:46 +0000534<p><b>GCC 3.4.x</b> on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
535 miscompiles portions of LLVM</a>.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000536<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
537 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000538<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
539 default with ENABLE_OPTIMIZED=1. To work around this, build with
540 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000541<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
542 compiling some files. At the time of this writing, GCC mainline (4.2)
543 did not share the problem.</p>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000544<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
545 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
546 code. LLVM will appear to mostly work but will be buggy, e.g. failing
547 portions of its testsuite.</p>
Reid Spencer72f92f02007-04-11 21:28:31 +0000548<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
549platforms compiling md5.c gets a mangled constant.</p>
Reid Spencer7a119082006-11-04 00:33:42 +0000550<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
551long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
552defined in a discarded section. You can safely ignore these messages as they are
553erroneous and the linkage is correct. These messages disappear using ld
5542.17.</p>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000555
556<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
557href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
558causes huge link times (minutes instead of seconds) when building LLVM. We
559recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
560
Misha Brukman00c73d22003-11-07 19:43:14 +0000561</div>
562
Chris Lattner95e92582004-07-18 22:32:22 +0000563
564
Misha Brukman00c73d22003-11-07 19:43:14 +0000565<!-- *********************************************************************** -->
566<div class="doc_section">
567 <a name="starting"><b>Getting Started with LLVM</b></a>
568</div>
569<!-- *********************************************************************** -->
570
Chris Lattner95e92582004-07-18 22:32:22 +0000571<div class="doc_text">
572
573<p>The remainder of this guide is meant to get you up and running with
574LLVM and to give you some basic information about the LLVM environment.</p>
575
576<p>The later sections of this guide describe the <a
577href="#layout">general layout</a> of the the LLVM source tree, a <a
578href="#tutorial">simple example</a> using the LLVM tool chain, and <a
579href="#links">links</a> to find more information about LLVM or to get
580help via e-mail.</p>
581</div>
582
Misha Brukman00c73d22003-11-07 19:43:14 +0000583<!-- ======================================================================= -->
584<div class="doc_subsection">
585 <a name="terminology">Terminology and Notation</a>
586</div>
587
588<div class="doc_text">
589
590<p>Throughout this manual, the following names are used to denote paths
591specific to the local system and working environment. <i>These are not
592environment variables you need to set but just strings used in the rest
593of this document below</i>. In any of the examples below, simply replace
594each of these names with the appropriate pathname on your local system.
595All these paths are absolute:</p>
596
Misha Brukman54111c42004-01-20 00:20:17 +0000597<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000598 <dt>SRC_ROOT
599 <dd>
600 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000601 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000602
Misha Brukman00c73d22003-11-07 19:43:14 +0000603 <dt>OBJ_ROOT
604 <dd>
605 This is the top level directory of the LLVM object tree (i.e. the
606 tree where object files and compiled programs will be placed. It
607 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000608 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000609
610 <dt>LLVMGCCDIR
611 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000612 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000613 <p>
614 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000615 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +0000616</dl>
617
618</div>
619
620<!-- ======================================================================= -->
621<div class="doc_subsection">
622 <a name="environment">Setting Up Your Environment</a>
623</div>
624
625<div class="doc_text">
626
627<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000628In order to compile and use LLVM, you may need to set some environment
629variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000630
Misha Brukman54111c42004-01-20 00:20:17 +0000631<dl>
Reid Spencerf96eb572004-12-15 00:14:01 +0000632 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000633 <dd>[Optional] This environment variable helps LLVM linking tools find the
John Criswell8bfe6a72005-05-18 19:43:33 +0000634 locations of your bytecode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000635 convenience since you can specify the paths using the -L options of the
John Criswell8bfe6a72005-05-18 19:43:33 +0000636 tools and the C/C++ front-end will automatically use the bytecode files
637 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000638 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000639</dl>
640
641</div>
642
643<!-- ======================================================================= -->
644<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000645 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000646</div>
647
648<div class="doc_text">
649
650<p>
651If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000652can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000653suite and the LLVM GCC front end compiled for your platform. There is an
654additional test suite that is optional. Each file is a TAR archive that is
655compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000656</p>
657
Misha Brukman3ce11032005-02-02 18:01:57 +0000658<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000659<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000660 <dt><tt>llvm-x.y.tar.gz</tt></dt>
661 <dd>Source release for the LLVM libraries and tools.<br/></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000662
Misha Brukman3ce11032005-02-02 18:01:57 +0000663 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Chris Lattner7db3f522005-02-09 21:15:51 +0000664 <dd>Source release for the LLVM test suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000665
Chris Lattner1ef81af2006-04-20 05:08:23 +0000666 <dt><tt>llvm-gcc4-x.y.source.tar.gz</tt></dt>
667 <dd>Source release of the llvm-gcc4 front end. See README.LLVM in the root
668 directory for build instructions.<br/></dd>
669
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000670 <dt><tt>llvm-gcc4-x.y-platform.tar.gz</tt></dt>
671 <dd>Binary release of the llvm-gcc4 front end for a specific platform.<br/></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000672
Misha Brukman00c73d22003-11-07 19:43:14 +0000673</dl>
674
Jim Laskey6c3acb72006-07-31 21:37:55 +0000675<p>It is also possible to download the sources of the llvm-gcc4 front end from a
676read-only subversion mirror at
677svn://anonsvn.opensource.apple.com/svn/llvm/trunk. </p>
Jim Laskey3261f0b2006-06-16 23:20:21 +0000678
Misha Brukman00c73d22003-11-07 19:43:14 +0000679</div>
680
681<!-- ======================================================================= -->
682<div class="doc_subsection">
John Criswell9c29bfb2007-06-29 19:12:31 +0000683 <a name="checkout">Checkout LLVM from Subversion</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000684</div>
685
686<div class="doc_text">
687
John Criswell9c29bfb2007-06-29 19:12:31 +0000688<p>If you have access to our Subversion repository, you can get a fresh copy of
689the entire source code. All you need to do is check it out from Subvresion as
Misha Brukman00c73d22003-11-07 19:43:14 +0000690follows:</p>
691
692<ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000693 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov98044e42007-06-29 20:56:49 +0000694 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
695 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell9c29bfb2007-06-29 19:12:31 +0000696 llvm</tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000697</ul>
698
John Criswell9c29bfb2007-06-29 19:12:31 +0000699
Misha Brukman00c73d22003-11-07 19:43:14 +0000700<p>This will create an '<tt>llvm</tt>' directory in the current
701directory and fully populate it with the LLVM source code, Makefiles,
702test directories, and local copies of documentation files.</p>
703
Misha Brukman54111c42004-01-20 00:20:17 +0000704<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikovd933fa92007-06-29 23:13:42 +0000705revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikovd724dc82007-06-30 00:00:57 +0000706'<tt>trunk</tt>'). The following releases are located in the following
707 subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000708
John Criswelld000e1d2003-12-18 16:43:17 +0000709<ul>
Tanya Lattner1dcadec2007-05-22 06:06:22 +0000710<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner134693a2006-11-20 06:07:10 +0000711<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000712<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattner993b9802006-04-20 04:35:34 +0000713<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000714<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000715<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000716<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000717<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000718<li>Release 1.2: <b>RELEASE_12</b></li>
719<li>Release 1.1: <b>RELEASE_11</b></li>
720<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000721</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000722
Reid Spencer66db92e2004-12-08 16:51:31 +0000723<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 +0000724you get it from the Subversion repository:</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000725<pre>
726 cd llvm/projects
Anton Korobeynikov96734d72007-06-29 21:44:14 +0000727 svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencer66db92e2004-12-08 16:51:31 +0000728</pre>
729<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000730configured by the LLVM configure script as well as automatically updated when
John Criswell9c29bfb2007-06-29 19:12:31 +0000731you run <tt>svn update</tt>.</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000732
Chris Lattner82ad9f12007-03-06 06:27:34 +0000733<p>If you would like to get the GCC front end source code, you can also get it
734and build it yourself. Please follow <a href="CFEBuildInstrs.html">these
735instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000736
Misha Brukman00c73d22003-11-07 19:43:14 +0000737</div>
738
739<!-- ======================================================================= -->
740<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000741 <a name="installcf">Install the GCC Front End</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000742</div>
743
744<div class="doc_text">
745
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000746<p>Before configuring and compiling the LLVM suite, you can optionally extract the
747LLVM GCC front end from the binary distribution. It is used for running the
748llvm-test testsuite and for compiling C/C++ programs. Note that you can optionally
749<a href="CFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
750main LLVM repository.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000751
752<p>To install the GCC front end, do the following:</p>
753
754<ol>
755 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000756 <li><tt>gunzip --stdout llvmgcc-<i>version</i>.<i>platform</i>.tar.gz | tar -xvf
Misha Brukman00c73d22003-11-07 19:43:14 +0000757 -</tt></li>
758</ol>
759
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000760<p>Once the binary is uncompressed, you should add a symlink for llvm-gcc and
761llvm-g++ to some directory in your path. When you configure LLVM, it will
762automatically detect llvm-gcc's presence (if it is in your path) enabling its
763use in llvm-test. Note that you can always build or install llvm-gcc at any
764pointer after building the main LLVM repository: just reconfigure llvm and
765llvm-test will pick it up.
766</p>
767
Misha Brukman00c73d22003-11-07 19:43:14 +0000768<p>The binary versions of the GCC front end may not suit all of your needs. For
769example, the binary distribution may include an old version of a system header
770file, not "fix" a header file that needs to be fixed for GCC, or it may be
771linked with libraries not available on your system.</p>
772
773<p>In cases like these, you may want to try <a
774href="CFEBuildInstrs.html">building the GCC front end from source.</a> This is
Chris Lattnerf76e7bb2007-02-14 07:34:22 +0000775much easier now than it was in the past.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000776
777</div>
778
779<!-- ======================================================================= -->
780<div class="doc_subsection">
781 <a name="config">Local LLVM Configuration</a>
782</div>
783
784<div class="doc_text">
785
John Criswell9c29bfb2007-06-29 19:12:31 +0000786 <p>Once checked out from the Subversion repository, the LLVM suite source
787 code must be
Reid Spencer66db92e2004-12-08 16:51:31 +0000788configured via the <tt>configure</tt> script. This script sets variables in the
789various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
790<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
791the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000792
793<p>The following environment variables are used by the <tt>configure</tt>
794script to configure the build system:</p>
795
Chris Lattner9abd8af2006-09-07 04:19:09 +0000796<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +0000797 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000798 <tr>
799 <td>CC</td>
800 <td>Tells <tt>configure</tt> which C compiler to use. By default,
801 <tt>configure</tt> will look for the first GCC C compiler in
802 <tt>PATH</tt>. Use this variable to override
803 <tt>configure</tt>'s default behavior.</td>
804 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000805 <tr>
806 <td>CXX</td>
807 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
808 <tt>configure</tt> will look for the first GCC C++ compiler in
809 <tt>PATH</tt>. Use this variable to override
810 <tt>configure</tt>'s default behavior.</td>
811 </tr>
812</table>
813
814<p>The following options can be used to set or enable LLVM specific options:</p>
815
Misha Brukman54111c42004-01-20 00:20:17 +0000816<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +0000817 <dt><i>--with-llvmgccdir</i></dt>
818 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
819 The value of this option should specify the full pathname of the C/C++ Front
820 End to be used. If this option is not provided, the PATH will be searched for
821 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
822 be inferred from the path found. If the option is not given, and no llvm-gcc
823 can be found in the path then a warning will be produced by
824 <tt>configure</tt> indicating this situation. LLVM may still be built with
825 the <tt>tools-only</tt> target but attempting to build the runtime libraries
826 will fail as these libraries require llvm-gcc and llvm-g++. See
827 <a href="#installcf">Install the GCC Front End</a> for details on installing
828 the C/C++ Front End. See
829 <a href="CFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
830 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000831 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +0000832 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +0000833 found. Use this if you have multiple tcl installations on your machine and you
834 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
835 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +0000836 option, the LLVM configure script will search for the tcl 8.4 and 8.3
837 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000838 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000839 </dd>
840 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000841 <dd>
842 Enables optimized compilation by default (debugging symbols are removed
843 and GCC optimization flags are enabled). The default is to use an
844 unoptimized build (also known as a debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000845 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000846 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +0000847 <dt><i>--enable-debug-runtime</i></dt>
848 <dd>
849 Enables debug symbols in the runtime libraries. The default is to strip
850 debug symbols from the runtime libraries.
851 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000852 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000853 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +0000854 Compile the Just In Time (JIT) compiler functionality. This is not
855 available
Misha Brukman00c73d22003-11-07 19:43:14 +0000856 on all platforms. The default is dependent on platform, so it is best
857 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000858 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000859 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000860 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
861 <dd>Controls which targets will be built and linked into llc. The default
862 value for <tt>target_options</tt> is "all" which builds and links all
863 available targets. The value "host-only" can be specified to build only a
864 native compiler (no cross-compiler targets available). The "native" target is
865 selected as the target of the build host. You can also specify a comma
866 separated list of target names that you want available in llc. The target
John Criswell8bfe6a72005-05-18 19:43:33 +0000867 names use all lower case. The current set of targets is: <br/>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000868 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000869 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000870 <dt><i>--enable-doxygen</i></dt>
871 <dd>Look for the doxygen program and enable construction of doxygen based
872 documentation from the source code. This is disabled by default because
873 generating the documentation can take a long time and producess 100s of
874 megabytes of output.</dd>
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +0000875 <dt><i>--with-udis86</i></dt>
876 <dd>LLVM can use external disassembler library for various purposes (now it's
877 used only for examining code produced by JIT). This option will enable usage
878 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
879 bits) disassembler library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000880</dl>
881
882<p>To configure LLVM, follow these steps:</p>
883
884<ol>
885 <li>Change directory into the object root directory:
John Criswell0f6d7c02003-10-27 18:18:16 +0000886 <br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000887 <tt>cd <i>OBJ_ROOT</i></tt>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000888 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000889
Misha Brukman00c73d22003-11-07 19:43:14 +0000890 <li>Run the <tt>configure</tt> script located in the LLVM source tree:
891 <br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000892 <tt><i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</tt>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000893 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000894</ol>
John Criswell85ed3612003-06-12 19:34:44 +0000895
Misha Brukman00c73d22003-11-07 19:43:14 +0000896</div>
John Criswell85ed3612003-06-12 19:34:44 +0000897
Misha Brukman00c73d22003-11-07 19:43:14 +0000898<!-- ======================================================================= -->
899<div class="doc_subsection">
900 <a name="compile">Compiling the LLVM Suite Source Code</a>
901</div>
John Criswell85ed3612003-06-12 19:34:44 +0000902
Misha Brukman00c73d22003-11-07 19:43:14 +0000903<div class="doc_text">
John Criswell0b459202003-07-08 20:35:59 +0000904
Misha Brukman00c73d22003-11-07 19:43:14 +0000905<p>Once you have configured LLVM, you can build it. There are three types of
906builds:</p>
John Criswell0b459202003-07-08 20:35:59 +0000907
Misha Brukman54111c42004-01-20 00:20:17 +0000908<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000909 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +0000910 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000911 These builds are the default when one types <tt>gmake</tt> (unless the
912 <tt>--enable-optimized</tt> option was used during configuration). The
913 build system will compile the tools and libraries with debugging
914 information.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000915 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000916
917 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +0000918 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000919 These builds are enabled with the <tt>--enable-optimized</tt> option to
920 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
921 <tt>gmake</tt> command line. For these builds, the build system will
922 compile the tools and libraries with GCC optimizations enabled and strip
923 debugging information from the libraries and executables it generates.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000924 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000925
926 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +0000927 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000928 These builds are for use with profiling. They compile profiling
929 information into the code for use with programs like <tt>gprof</tt>.
930 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
931 on the <tt>gmake</tt> command line.
932</dl>
John Criswell7a73b802003-06-30 21:59:07 +0000933
Misha Brukman00c73d22003-11-07 19:43:14 +0000934<p>Once you have LLVM configured, you can build it by entering the
935<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +0000936
Misha Brukman00c73d22003-11-07 19:43:14 +0000937<p><tt>gmake</tt></p>
John Criswell20d2d3e2003-10-10 14:26:14 +0000938
Chris Lattner95e92582004-07-18 22:32:22 +0000939<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +0000940are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +0000941
942<p>
943If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +0000944the parallel build options provided by GNU Make. For example, you could use the
945command:</p>
John Criswell85ed3612003-06-12 19:34:44 +0000946
Misha Brukman00c73d22003-11-07 19:43:14 +0000947<p><tt>gmake -j2</tt></p>
John Criswellce760f62003-07-03 16:01:38 +0000948
Misha Brukman00c73d22003-11-07 19:43:14 +0000949<p>There are several special targets which are useful when working with the LLVM
950source code:</p>
John Criswellce760f62003-07-03 16:01:38 +0000951
Misha Brukman54111c42004-01-20 00:20:17 +0000952<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000953 <dt><tt>gmake clean</tt>
954 <dd>
955 Removes all files generated by the build. This includes object files,
956 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000957 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000958
Reid Spencer66db92e2004-12-08 16:51:31 +0000959 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000960 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +0000961 Removes everything that <tt>gmake clean</tt> does, but also removes files
962 generated by <tt>configure</tt>. It attempts to return the source tree to the
963 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000964 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000965
Misha Brukmane51c3562004-08-23 20:25:33 +0000966 <dt><tt>gmake install</tt>
967 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +0000968 Installs LLVM header files, libraries, tools, and documentation in a
969 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +0000970 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
971 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000972 <br><br>
973
Reid Spencer66db92e2004-12-08 16:51:31 +0000974 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000975 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +0000976 Assuming you built LLVM into $OBJDIR, when this command is run, it will
977 install bytecode libraries into the GCC front end's bytecode library
978 directory. If you need to update your bytecode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +0000979 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000980 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000981</dl>
John Criswellce760f62003-07-03 16:01:38 +0000982
Reid Spencer66db92e2004-12-08 16:51:31 +0000983<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
984details on these <tt>make</tt> targets and descriptions of other targets
985available.</p>
986
Misha Brukman00c73d22003-11-07 19:43:14 +0000987<p>It is also possible to override default values from <tt>configure</tt> by
988declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +0000989
Misha Brukman54111c42004-01-20 00:20:17 +0000990<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000991 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
992 <dd>
993 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000994 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000995
Reid Spencer004ba032006-04-09 23:45:38 +0000996 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +0000997 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +0000998 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000999 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +00001000
Misha Brukman00c73d22003-11-07 19:43:14 +00001001 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1002 <dd>
1003 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001004 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001005
Misha Brukman00c73d22003-11-07 19:43:14 +00001006 <dt><tt>gmake VERBOSE=1</tt>
1007 <dd>
1008 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001009 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001010
1011 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1012 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +00001013 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001014 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001015</dl>
John Criswellce760f62003-07-03 16:01:38 +00001016
Misha Brukman00c73d22003-11-07 19:43:14 +00001017<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1018it and any subdirectories that it contains. Entering any directory inside the
1019LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1020that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +00001021
Misha Brukman00c73d22003-11-07 19:43:14 +00001022</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001023
Misha Brukman00c73d22003-11-07 19:43:14 +00001024<!-- ======================================================================= -->
1025<div class="doc_subsection">
Reid Spencerd30a9712006-07-27 06:41:31 +00001026 <a name="cross-compile">Cross-Compiling LLVM</a>
Reid Spencer17850ef2006-07-27 05:43:30 +00001027</div>
1028
1029<div class="doc_text">
Reid Spencerd30a9712006-07-27 06:41:31 +00001030 <p>It is possible to cross-compile LLVM. That is, you can create LLVM
1031 executables and libraries for a platform different than the one one which you
1032 are compiling. To do this, a few additional steps are
1033 required. <sup><a href="#ccn_1">1</a></sup> To cross-compile LLVM, use
Reid Spencer17850ef2006-07-27 05:43:30 +00001034 these instructions:</p>
1035 <ol>
Reid Spencerd30a9712006-07-27 06:41:31 +00001036 <li>Configure and build LLVM as a native compiler. You will need
Reid Spencer17850ef2006-07-27 05:43:30 +00001037 just <tt>TableGen</tt> from that build.
1038 <ul>
1039 <li>If you have <tt>$LLVM_OBJ_ROOT=$LLVM_SRC_ROOT</tt> just execute
1040 <tt>make -C utils/TableGen</tt> after configuring.</li>
1041 <li>Otherwise you will need to monitor building process and terminate
1042 it just after <tt>TableGen</tt> was built.</li>
1043 </ul>
1044 </li>
1045 <li>Copy the TableGen binary to somewhere safe (out of your build tree).
1046 </li>
Reid Spencerd30a9712006-07-27 06:41:31 +00001047 <li>Configure LLVM to build with a cross-compiler. To do this, supply the
Reid Spencer17850ef2006-07-27 05:43:30 +00001048 configure script with <tt>--build</tt> and <tt>--host</tt> options that
Reid Spencerd30a9712006-07-27 06:41:31 +00001049 are different. The values of these options must be legal target triples
1050 that your GCC compiler supports.</li>
Reid Spencer17850ef2006-07-27 05:43:30 +00001051 <li>Put the saved <tt>TableGen</tt> executable into the
1052 into <tt>$LLVM_OBJ_ROOT/{BUILD_TYPE}/bin</tt> directory (e.g. into
1053 <tt>.../Release/bin</tt> for a Release build).</li>
1054 <li>Build LLVM as usual.</li>
1055 </ol>
Reid Spencerd30a9712006-07-27 06:41:31 +00001056 <p>The result of such a build will produce executables that are not executable
1057 on your build host (--build option) but can be executed on your compile host
1058 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001059 <p><b>Notes:</b></p>
1060 <div class="doc_notes">
1061 <ol>
1062 <li><a name="ccn_1">Cross-compiling</a> was tested only with Linux as
1063 build platform and Windows as host using mingw32 cross-compiler. Other
1064 combinations have not been tested.</li>
1065 </ol>
1066 </div>
1067</div>
1068
1069<!-- ======================================================================= -->
1070<div class="doc_subsection">
Misha Brukman00c73d22003-11-07 19:43:14 +00001071 <a name="objfiles">The Location of LLVM Object Files</a>
1072</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001073
Misha Brukman00c73d22003-11-07 19:43:14 +00001074<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001075
Misha Brukman00c73d22003-11-07 19:43:14 +00001076<p>The LLVM build system is capable of sharing a single LLVM source tree among
1077several LLVM builds. Hence, it is possible to build LLVM for several different
1078platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001079
Misha Brukman00c73d22003-11-07 19:43:14 +00001080<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001081
Misha Brukman00c73d22003-11-07 19:43:14 +00001082<ul>
1083 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001084
Misha Brukman00c73d22003-11-07 19:43:14 +00001085 <p><tt>cd <i>OBJ_ROOT</i></tt></p></li>
John Criswellce760f62003-07-03 16:01:38 +00001086
Misha Brukman00c73d22003-11-07 19:43:14 +00001087 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1088 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001089
Misha Brukman00c73d22003-11-07 19:43:14 +00001090 <p><tt><i>SRC_ROOT</i>/configure</tt></p></li>
1091</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001092
Misha Brukman00c73d22003-11-07 19:43:14 +00001093<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1094named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001095
Misha Brukman54111c42004-01-20 00:20:17 +00001096<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001097 <dt>Debug Builds
1098 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001099 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001100 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001101 <dd><tt><i>OBJ_ROOT</i>/Debug/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001102 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001103 <dd><tt><i>OBJ_ROOT</i>/Debug/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001104 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001105 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001106
Misha Brukman00c73d22003-11-07 19:43:14 +00001107 <dt>Release Builds
1108 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001109 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001110 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001111 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001112 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001113 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001114 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001115 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001116
Misha Brukman00c73d22003-11-07 19:43:14 +00001117 <dt>Profile Builds
1118 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001119 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001120 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001121 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001122 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001123 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001124 </dl>
1125</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001126
Misha Brukman00c73d22003-11-07 19:43:14 +00001127</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001128
Chris Lattnera553f622004-03-25 20:38:40 +00001129<!-- ======================================================================= -->
1130<div class="doc_subsection">
1131 <a name="optionalconfig">Optional Configuration Items</a>
1132</div>
1133
1134<div class="doc_text">
1135
1136<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001137If you're running on a Linux system that supports the "<a
Reid Spencer66db92e2004-12-08 16:51:31 +00001138 href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">
1139 binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001140module, and you have root access on the system, you can set your system up to
1141execute LLVM bytecode files directly. To do this, use commands like this (the
1142first command may not be required if you are already using the module):</p>
1143
Misha Brukman9106eca2005-02-03 22:25:23 +00001144<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001145<pre>
1146 $ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Misha Brukman9106eca2005-02-03 22:25:23 +00001147 $ echo ':llvm:M::llvm::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Chris Lattnera553f622004-03-25 20:38:40 +00001148 $ chmod u+x hello.bc (if needed)
1149 $ ./hello.bc
1150</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001151</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001152
1153<p>
1154This allows you to execute LLVM bytecode files directly. Thanks to Jack
1155Cummings for pointing this out!
1156</p>
1157
1158</div>
1159
1160
Misha Brukman00c73d22003-11-07 19:43:14 +00001161<!-- *********************************************************************** -->
1162<div class="doc_section">
1163 <a name="layout"><b>Program Layout</b></a>
1164</div>
1165<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001166
Misha Brukman00c73d22003-11-07 19:43:14 +00001167<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001168
Misha Brukman00c73d22003-11-07 19:43:14 +00001169<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell364cec42004-03-12 20:31:37 +00001170href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001171href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001172The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001173
Misha Brukman00c73d22003-11-07 19:43:14 +00001174</div>
John Criswell85ed3612003-06-12 19:34:44 +00001175
Misha Brukman00c73d22003-11-07 19:43:14 +00001176<!-- ======================================================================= -->
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001177<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1178<div class="doc_text">
1179 <p>This directory contains some simple examples of how to use the LLVM IR and
1180 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001181</div>
John Criswell85ed3612003-06-12 19:34:44 +00001182
Misha Brukman00c73d22003-11-07 19:43:14 +00001183<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001184<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001185<div class="doc_text">
1186
1187<p>This directory contains public header files exported from the LLVM
1188library. The three main subdirectories of this directory are:</p>
1189
Reid Spencer77d90192004-09-05 20:50:22 +00001190<dl>
1191 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1192 <dd>This directory contains all of the LLVM specific header files. This
1193 directory also has subdirectories for different portions of LLVM:
1194 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1195 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001196
Reid Spencer77d90192004-09-05 20:50:22 +00001197 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1198 <dd>This directory contains generic support libraries that are provided with
1199 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1200 and a Command Line option processing library store their header files here.
1201 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001202
Reid Spencer77d90192004-09-05 20:50:22 +00001203 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1204 <dd>This directory contains header files configured by the <tt>configure</tt>
1205 script. They wrap "standard" UNIX and C header files. Source code can
1206 include these header files which automatically take care of the conditional
1207 #includes that the <tt>configure</tt> script generates.</dd>
1208</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001209</div>
1210
1211<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001212<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001213<div class="doc_text">
1214
1215<p>This directory contains most of the source files of the LLVM system. In LLVM,
1216almost all code exists in libraries, making it very easy to share code among the
1217different <a href="#tools">tools</a>.</p>
1218
Misha Brukman54111c42004-01-20 00:20:17 +00001219<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001220 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1221 <dd> This directory holds the core LLVM source files that implement core
1222 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001223
Reid Spencer77d90192004-09-05 20:50:22 +00001224 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1225 <dd>This directory holds the source code for the LLVM assembly language parser
1226 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001227
Reid Spencer77d90192004-09-05 20:50:22 +00001228 <dt><tt><b>llvm/lib/ByteCode/</b></tt></dt>
1229 <dd>This directory holds code for reading and write LLVM bytecode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001230
Reid Spencer77d90192004-09-05 20:50:22 +00001231 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001232 different program analyses, such as Dominator Information, Call Graphs,
1233 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001234 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001235
Reid Spencer77d90192004-09-05 20:50:22 +00001236 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1237 <dd> This directory contains the source code for the LLVM to LLVM program
1238 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1239 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1240 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001241
Reid Spencer77d90192004-09-05 20:50:22 +00001242 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1243 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001244 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1245 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001246 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001247
Reid Spencer77d90192004-09-05 20:50:22 +00001248 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1249 <dd> This directory contains the major parts of the code generator: Instruction
1250 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001251
Reid Spencer77d90192004-09-05 20:50:22 +00001252 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1253 <dd> This directory contains the source level debugger library that makes
1254 it possible to instrument LLVM programs so that a debugger could identify
1255 source code locations at which the program is executing.</dd>
1256
1257 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
1258 <dd> This directory contains libraries for executing LLVM bytecode directly
1259 at runtime in both interpreted and JIT compiled fashions.</dd>
1260
1261 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1262 <dd> This directory contains the source code that corresponds to the header
1263 files located in <tt>llvm/include/Support/</tt>.</dd>
1264
1265 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1266 <dd>This directory contains the operating system abstraction layer that
1267 shields LLVM from platform-specific coding.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001268</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001269
Misha Brukman00c73d22003-11-07 19:43:14 +00001270</div>
John Criswell85ed3612003-06-12 19:34:44 +00001271
Misha Brukman00c73d22003-11-07 19:43:14 +00001272<!-- ======================================================================= -->
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001273<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1274<div class="doc_text">
1275 <p>This directory contains projects that are not strictly part of LLVM but are
1276 shipped with LLVM. This is also the directory where you should create your own
1277 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
1278 to set up your own project. See <tt>llvm/projects/Stacker</tt> for a fully
1279 functional example of a compiler front end.</p>
1280</div>
1281
1282<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001283<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001284<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001285
Misha Brukman00c73d22003-11-07 19:43:14 +00001286<p>This directory contains libraries which are compiled into LLVM bytecode and
1287used when linking programs with the GCC front end. Most of these libraries are
1288skeleton versions of real libraries; for example, libc is a stripped down
1289version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001290
Misha Brukman00c73d22003-11-07 19:43:14 +00001291<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1292end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001293
Misha Brukman00c73d22003-11-07 19:43:14 +00001294</div>
John Criswell85ed3612003-06-12 19:34:44 +00001295
Misha Brukman00c73d22003-11-07 19:43:14 +00001296<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001297<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001298<div class="doc_text">
Reid Spencer77d90192004-09-05 20:50:22 +00001299 <p>This directory contains feature and regression tests and other basic sanity
1300 checks on the LLVM infrastructure. These are intended to run quickly and cover
1301 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001302</div>
John Criswell85ed3612003-06-12 19:34:44 +00001303
Misha Brukman00c73d22003-11-07 19:43:14 +00001304<!-- ======================================================================= -->
John Criswell9c29bfb2007-06-29 19:12:31 +00001305<div class="doc_subsection"><a name="llvmtest"><tt>test-suite</tt></a></div>
Reid Spencer77d90192004-09-05 20:50:22 +00001306<div class="doc_text">
John Criswell9c29bfb2007-06-29 19:12:31 +00001307 <p>This is not a directory in the normal llvm module; it is a separate
1308 Subversion
1309 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1310 This
John Criswell3d8ba512004-12-08 17:53:54 +00001311 module contains a comprehensive correctness, performance, and benchmarking
1312 test
John Criswell9c29bfb2007-06-29 19:12:31 +00001313 suite for LLVM. It is a separate Subversion module because not every LLVM
1314 user is
John Criswell838bce52005-05-09 16:39:27 +00001315 interested in downloading or building such a comprehensive test suite. For
1316 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001317 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001318</div>
John Criswell85ed3612003-06-12 19:34:44 +00001319
Reid Spencer77d90192004-09-05 20:50:22 +00001320<!-- ======================================================================= -->
1321<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001322<div class="doc_text">
John Criswell20d2d3e2003-10-10 14:26:14 +00001323
Misha Brukman00c73d22003-11-07 19:43:14 +00001324<p>The <b>tools</b> directory contains the executables built out of the
1325libraries above, which form the main part of the user interface. You can
1326always get help for a tool by typing <tt>tool_name --help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001327following is a brief introduction to the most important tools. More detailed
1328information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001329
Misha Brukman54111c42004-01-20 00:20:17 +00001330<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001331
Reid Spencer77d90192004-09-05 20:50:22 +00001332 <dt><tt><b>bugpoint</b></tt></dt>
1333 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001334 optimization passes or code generation backends by narrowing down the
1335 given test case to the minimum number of passes and/or instructions that
1336 still cause a problem, whether it is a crash or miscompilation. See <a
1337 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001338 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001339
Reid Spencer77d90192004-09-05 20:50:22 +00001340 <dt><tt><b>llvmc</b></tt></dt>
1341 <dd>The LLVM Compiler Driver. This program can
1342 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1343 pre-processing, translation, optimization, assembly, and linking of programs
1344 all from one command line. <tt>llvmc</tt> also takes care of processing the
1345 dependent libraries found in bytecode. This reduces the need to get the
Reid Spencer079e9452004-12-08 18:00:30 +00001346 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswell8bfe6a72005-05-18 19:43:33 +00001347 note that this tool, while functional, is still experimental and not feature
1348 complete.</dd>
Reid Spencer77d90192004-09-05 20:50:22 +00001349
1350 <dt><tt><b>llvm-ar</b></tt></dt>
1351 <dd>The archiver produces an archive containing
Misha Brukman00c73d22003-11-07 19:43:14 +00001352 the given LLVM bytecode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001353 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001354
Reid Spencer77d90192004-09-05 20:50:22 +00001355 <dt><tt><b>llvm-as</b></tt></dt>
1356 <dd>The assembler transforms the human readable LLVM assembly to LLVM
1357 bytecode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001358
Reid Spencer77d90192004-09-05 20:50:22 +00001359 <dt><tt><b>llvm-dis</b></tt></dt>
1360 <dd>The disassembler transforms the LLVM bytecode to human readable
1361 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001362
Reid Spencer079e9452004-12-08 18:00:30 +00001363 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001364 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
1365 This is the linker invoked by <tt>llvmc</tt>. It performsn standard link time
1366 optimizations and allows optimization modules to be loaded and run so that
1367 language specific optimizations can be applied at link time.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001368
Reid Spencer77d90192004-09-05 20:50:22 +00001369 <dt><tt><b>llvm-link</b></tt></dt>
1370 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1371 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001372
Reid Spencer77d90192004-09-05 20:50:22 +00001373 <dt><tt><b>lli</b></tt></dt>
1374 <dd><tt>lli</tt> is the LLVM interpreter, which
Misha Brukman00c73d22003-11-07 19:43:14 +00001375 can directly execute LLVM bytecode (although very slowly...). In addition
1376 to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
1377 specifying <tt>-trace</tt> on the command line). Finally, for
John Criswelld9eceee2004-12-08 18:04:14 +00001378 architectures that support it (currently x86, Sparc, and PowerPC), by default,
Misha Brukman00c73d22003-11-07 19:43:14 +00001379 <tt>lli</tt> will function as a Just-In-Time compiler (if the
1380 functionality was compiled in), and will execute the code <i>much</i>
Reid Spencer77d90192004-09-05 20:50:22 +00001381 faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001382
Reid Spencer77d90192004-09-05 20:50:22 +00001383 <dt><tt><b>llc</b></tt></dt>
1384 <dd> <tt>llc</tt> is the LLVM backend compiler, which
John Criswell8bfe6a72005-05-18 19:43:33 +00001385 translates LLVM bytecode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001386 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001387
Reid Spencerd4694f92004-12-22 06:29:07 +00001388 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001389 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1390 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
1391 byte code or assembly (with the <tt>-emit-llvm</tt> option) instead of the
1392 usual machine code output. It works just like any other GCC compiler,
1393 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1394 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell9c29bfb2007-06-29 19:12:31 +00001395 separate Subversion module.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001396
Reid Spencer77d90192004-09-05 20:50:22 +00001397 <dt><tt><b>opt</b></tt></dt>
Reid Spencer84f82f72006-08-28 00:34:19 +00001398 <dd><tt>opt</tt> reads LLVM bytecode, applies a series of LLVM to LLVM
1399 transformations (which are specified on the command line), and then outputs
1400 the resultant bytecode. The '<tt>opt --help</tt>' command is a good way to
1401 get a list of the program transformations available in LLVM.<br/>
1402 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
1403 LLVM bytecode file and print out the results. It is primarily useful for
1404 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001405</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001406</div>
John Criswell85ed3612003-06-12 19:34:44 +00001407
Misha Brukman00c73d22003-11-07 19:43:14 +00001408<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001409<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001410<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001411
Misha Brukman00c73d22003-11-07 19:43:14 +00001412<p>This directory contains utilities for working with LLVM source code, and some
1413of the utilities are actually required as part of the build process because they
1414are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001415
Misha Brukman54111c42004-01-20 00:20:17 +00001416<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001417 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001418 that finds differences between code that LLC generates and code that LLI
1419 generates. This is a useful tool if you are debugging one of them,
1420 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001421 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001422
Misha Brukman54111c42004-01-20 00:20:17 +00001423 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001424 syntax-highlighting files which will work with Emacs and XEmacs editors,
1425 providing syntax highlighting support for LLVM assembly files and TableGen
1426 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001427 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001428
Misha Brukman54111c42004-01-20 00:20:17 +00001429 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001430 and outputs all non-generated source files, which is useful if one wishes
1431 to do a lot of development across directories and does not want to
1432 individually find each file. One way to use it is to run, for example:
1433 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001434 tree.<br><br>
1435
Reid Spencer77d90192004-09-05 20:50:22 +00001436 <dt><tt><b>llvmgrep</b></tt></dt>
1437 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1438 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1439 line. This is a very efficient way of searching the source base for a
1440 particular regular expression.</dd>
1441
Misha Brukman54111c42004-01-20 00:20:17 +00001442 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001443 files in the current directory and then compiles and links the tool that
1444 is the first argument. For example, assuming you are in the directory
1445 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1446 simply running <tt>makellvm llc</tt> will make a build of the current
1447 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001448 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001449
Tanya Lattner7a857dd2007-05-22 06:12:51 +00001450 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukman54111c42004-01-20 00:20:17 +00001451 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman00c73d22003-11-07 19:43:14 +00001452 cron script to generate nightly status reports of the functionality of
1453 tools, and the results can be seen by following the appropriate link on
Chris Lattner9abd8af2006-09-07 04:19:09 +00001454 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001455
Misha Brukman54111c42004-01-20 00:20:17 +00001456 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001457 the tool used to generate register descriptions, instruction set
1458 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001459 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001460
Misha Brukman54111c42004-01-20 00:20:17 +00001461 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001462 syntax-highlighting files which will work with the VIM editor, providing
1463 syntax highlighting support for LLVM assembly files and TableGen
1464 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001465 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001466
Misha Brukman00c73d22003-11-07 19:43:14 +00001467</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001468
Misha Brukman00c73d22003-11-07 19:43:14 +00001469</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001470
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001471<!-- ======================================================================= -->
1472<div class="doc_subsection"><a name="win32"><tt>llvm/win32</tt></a></div>
1473<div class="doc_text">
1474 <p>This directory contains build scripts and project files for use with
1475 Visual C++. This allows developers on Windows to build LLVM without the need
John Criswell3d8ba512004-12-08 17:53:54 +00001476 for Cygwin. The contents of this directory should be considered experimental
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001477 at this time.
1478 </p>
1479</div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001480<!-- *********************************************************************** -->
1481<div class="doc_section">
1482 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1483</div>
1484<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001485
Misha Brukman00c73d22003-11-07 19:43:14 +00001486<div class="doc_text">
Chris Lattner59075882007-01-04 07:08:27 +00001487<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
1488so we only include instructiosn for llvm-gcc4.
Chris Lattner5907d402006-08-14 20:45:25 +00001489</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001490
1491<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1492from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
1493create bytecode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1494the '--emit-llvm' flag is needed to produce LLVM bytecode output. For <i>makefiles</i> and
1495<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bytecode
1496output.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001497</div>
1498
1499<!-- ======================================================================= -->
Chris Lattner9abd8af2006-09-07 04:19:09 +00001500<div class="doc_subsection"><a name="tutorial4">Example with llvm-gcc4</a></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001501
1502<div class="doc_text">
1503
1504<ol>
1505 <li>First, create a simple C file, name it 'hello.c':
1506 <pre>
1507 #include &lt;stdio.h&gt;
1508 int main() {
1509 printf("hello world\n");
1510 return 0;
1511 }
1512 </pre></li>
1513
1514 <li><p>Next, compile the C file into a native executable:</p>
1515
1516 <p><tt>% llvm-gcc hello.c -o hello</tt></p>
1517
1518 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1519 -c arguments work as usual (producing a native .s or .o file,
1520 respectively). </p>
1521
1522 <li><p>Next, compile the C file into a LLVM bytecode file:</p>
1523 <p><tt>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</tt></p>
1524
1525 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1526 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1527 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
1528 the bytecode file.</p>
1529
1530 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1531 </p></li>
1532
1533 <li><p>Run the program in both forms. To run the program, use:</p>
1534
1535 <p><tt>% ./hello</tt></p>
1536
1537 <p>and</p>
1538
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001539 <p><tt>% lli hello.bc</tt></p>
Chris Lattner5907d402006-08-14 20:45:25 +00001540
1541 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001542 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001543
1544 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1545 code:</p>
1546
Chris Lattner9abd8af2006-09-07 04:19:09 +00001547 <p><tt>% llvm-dis &lt; hello.bc | less</tt><br><br></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001548
1549 <li><p>Compile the program to native assembly using the LLC code
1550 generator:</p>
1551
1552 <p><tt>% llc hello.bc -o hello.s</tt></p>
1553
1554 <li><p>Assemble the native assembly language file into a program:</p>
1555
1556 <p><b>Solaris:</b><tt>% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native</tt></p>
1557 <p><b>Others:</b><tt>% gcc hello.s -o hello.native</tt></p>
1558
1559 <li><p>Execute the native code program:</p>
1560
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001561 <p><tt>% ./hello.native</tt></p>
Chris Lattner5907d402006-08-14 20:45:25 +00001562
1563 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1564 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001565 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001566
1567</ol>
1568
1569</div>
1570
John Criswell85ed3612003-06-12 19:34:44 +00001571
Misha Brukman00c73d22003-11-07 19:43:14 +00001572<!-- *********************************************************************** -->
1573<div class="doc_section">
1574 <a name="problems">Common Problems</a>
1575</div>
1576<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001577
Misha Brukman00c73d22003-11-07 19:43:14 +00001578<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001579
Misha Brukman00c73d22003-11-07 19:43:14 +00001580<p>If you are having problems building or using LLVM, or if you have any other
1581general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1582Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001583
Misha Brukman00c73d22003-11-07 19:43:14 +00001584</div>
John Criswell85ed3612003-06-12 19:34:44 +00001585
Misha Brukman00c73d22003-11-07 19:43:14 +00001586<!-- *********************************************************************** -->
1587<div class="doc_section">
1588 <a name="links">Links</a>
1589</div>
1590<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001591
Misha Brukman00c73d22003-11-07 19:43:14 +00001592<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001593
Misha Brukman00c73d22003-11-07 19:43:14 +00001594<p>This document is just an <b>introduction</b> to how to use LLVM to do
1595some simple things... there are many more interesting and complicated things
1596that you can do that aren't documented here (but we'll gladly accept a patch
1597if you want to write something up!). For more information about LLVM, check
1598out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001599
Misha Brukman00c73d22003-11-07 19:43:14 +00001600<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001601 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1602 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1603 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001604 that Uses LLVM</a></li>
1605</ul>
1606
1607</div>
1608
1609<!-- *********************************************************************** -->
1610
1611<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001612<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001613 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1614 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1615 <a href="http://validator.w3.org/check/referer"><img
1616 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
1617
Misha Brukman142207b2003-11-22 01:30:01 +00001618 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001619 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001620 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001621 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001622</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001623</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001624</html>