blob: e9a03a22fd7557a1fa3336510bba83a20528afde [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 Lattner95e92582004-07-18 22:32:22 +000022 <li><a href="#brokengcc">Broken versions of GCC</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>
30 <li><a href="#checkout">Checkout LLVM from CVS</a>
31 <li><a href="#installcf">Install the GCC Front End</a>
32 <li><a href="#config">Local LLVM Configuration</a>
33 <li><a href="#compile">Compiling the LLVM Suite Source Code</a>
Reid 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>
41 <li><a href="#cvsdir"><tt>CVS</tt> directories</a>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000043 <li><a href="#include"><tt>llvm/include</tt></a>
44 <li><a href="#lib"><tt>llvm/lib</tt></a>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000045 <li><a href="#projects"><tt>llvm/projects</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000046 <li><a href="#runtime"><tt>llvm/runtime</tt></a>
47 <li><a href="#test"><tt>llvm/test</tt></a>
Reid Spencer77d90192004-09-05 20:50:22 +000048 <li><a href="#llvmtest"><tt>llvm-test</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a>
50 <li><a href="#utils"><tt>llvm/utils</tt></a>
Reid Spencerc4b09ba2004-12-08 16:18:26 +000051 <li><a href="#win32"><tt>llvm/win32</tt></a>
Misha Brukman00c73d22003-11-07 19:43:14 +000052 </ol></li>
John Criswell0f6d7c02003-10-27 18:18:16 +000053
Misha Brukman00c73d22003-11-07 19:43:14 +000054 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner9abd8af2006-09-07 04:19:09 +000055 <ol>
56 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
57 <li><a href="#tutorial3">Example with llvm-gcc3</a></li>
58 </ol>
Misha Brukman00c73d22003-11-07 19:43:14 +000059 <li><a href="#problems">Common Problems</a>
60 <li><a href="#links">Links</a>
61</ul>
62
Chris Lattner7911ce22004-05-23 21:07:27 +000063<div class="doc_author">
64 <p>Written by:
65 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
66 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
67 <a href="http://misha.brukman.net">Misha Brukman</a>,
68 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
69 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
70 </p>
71</div>
Misha Brukman00c73d22003-11-07 19:43:14 +000072
73
74<!-- *********************************************************************** -->
75<div class="doc_section">
76 <a name="overview"><b>Overview</b></a>
77</div>
78<!-- *********************************************************************** -->
79
80<div class="doc_text">
81
82<p>Welcome to LLVM! In order to get started, you first need to know some
83basic information.</p>
84
85<p>First, LLVM comes in two pieces. The first piece is the LLVM suite. This
86contains all of the tools, libraries, and header files needed to use the low
87level virtual machine. It contains an assembler, disassembler, bytecode
Reid Spencer84f82f72006-08-28 00:34:19 +000088analyzer and bytecode optimizer. It also contains a test suite that can be
Misha Brukman00c73d22003-11-07 19:43:14 +000089used to test the LLVM tools and the GCC front end.</p>
90
91<p>The second piece is the GCC front end. This component provides a version of
92GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front
93end is a modified version of GCC 3.4 (we track the GCC 3.4 development). Once
94compiled into LLVM bytecode, a program can be manipulated with the LLVM tools
95from the LLVM suite.</p>
96
John Criswell3d8ba512004-12-08 17:53:54 +000097<p>
98There is a third, optional piece called llvm-test. It is a suite of programs
99with a testing harness that can be used to further test LLVM's functionality
100and performance.
101</p>
102
Misha Brukman00c73d22003-11-07 19:43:14 +0000103</div>
104
105<!-- *********************************************************************** -->
106<div class="doc_section">
107 <a name="quickstart"><b>Getting Started Quickly (A Summary)</b></a>
108</div>
109<!-- *********************************************************************** -->
110
111<div class="doc_text">
112
113<p>Here's the short story for getting up and running quickly with LLVM:</p>
114
115<ol>
Reid Spencer9f547912004-11-08 00:29:22 +0000116 <li>Read the documentation.</li>
117 <li>Read the documentation.</li>
118 <li>Remember that you were warned twice about reading the documentation.</li>
Misha Brukman9106eca2005-02-03 22:25:23 +0000119 <li>Install the GCC front end if you intend to compile C or C++:
Misha Brukman00c73d22003-11-07 19:43:14 +0000120 <ol>
Reid Spencerd4694f92004-12-22 06:29:07 +0000121 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000122 <li><tt>gunzip --stdout cfrontend.<i>platform</i>.tar.gz | tar -xvf -</tt>
Reid Spencerd4694f92004-12-22 06:29:07 +0000123 </li>
John Criswell9e2485c2004-12-10 15:51:16 +0000124 <li><tt>cd cfrontend/<i>platform</i><br>
Reid Spencerd4694f92004-12-22 06:29:07 +0000125 ./fixheaders</tt></li>
John Criswell838bce52005-05-09 16:39:27 +0000126 <li>Add the cfrontend's "bin" directory to your PATH variable.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000127 </ol></li>
128
Misha Brukman9106eca2005-02-03 22:25:23 +0000129 <li>Get the LLVM Source Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000130 <ul>
Misha Brukman9106eca2005-02-03 22:25:23 +0000131 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
Misha Brukman00c73d22003-11-07 19:43:14 +0000132 <ol>
133 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell364cec42004-03-12 20:31:37 +0000134 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000135 </ol></li>
136
Misha Brukman00c73d22003-11-07 19:43:14 +0000137 </ul></li>
138
Misha Brukman9106eca2005-02-03 22:25:23 +0000139 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswell9e2485c2004-12-10 15:51:16 +0000140 <ul>
Misha Brukman9106eca2005-02-03 22:25:23 +0000141 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
John Criswell9e2485c2004-12-10 15:51:16 +0000142 <ol>
143 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
144 <li><tt>cd llvm/projects</tt>
145 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
John Criswell9e2485c2004-12-10 15:51:16 +0000146 </ol></li>
147
John Criswell9e2485c2004-12-10 15:51:16 +0000148 </ul></li>
149
150
Misha Brukman00c73d22003-11-07 19:43:14 +0000151 <li>Configure the LLVM Build Environment
152 <ol>
Misha Brukman9106eca2005-02-03 22:25:23 +0000153 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
154 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
155 Some common options:
156
Misha Brukman00c73d22003-11-07 19:43:14 +0000157 <ul>
Reid Spencerd4694f92004-12-22 06:29:07 +0000158 <li><tt>--prefix=<i>directory</i></tt>
159 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000160 want the LLVM tools and libraries to be installed (default
161 <tt>/usr/local</tt>).</p></li>
Reid Spencerfef93b72004-12-26 05:47:26 +0000162 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
163 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswell838bce52005-05-09 16:39:27 +0000164 C/C++ front end installation to use with this LLVM configuration. If
Reid Spencerfef93b72004-12-26 05:47:26 +0000165 not specified, the PATH will be searched.</p></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000166 <li><tt>--enable-spec2000=<i>directory</i></tt>
167 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
168 benchmarks should be available in
169 <tt><i>directory</i></tt>.</p></li>
170 </ul>
171 </ol></li>
172
173 <li>Build the LLVM Suite:
174 <ol>
Chris Lattner95e92582004-07-18 22:32:22 +0000175 <li><tt>gmake -k |&amp; tee gnumake.out
176 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
177 <li>If you get an "internal compiler error (ICE)" see <a href="#brokengcc">below</a>.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000178 </ol>
179
180</ol>
181
Chris Lattnerfcd37252004-06-21 22:52:48 +0000182<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000183detailed information on configuring and compiling LLVM. See <a
184href="#environment">Setting Up Your Environment</a> for tips that simplify
185working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
186Layout</a> to learn about the layout of the source code tree.</p>
187
188</div>
189
190<!-- *********************************************************************** -->
191<div class="doc_section">
192 <a name="requirements"><b>Requirements</b></a>
193</div>
194<!-- *********************************************************************** -->
195
196<div class="doc_text">
197
198<p>Before you begin to use the LLVM system, review the requirements given below.
199This may save you some trouble by knowing ahead of time what hardware and
200software you will need.</p>
201
202</div>
203
204<!-- ======================================================================= -->
205<div class="doc_subsection">
206 <a name="hardware"><b>Hardware</b></a>
207</div>
208
209<div class="doc_text">
210
211<p>LLVM is known to work on the following platforms:</p>
212
Chris Lattner9abd8af2006-09-07 04:19:09 +0000213<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000214<tr>
215 <th>OS</th>
216 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000217 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000218</tr>
219<tr>
220 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000221 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000222 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000223</tr>
224<tr>
225 <td>Solaris</td>
226 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000227 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000228</tr>
229<tr>
230 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000231 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000232 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000233</tr>
234<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000235 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000236 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000237 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000238</tr>
239<tr>
Tanya Lattner993b9802006-04-20 04:35:34 +0000240 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
241 <td>x86</td>
242 <td>GCC</td>
243
244</tr>
245<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000246 <td>Cygwin/Win32</td>
Chris Lattner6947e552006-07-21 00:06:27 +0000247 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a></sup></td>
Reid Spencer65e8f5b2004-12-23 19:39:54 +0000248 <td>GCC 3.4.X, binutils 2.15</td>
Misha Brukman69def742004-11-19 21:53:22 +0000249</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000250<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000251 <td>MinGW/Win32</td>
Chris Lattner6947e552006-07-21 00:06:27 +0000252 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,<a href="#pf_8">8</a></sup></td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000253 <td>GCC 3.4.X, binutils 2.15</td>
254</tr>
255<tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000256 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000257 <td>amd64<sup><a href="#pf_3">3</a></sup></td>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000258 <td>GCC</td>
259</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000260</table>
261
262<p>LLVM has partial support for the following platforms:</p>
263
Chris Lattner9abd8af2006-09-07 04:19:09 +0000264<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000265<tr>
266 <th>OS</th>
267 <th>Arch</th>
268 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000269</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000270<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000271 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000272 <td>x86<sup><a href="#pf_1">1</a></sup></td>
273 <td>Visual Studio .NET<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000274<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000275 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000276 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000277 <td>GCC</td>
278</tr>
279<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000280 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000281 <td>PowerPC</td>
282 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000283</tr>
John Criswell75162552005-05-09 16:49:59 +0000284
285<tr>
286 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
287 <td>Alpha</td>
288 <td>GCC</td>
289</tr>
290<tr>
291 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
292 <td>Itanium (IA-64)</td>
293 <td>GCC</td>
294</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000295<tr>
296 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
297 <td>Itanium (IA-64)</td>
298 <td>HP aCC</td>
299</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000300</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000301
Misha Brukmana892ead2005-02-09 21:01:26 +0000302<p><b>Notes:</b></p>
303
Misha Brukman6d8e1532005-02-09 22:38:47 +0000304<div class="doc_notes">
305<ol>
306<li><a name="pf_1">Code generation supported for Pentium processors and
307up</a></li>
308<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
309<li><a name="pf_3">No native code generation</a></li>
310<li><a name="pf_4">Build is not complete: one or more tools don't link</a></li>
311<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner5907d402006-08-14 20:45:25 +0000312<li><a name="pf_6">The port is done using the MSYS shell.</a>
Misha Brukmana892ead2005-02-09 21:01:26 +0000313<a href="http://www.mingw.org/MinGWiki/">Download</a> and install
Chris Lattner6947e552006-07-21 00:06:27 +0000314bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source,
Chris Lattner5907d402006-08-14 20:45:25 +0000315if necessary. Bison &amp; flex can be also grabbed from GNUWin32 sf.net
316project.</li>
John Criswell75162552005-05-09 16:49:59 +0000317<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Chris Lattner5907d402006-08-14 20:45:25 +0000318<li><a name="pf_8">Binutils</a> up to post-2.17 has bug in bfd/cofflink.c
Chris Lattner6947e552006-07-21 00:06:27 +0000319 preventing LLVM from building correctly. Several workarounds have been
320 introduced into LLVM build system, but the bug can occur anytime in the
Chris Lattner5907d402006-08-14 20:45:25 +0000321 future. We highly recommend that you rebuild your current binutils with the
Chris Lattner6947e552006-07-21 00:06:27 +0000322 patch from <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=2659">
Chris Lattner5907d402006-08-14 20:45:25 +0000323 Binutils bugzilla</a>, if it wasn't already applied.</li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000324</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000325</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000326
Misha Brukman69def742004-11-19 21:53:22 +0000327<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswell8bfe6a72005-05-18 19:43:33 +0000328mode, depending on the system (it is so large because of all the debugging
329information and the fact that the libraries are statically linked into multiple
330tools). If you do not need many of the tools and you are space-conscious,
Misha Brukman69def742004-11-19 21:53:22 +0000331you can disable them individually in <tt>llvm/tools/Makefile</tt>. The Release
332build requires considerably less space.</p>
333
Misha Brukman00c73d22003-11-07 19:43:14 +0000334<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
335guaranteed to do so. If compilation is successful, the LLVM utilities should be
336able to assemble, disassemble, analyze, and optimize LLVM bytecode. Code
337generation should work as well, although the generated native code may not work
338on your platform.</p>
339
340<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman22e9e332004-08-09 19:57:01 +0000341to work on another platform, you can download a copy of the source and <a
342href="CFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000343
344</div>
345
346<!-- ======================================================================= -->
Reid Spencer748d82e2004-11-15 21:15:12 +0000347<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000348<div class="doc_text">
Reid Spencer748d82e2004-11-15 21:15:12 +0000349 <p>Compiling LLVM requires that you have several software packages
350 installed. The table below lists those required packages. The Package column
351 is the usual name for the software package that LLVM depends on. The Version
352 column provides "known to work" versions of the package. The Notes column
353 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000354 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000355 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000356
Reid Spencer748d82e2004-11-15 21:15:12 +0000357 <tr>
358 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
359 <td>3.79, 3.79.1</td>
360 <td>Makefile/build processor</td>
361 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000362
Reid Spencer748d82e2004-11-15 21:15:12 +0000363 <tr>
364 <td><a href="http://gcc.gnu.org">GCC</a></td>
365 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000366 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000367 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000368
Reid Spencer748d82e2004-11-15 21:15:12 +0000369 <tr>
Chris Lattner2286cab2005-09-06 04:07:15 +0000370 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
371 <td>4.5</td>
372 <td>For building the CFE</td>
373 </tr>
374
375 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000376 <td><a href="http://www.gnu.org/software/flex">Flex</a></td>
377 <td>2.5.4</td>
378 <td>LEX compiler</td>
379 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000380
Reid Spencer748d82e2004-11-15 21:15:12 +0000381 <tr>
382 <td><a href="http://www.gnu.org/software/bison/bison.html">Bison</a></td>
Jeff Cohen4896c5d2006-01-04 06:51:22 +0000383 <td>1.28, 1.35, 1.75, 1.875d, 2.0, or 2.1<br>(not 1.85 or 1.875)</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000384 <td>YACC compiler</td>
385 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000386
Reid Spencer748d82e2004-11-15 21:15:12 +0000387 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000388 <td><a href="https://www.cvshome.org/downloads.html">CVS</a></td>
389 <td>&ge;1.11</td>
390 <td>CVS access to LLVM<sup><a href="#sf2">2</a></sup></td>
391 </tr>
392
393 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000394 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
395 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000396 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000397 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000398
Reid Spencer748d82e2004-11-15 21:15:12 +0000399 <tr>
400 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
401 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000402 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000403 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000404
Reid Spencer748d82e2004-11-15 21:15:12 +0000405 <tr>
406 <td><a href="http://expect.nist.gov/">expect</a></td>
407 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000408 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000409 </tr>
410
411 <tr>
412 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000413 <td>&ge;5.6.0</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000414 <td>Nightly tester, utilities</td>
415 </tr>
416
417 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000418 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
419 <td>1.4</td>
420 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000421 </tr>
422
423 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000424 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
425 <td>2.59</td>
426 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
427 </tr>
428
429 <tr>
430 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
431 <td>1.9.2</td>
432 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
433 </tr>
434
435 <tr>
436 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
437 <td>1.5.10</td>
438 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000439 </tr>
440
441 </table>
442
Misha Brukman6d8e1532005-02-09 22:38:47 +0000443 <p><b>Notes:</b></p>
444 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000445 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000446 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000447 need to build the other languages for LLVM's purposes.</a> See
448 <a href="#brokengcc">below</a> for specific version info.</li>
449 <li><a name="sf2">You only need CVS if you intend to build from the
450 latest LLVM sources. If you're working from a release distribution, you
451 don't need CVS.</a></li>
452 <li><a name="sf3">Only needed if you want to run the automated test
453 suite in the <tt>llvm/test</tt> directory.</a></li>
454 <li><a name="sf4">If you want to make changes to the configure scripts,
Reid Spencer748d82e2004-11-15 21:15:12 +0000455 you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4
Reid Spencer200d93b2004-12-09 17:55:37 +0000456 or higher). You will also need automake (1.9.2). We only use aclocal
457 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000458 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000459 </div>
460
Reid Spencer748d82e2004-11-15 21:15:12 +0000461 <p>Additionally, your compilation host is expected to have the usual
462 plethora of Unix utilities. Specifically:</p>
463 <ul>
464 <li><b>ar</b> - archive library builder</li>
465 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
466 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
467 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000468 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000469 <li><b>cp</b> - copy files</li>
470 <li><b>date</b> - print the current date/time </li>
471 <li><b>echo</b> - print to standard output</li>
472 <li><b>egrep</b> - extended regular expression search utility</li>
473 <li><b>etags</b> - C/C++ tag file creator for vim/emacs</li>
474 <li><b>find</b> - find files/dirs in a file system</li>
475 <li><b>grep</b> - regular expression search utility</li>
476 <li><b>gzip*</b> - gzip command for distribution generation</li>
477 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
478 <li><b>install</b> - install directories/files </li>
479 <li><b>mkdir</b> - create a directory</li>
480 <li><b>mv</b> - move (rename) files</li>
481 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000482 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000483 <li><b>sed</b> - stream editor for transforming output</li>
484 <li><b>sh</b> - Bourne shell for make build scripts</li>
485 <li><b>tar</b> - tape archive for distribution generation</li>
486 <li><b>test</b> - test things in file system</li>
487 <li><b>unzip*</b> - unzip command for distribution checking</li>
488 <li><b>zip*</b> - zip command for distribution generation</li>
489 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000490</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000491
Chris Lattner95e92582004-07-18 22:32:22 +0000492<!-- ======================================================================= -->
493<div class="doc_subsection">
494 <a name="brokengcc">Broken versions of GCC</a>
495</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000496
Chris Lattner95e92582004-07-18 22:32:22 +0000497<div class="doc_text">
498
499<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
500bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner6557f182006-06-16 17:20:33 +0000501to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
502successfully with them (however, see below). Other versions of GCC will
503probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000504here are known to not work. If you are using one of these versions, please try
505to upgrade your GCC to something more recent. If you run into a problem with a
506version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
507us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
508of GCC you are using.
509</p>
510
511<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
512problems in the STL that effectively prevent it from compiling LLVM.
513</p>
514
John Criswell294ba022004-11-23 22:06:24 +0000515<p><b>GCC 3.2.2</b>: This version of GCC fails to compile LLVM.</p>
516
Chris Lattner95e92582004-07-18 22:32:22 +0000517<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
518href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
519the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000520
Chris Lattner8e64f152005-02-13 22:20:49 +0000521<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
522 Cygwin does not work. Please <a href="CFEBuildInstrs.html#cygwin">upgrade
523 to a newer version</a> if possible.</p>
524<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
525 possibly others) does not compile LLVM correctly (it appears that exception
526 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
527 to a newer version of GCC.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000528<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
529 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000530<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
531 default with ENABLE_OPTIMIZED=1. To work around this, build with
532 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000533<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
534 compiling some files. At the time of this writing, GCC mainline (4.2)
535 did not share the problem.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000536</div>
537
Chris Lattner95e92582004-07-18 22:32:22 +0000538
539
Misha Brukman00c73d22003-11-07 19:43:14 +0000540<!-- *********************************************************************** -->
541<div class="doc_section">
542 <a name="starting"><b>Getting Started with LLVM</b></a>
543</div>
544<!-- *********************************************************************** -->
545
Chris Lattner95e92582004-07-18 22:32:22 +0000546<div class="doc_text">
547
548<p>The remainder of this guide is meant to get you up and running with
549LLVM and to give you some basic information about the LLVM environment.</p>
550
551<p>The later sections of this guide describe the <a
552href="#layout">general layout</a> of the the LLVM source tree, a <a
553href="#tutorial">simple example</a> using the LLVM tool chain, and <a
554href="#links">links</a> to find more information about LLVM or to get
555help via e-mail.</p>
556</div>
557
Misha Brukman00c73d22003-11-07 19:43:14 +0000558<!-- ======================================================================= -->
559<div class="doc_subsection">
560 <a name="terminology">Terminology and Notation</a>
561</div>
562
563<div class="doc_text">
564
565<p>Throughout this manual, the following names are used to denote paths
566specific to the local system and working environment. <i>These are not
567environment variables you need to set but just strings used in the rest
568of this document below</i>. In any of the examples below, simply replace
569each of these names with the appropriate pathname on your local system.
570All these paths are absolute:</p>
571
Misha Brukman54111c42004-01-20 00:20:17 +0000572<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000573 <dt>SRC_ROOT
574 <dd>
575 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000576 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000577
Misha Brukman00c73d22003-11-07 19:43:14 +0000578 <dt>OBJ_ROOT
579 <dd>
580 This is the top level directory of the LLVM object tree (i.e. the
581 tree where object files and compiled programs will be placed. It
582 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000583 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000584
585 <dt>LLVMGCCDIR
586 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000587 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000588 <p>
589 For the pre-built GCC front end binaries, the LLVMGCCDIR is
590 <tt>cfrontend/<i>platform</i>/llvm-gcc</tt>.
591</dl>
592
593</div>
594
595<!-- ======================================================================= -->
596<div class="doc_subsection">
597 <a name="environment">Setting Up Your Environment</a>
598</div>
599
600<div class="doc_text">
601
602<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000603In order to compile and use LLVM, you may need to set some environment
604variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000605
Misha Brukman54111c42004-01-20 00:20:17 +0000606<dl>
Reid Spencerf96eb572004-12-15 00:14:01 +0000607 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000608 <dd>[Optional] This environment variable helps LLVM linking tools find the
John Criswell8bfe6a72005-05-18 19:43:33 +0000609 locations of your bytecode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000610 convenience since you can specify the paths using the -L options of the
John Criswell8bfe6a72005-05-18 19:43:33 +0000611 tools and the C/C++ front-end will automatically use the bytecode files
612 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000613 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000614</dl>
615
616</div>
617
618<!-- ======================================================================= -->
619<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000620 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000621</div>
622
623<div class="doc_text">
624
625<p>
626If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000627can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000628suite and the LLVM GCC front end compiled for your platform. There is an
629additional test suite that is optional. Each file is a TAR archive that is
630compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000631</p>
632
Misha Brukman3ce11032005-02-02 18:01:57 +0000633<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000634<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000635 <dt><tt>llvm-x.y.tar.gz</tt></dt>
636 <dd>Source release for the LLVM libraries and tools.<br/></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000637
Misha Brukman3ce11032005-02-02 18:01:57 +0000638 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Chris Lattner7db3f522005-02-09 21:15:51 +0000639 <dd>Source release for the LLVM test suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000640
Misha Brukman3ce11032005-02-02 18:01:57 +0000641 <dt><tt>cfrontend-x.y.source.tar.gz</tt></dt>
642 <dd>Source release of the GCC front end.<br/></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000643
Misha Brukman3ce11032005-02-02 18:01:57 +0000644 <dt><tt>cfrontend-x.y.i686-redhat-linux-gnu.tar.gz</tt></dt>
645 <dd>Binary release of the GCC front end for Linux/x86.<br/></dd>
John Criswelld000e1d2003-12-18 16:43:17 +0000646
Chris Lattner1ef81af2006-04-20 05:08:23 +0000647 <dt><tt>llvm-gcc4-x.y.source.tar.gz</tt></dt>
648 <dd>Source release of the llvm-gcc4 front end. See README.LLVM in the root
649 directory for build instructions.<br/></dd>
650
651 <dt><tt>llvm-gcc4-x.y.powerpc-apple-darwin8.6.0.tar.gz</tt></dt>
652 <dd>Binary release of the llvm-gcc4 front end for MacOS X/PowerPC.<br/></dd>
653
654 <dt><tt>llvm-gcc4-x.y.i686-apple-darwin8.6.1.tar.gz</tt></dt>
655 <dd>Binary release of the llvm-gcc4 front end for MacOS X/X86.<br/></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000656</dl>
657
Jim Laskey6c3acb72006-07-31 21:37:55 +0000658<p>It is also possible to download the sources of the llvm-gcc4 front end from a
659read-only subversion mirror at
660svn://anonsvn.opensource.apple.com/svn/llvm/trunk. </p>
Jim Laskey3261f0b2006-06-16 23:20:21 +0000661
Misha Brukman00c73d22003-11-07 19:43:14 +0000662</div>
663
664<!-- ======================================================================= -->
665<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000666 <a name="checkout">Checkout LLVM from CVS</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000667</div>
668
669<div class="doc_text">
670
671<p>If you have access to our CVS repository, you can get a fresh copy of
672the entire source code. All you need to do is check it out from CVS as
673follows:</p>
674
675<ul>
676<li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
Chris Lattnerc75a04b2006-08-03 22:14:43 +0000677 <li><tt>cvs -d :pserver:anon@llvm.org:/var/cvs/llvm login</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000678 <li>Hit the return key when prompted for the password.
Chris Lattnerc75a04b2006-08-03 22:14:43 +0000679 <li><tt>cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co
Misha Brukman00c73d22003-11-07 19:43:14 +0000680 llvm</tt>
681</ul>
682
683<p>This will create an '<tt>llvm</tt>' directory in the current
684directory and fully populate it with the LLVM source code, Makefiles,
685test directories, and local copies of documentation files.</p>
686
Misha Brukman54111c42004-01-20 00:20:17 +0000687<p>If you want to get a specific release (as opposed to the most recent
688revision), you can specify a label. The following releases have the following
Misha Brukman3ce11032005-02-02 18:01:57 +0000689labels:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000690
John Criswelld000e1d2003-12-18 16:43:17 +0000691<ul>
Tanya Lattner993b9802006-04-20 04:35:34 +0000692<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000693<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000694<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000695<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000696<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000697<li>Release 1.2: <b>RELEASE_12</b></li>
698<li>Release 1.1: <b>RELEASE_11</b></li>
699<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000700</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000701
Reid Spencer66db92e2004-12-08 16:51:31 +0000702<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
703you get it from the CVS repository:</p>
704<pre>
705 cd llvm/projects
Chris Lattnerc75a04b2006-08-03 22:14:43 +0000706 cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co llvm-test
Reid Spencer66db92e2004-12-08 16:51:31 +0000707</pre>
708<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000709configured by the LLVM configure script as well as automatically updated when
Reid Spencer66db92e2004-12-08 16:51:31 +0000710you run <tt>cvs update</tt>.</p>
711
Tanya Lattner993b9802006-04-20 04:35:34 +0000712<p>If you would like to get the GCC 3.4 front end source code, you can also get it from the CVS repository:</p>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000713
Chris Lattner604fdc12004-06-28 17:14:01 +0000714<pre>
Chris Lattnerc75a04b2006-08-03 22:14:43 +0000715 cvs -z3 -d :pserver:anon@llvm.org:/var/cvs/llvm co llvm-gcc
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000716</pre>
Misha Brukman00c73d22003-11-07 19:43:14 +0000717
Chris Lattner604fdc12004-06-28 17:14:01 +0000718<p>Please note that you must follow <a href="CFEBuildInstrs.html">these
John Criswell3d8ba512004-12-08 17:53:54 +0000719instructions</a> to successfully build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000720
Misha Brukman00c73d22003-11-07 19:43:14 +0000721</div>
722
723<!-- ======================================================================= -->
724<div class="doc_subsection">
Misha Brukman54111c42004-01-20 00:20:17 +0000725 <a name="installcf">Install the GCC Front End</a>
Misha Brukman00c73d22003-11-07 19:43:14 +0000726</div>
727
728<div class="doc_text">
729
730<p>Before configuring and compiling the LLVM suite, you need to extract the LLVM
731GCC front end from the binary distribution. It is used for building the
732bytecode libraries later used by the GCC front end for linking programs, and its
733location must be specified when the LLVM suite is configured.</p>
734
735<p>To install the GCC front end, do the following:</p>
736
737<ol>
738 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000739 <li><tt>gunzip --stdout cfrontend-<i>version</i>.<i>platform</i>.tar.gz | tar -xvf
Misha Brukman00c73d22003-11-07 19:43:14 +0000740 -</tt></li>
741</ol>
742
John Criswell9e2485c2004-12-10 15:51:16 +0000743<p>Next, you will need to fix your system header files:</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000744
John Criswell364cec42004-03-12 20:31:37 +0000745<p><tt>cd cfrontend/<i>platform</i><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000746 ./fixheaders</tt></p>
747
748<p>The binary versions of the GCC front end may not suit all of your needs. For
749example, the binary distribution may include an old version of a system header
750file, not "fix" a header file that needs to be fixed for GCC, or it may be
751linked with libraries not available on your system.</p>
752
753<p>In cases like these, you may want to try <a
754href="CFEBuildInstrs.html">building the GCC front end from source.</a> This is
755not for the faint of heart, so be forewarned.</p>
756
757</div>
758
759<!-- ======================================================================= -->
760<div class="doc_subsection">
761 <a name="config">Local LLVM Configuration</a>
762</div>
763
764<div class="doc_text">
765
766<p>Once checked out from the CVS repository, the LLVM suite source code must be
Reid Spencer66db92e2004-12-08 16:51:31 +0000767configured via the <tt>configure</tt> script. This script sets variables in the
768various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
769<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
770the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000771
772<p>The following environment variables are used by the <tt>configure</tt>
773script to configure the build system:</p>
774
Chris Lattner9abd8af2006-09-07 04:19:09 +0000775<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +0000776 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000777 <tr>
778 <td>CC</td>
779 <td>Tells <tt>configure</tt> which C compiler to use. By default,
780 <tt>configure</tt> will look for the first GCC C compiler in
781 <tt>PATH</tt>. Use this variable to override
782 <tt>configure</tt>'s default behavior.</td>
783 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000784 <tr>
785 <td>CXX</td>
786 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
787 <tt>configure</tt> will look for the first GCC C++ compiler in
788 <tt>PATH</tt>. Use this variable to override
789 <tt>configure</tt>'s default behavior.</td>
790 </tr>
791</table>
792
793<p>The following options can be used to set or enable LLVM specific options:</p>
794
Misha Brukman54111c42004-01-20 00:20:17 +0000795<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +0000796 <dt><i>--with-llvmgccdir</i></dt>
797 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
798 The value of this option should specify the full pathname of the C/C++ Front
799 End to be used. If this option is not provided, the PATH will be searched for
800 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
801 be inferred from the path found. If the option is not given, and no llvm-gcc
802 can be found in the path then a warning will be produced by
803 <tt>configure</tt> indicating this situation. LLVM may still be built with
804 the <tt>tools-only</tt> target but attempting to build the runtime libraries
805 will fail as these libraries require llvm-gcc and llvm-g++. See
806 <a href="#installcf">Install the GCC Front End</a> for details on installing
807 the C/C++ Front End. See
808 <a href="CFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
809 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000810 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +0000811 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +0000812 found. Use this if you have multiple tcl installations on your machine and you
813 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
814 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +0000815 option, the LLVM configure script will search for the tcl 8.4 and 8.3
816 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000817 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000818 </dd>
819 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000820 <dd>
821 Enables optimized compilation by default (debugging symbols are removed
822 and GCC optimization flags are enabled). The default is to use an
823 unoptimized build (also known as a debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000824 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000825 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +0000826 <dt><i>--enable-debug-runtime</i></dt>
827 <dd>
828 Enables debug symbols in the runtime libraries. The default is to strip
829 debug symbols from the runtime libraries.
830 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000831 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000832 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +0000833 Compile the Just In Time (JIT) compiler functionality. This is not
834 available
Misha Brukman00c73d22003-11-07 19:43:14 +0000835 on all platforms. The default is dependent on platform, so it is best
836 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000837 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000838 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000839 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
840 <dd>Controls which targets will be built and linked into llc. The default
841 value for <tt>target_options</tt> is "all" which builds and links all
842 available targets. The value "host-only" can be specified to build only a
843 native compiler (no cross-compiler targets available). The "native" target is
844 selected as the target of the build host. You can also specify a comma
845 separated list of target names that you want available in llc. The target
John Criswell8bfe6a72005-05-18 19:43:33 +0000846 names use all lower case. The current set of targets is: <br/>
Reid Spencer2dedcf52005-04-22 17:58:03 +0000847 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000848 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +0000849 <dt><i>--enable-doxygen</i></dt>
850 <dd>Look for the doxygen program and enable construction of doxygen based
851 documentation from the source code. This is disabled by default because
852 generating the documentation can take a long time and producess 100s of
853 megabytes of output.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000854</dl>
855
856<p>To configure LLVM, follow these steps:</p>
857
858<ol>
859 <li>Change directory into the object root directory:
John Criswell0f6d7c02003-10-27 18:18:16 +0000860 <br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000861 <tt>cd <i>OBJ_ROOT</i></tt>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000862 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000863
Misha Brukman00c73d22003-11-07 19:43:14 +0000864 <li>Run the <tt>configure</tt> script located in the LLVM source tree:
865 <br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000866 <tt><i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</tt>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000867 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000868</ol>
John Criswell85ed3612003-06-12 19:34:44 +0000869
Misha Brukman00c73d22003-11-07 19:43:14 +0000870</div>
John Criswell85ed3612003-06-12 19:34:44 +0000871
Misha Brukman00c73d22003-11-07 19:43:14 +0000872<!-- ======================================================================= -->
873<div class="doc_subsection">
874 <a name="compile">Compiling the LLVM Suite Source Code</a>
875</div>
John Criswell85ed3612003-06-12 19:34:44 +0000876
Misha Brukman00c73d22003-11-07 19:43:14 +0000877<div class="doc_text">
John Criswell0b459202003-07-08 20:35:59 +0000878
Misha Brukman00c73d22003-11-07 19:43:14 +0000879<p>Once you have configured LLVM, you can build it. There are three types of
880builds:</p>
John Criswell0b459202003-07-08 20:35:59 +0000881
Misha Brukman54111c42004-01-20 00:20:17 +0000882<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000883 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +0000884 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000885 These builds are the default when one types <tt>gmake</tt> (unless the
886 <tt>--enable-optimized</tt> option was used during configuration). The
887 build system will compile the tools and libraries with debugging
888 information.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000889 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000890
891 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +0000892 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000893 These builds are enabled with the <tt>--enable-optimized</tt> option to
894 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
895 <tt>gmake</tt> command line. For these builds, the build system will
896 compile the tools and libraries with GCC optimizations enabled and strip
897 debugging information from the libraries and executables it generates.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000898 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000899
900 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +0000901 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000902 These builds are for use with profiling. They compile profiling
903 information into the code for use with programs like <tt>gprof</tt>.
904 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
905 on the <tt>gmake</tt> command line.
906</dl>
John Criswell7a73b802003-06-30 21:59:07 +0000907
Misha Brukman00c73d22003-11-07 19:43:14 +0000908<p>Once you have LLVM configured, you can build it by entering the
909<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +0000910
Misha Brukman00c73d22003-11-07 19:43:14 +0000911<p><tt>gmake</tt></p>
John Criswell20d2d3e2003-10-10 14:26:14 +0000912
Chris Lattner95e92582004-07-18 22:32:22 +0000913<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +0000914are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +0000915
916<p>
917If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +0000918the parallel build options provided by GNU Make. For example, you could use the
919command:</p>
John Criswell85ed3612003-06-12 19:34:44 +0000920
Misha Brukman00c73d22003-11-07 19:43:14 +0000921<p><tt>gmake -j2</tt></p>
John Criswellce760f62003-07-03 16:01:38 +0000922
Misha Brukman00c73d22003-11-07 19:43:14 +0000923<p>There are several special targets which are useful when working with the LLVM
924source code:</p>
John Criswellce760f62003-07-03 16:01:38 +0000925
Misha Brukman54111c42004-01-20 00:20:17 +0000926<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000927 <dt><tt>gmake clean</tt>
928 <dd>
929 Removes all files generated by the build. This includes object files,
930 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000931 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000932
Reid Spencer66db92e2004-12-08 16:51:31 +0000933 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000934 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +0000935 Removes everything that <tt>gmake clean</tt> does, but also removes files
936 generated by <tt>configure</tt>. It attempts to return the source tree to the
937 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000938 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000939
Misha Brukmane51c3562004-08-23 20:25:33 +0000940 <dt><tt>gmake install</tt>
941 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +0000942 Installs LLVM header files, libraries, tools, and documentation in a
943 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +0000944 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
945 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000946 <br><br>
947
Reid Spencer66db92e2004-12-08 16:51:31 +0000948 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000949 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +0000950 Assuming you built LLVM into $OBJDIR, when this command is run, it will
951 install bytecode libraries into the GCC front end's bytecode library
952 directory. If you need to update your bytecode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +0000953 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000954 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000955</dl>
John Criswellce760f62003-07-03 16:01:38 +0000956
Reid Spencer66db92e2004-12-08 16:51:31 +0000957<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
958details on these <tt>make</tt> targets and descriptions of other targets
959available.</p>
960
Misha Brukman00c73d22003-11-07 19:43:14 +0000961<p>It is also possible to override default values from <tt>configure</tt> by
962declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +0000963
Misha Brukman54111c42004-01-20 00:20:17 +0000964<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000965 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
966 <dd>
967 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000968 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000969
Reid Spencer004ba032006-04-09 23:45:38 +0000970 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +0000971 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +0000972 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000973 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +0000974
Misha Brukman00c73d22003-11-07 19:43:14 +0000975 <dt><tt>gmake ENABLE_PROFILING=1</tt>
976 <dd>
977 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000978 <br><br>
John Criswellce760f62003-07-03 16:01:38 +0000979
Misha Brukman00c73d22003-11-07 19:43:14 +0000980 <dt><tt>gmake VERBOSE=1</tt>
981 <dd>
982 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000983 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +0000984
985 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
986 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +0000987 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000988 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000989</dl>
John Criswellce760f62003-07-03 16:01:38 +0000990
Misha Brukman00c73d22003-11-07 19:43:14 +0000991<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
992it and any subdirectories that it contains. Entering any directory inside the
993LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
994that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +0000995
Misha Brukman00c73d22003-11-07 19:43:14 +0000996</div>
John Criswell20d2d3e2003-10-10 14:26:14 +0000997
Misha Brukman00c73d22003-11-07 19:43:14 +0000998<!-- ======================================================================= -->
999<div class="doc_subsection">
Reid Spencerd30a9712006-07-27 06:41:31 +00001000 <a name="cross-compile">Cross-Compiling LLVM</a>
Reid Spencer17850ef2006-07-27 05:43:30 +00001001</div>
1002
1003<div class="doc_text">
Reid Spencerd30a9712006-07-27 06:41:31 +00001004 <p>It is possible to cross-compile LLVM. That is, you can create LLVM
1005 executables and libraries for a platform different than the one one which you
1006 are compiling. To do this, a few additional steps are
1007 required. <sup><a href="#ccn_1">1</a></sup> To cross-compile LLVM, use
Reid Spencer17850ef2006-07-27 05:43:30 +00001008 these instructions:</p>
1009 <ol>
Reid Spencerd30a9712006-07-27 06:41:31 +00001010 <li>Configure and build LLVM as a native compiler. You will need
Reid Spencer17850ef2006-07-27 05:43:30 +00001011 just <tt>TableGen</tt> from that build.
1012 <ul>
1013 <li>If you have <tt>$LLVM_OBJ_ROOT=$LLVM_SRC_ROOT</tt> just execute
1014 <tt>make -C utils/TableGen</tt> after configuring.</li>
1015 <li>Otherwise you will need to monitor building process and terminate
1016 it just after <tt>TableGen</tt> was built.</li>
1017 </ul>
1018 </li>
1019 <li>Copy the TableGen binary to somewhere safe (out of your build tree).
1020 </li>
Reid Spencerd30a9712006-07-27 06:41:31 +00001021 <li>Configure LLVM to build with a cross-compiler. To do this, supply the
Reid Spencer17850ef2006-07-27 05:43:30 +00001022 configure script with <tt>--build</tt> and <tt>--host</tt> options that
Reid Spencerd30a9712006-07-27 06:41:31 +00001023 are different. The values of these options must be legal target triples
1024 that your GCC compiler supports.</li>
Reid Spencer17850ef2006-07-27 05:43:30 +00001025 <li>Put the saved <tt>TableGen</tt> executable into the
1026 into <tt>$LLVM_OBJ_ROOT/{BUILD_TYPE}/bin</tt> directory (e.g. into
1027 <tt>.../Release/bin</tt> for a Release build).</li>
1028 <li>Build LLVM as usual.</li>
1029 </ol>
Reid Spencerd30a9712006-07-27 06:41:31 +00001030 <p>The result of such a build will produce executables that are not executable
1031 on your build host (--build option) but can be executed on your compile host
1032 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001033 <p><b>Notes:</b></p>
1034 <div class="doc_notes">
1035 <ol>
1036 <li><a name="ccn_1">Cross-compiling</a> was tested only with Linux as
1037 build platform and Windows as host using mingw32 cross-compiler. Other
1038 combinations have not been tested.</li>
1039 </ol>
1040 </div>
1041</div>
1042
1043<!-- ======================================================================= -->
1044<div class="doc_subsection">
Misha Brukman00c73d22003-11-07 19:43:14 +00001045 <a name="objfiles">The Location of LLVM Object Files</a>
1046</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001047
Misha Brukman00c73d22003-11-07 19:43:14 +00001048<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001049
Misha Brukman00c73d22003-11-07 19:43:14 +00001050<p>The LLVM build system is capable of sharing a single LLVM source tree among
1051several LLVM builds. Hence, it is possible to build LLVM for several different
1052platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001053
Misha Brukman00c73d22003-11-07 19:43:14 +00001054<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001055
Misha Brukman00c73d22003-11-07 19:43:14 +00001056<ul>
1057 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001058
Misha Brukman00c73d22003-11-07 19:43:14 +00001059 <p><tt>cd <i>OBJ_ROOT</i></tt></p></li>
John Criswellce760f62003-07-03 16:01:38 +00001060
Misha Brukman00c73d22003-11-07 19:43:14 +00001061 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1062 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001063
Misha Brukman00c73d22003-11-07 19:43:14 +00001064 <p><tt><i>SRC_ROOT</i>/configure</tt></p></li>
1065</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001066
Misha Brukman00c73d22003-11-07 19:43:14 +00001067<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1068named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001069
Misha Brukman54111c42004-01-20 00:20:17 +00001070<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001071 <dt>Debug Builds
1072 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001073 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001074 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001075 <dd><tt><i>OBJ_ROOT</i>/Debug/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001076 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001077 <dd><tt><i>OBJ_ROOT</i>/Debug/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001078 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001079 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001080
Misha Brukman00c73d22003-11-07 19:43:14 +00001081 <dt>Release Builds
1082 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001083 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001084 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001085 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001086 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001087 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001088 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001089 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001090
Misha Brukman00c73d22003-11-07 19:43:14 +00001091 <dt>Profile Builds
1092 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001093 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001094 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001095 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001096 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001097 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001098 </dl>
1099</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001100
Misha Brukman00c73d22003-11-07 19:43:14 +00001101</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001102
Chris Lattnera553f622004-03-25 20:38:40 +00001103<!-- ======================================================================= -->
1104<div class="doc_subsection">
1105 <a name="optionalconfig">Optional Configuration Items</a>
1106</div>
1107
1108<div class="doc_text">
1109
1110<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001111If you're running on a Linux system that supports the "<a
Reid Spencer66db92e2004-12-08 16:51:31 +00001112 href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">
1113 binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001114module, and you have root access on the system, you can set your system up to
1115execute LLVM bytecode files directly. To do this, use commands like this (the
1116first command may not be required if you are already using the module):</p>
1117
Misha Brukman9106eca2005-02-03 22:25:23 +00001118<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001119<pre>
1120 $ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Misha Brukman9106eca2005-02-03 22:25:23 +00001121 $ echo ':llvm:M::llvm::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Chris Lattnera553f622004-03-25 20:38:40 +00001122 $ chmod u+x hello.bc (if needed)
1123 $ ./hello.bc
1124</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001125</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001126
1127<p>
1128This allows you to execute LLVM bytecode files directly. Thanks to Jack
1129Cummings for pointing this out!
1130</p>
1131
1132</div>
1133
1134
Misha Brukman00c73d22003-11-07 19:43:14 +00001135<!-- *********************************************************************** -->
1136<div class="doc_section">
1137 <a name="layout"><b>Program Layout</b></a>
1138</div>
1139<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001140
Misha Brukman00c73d22003-11-07 19:43:14 +00001141<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001142
Misha Brukman00c73d22003-11-07 19:43:14 +00001143<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell364cec42004-03-12 20:31:37 +00001144href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001145href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001146The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001147
Misha Brukman00c73d22003-11-07 19:43:14 +00001148</div>
John Criswell85ed3612003-06-12 19:34:44 +00001149
Misha Brukman00c73d22003-11-07 19:43:14 +00001150<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001151<div class="doc_subsection"><a name="cvsdir"><tt>CVS</tt> directories</a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001152<div class="doc_text">
Misha Brukman00c73d22003-11-07 19:43:14 +00001153<p>Every directory checked out of CVS will contain a <tt>CVS</tt> directory; for
1154the most part these can just be ignored.</p>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001155</div>
John Criswell85ed3612003-06-12 19:34:44 +00001156
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001157<!-- ======================================================================= -->
1158<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1159<div class="doc_text">
1160 <p>This directory contains some simple examples of how to use the LLVM IR and
1161 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001162</div>
John Criswell85ed3612003-06-12 19:34:44 +00001163
Misha Brukman00c73d22003-11-07 19:43:14 +00001164<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001165<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001166<div class="doc_text">
1167
1168<p>This directory contains public header files exported from the LLVM
1169library. The three main subdirectories of this directory are:</p>
1170
Reid Spencer77d90192004-09-05 20:50:22 +00001171<dl>
1172 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1173 <dd>This directory contains all of the LLVM specific header files. This
1174 directory also has subdirectories for different portions of LLVM:
1175 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1176 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001177
Reid Spencer77d90192004-09-05 20:50:22 +00001178 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1179 <dd>This directory contains generic support libraries that are provided with
1180 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1181 and a Command Line option processing library store their header files here.
1182 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001183
Reid Spencer77d90192004-09-05 20:50:22 +00001184 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1185 <dd>This directory contains header files configured by the <tt>configure</tt>
1186 script. They wrap "standard" UNIX and C header files. Source code can
1187 include these header files which automatically take care of the conditional
1188 #includes that the <tt>configure</tt> script generates.</dd>
1189</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001190</div>
1191
1192<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001193<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001194<div class="doc_text">
1195
1196<p>This directory contains most of the source files of the LLVM system. In LLVM,
1197almost all code exists in libraries, making it very easy to share code among the
1198different <a href="#tools">tools</a>.</p>
1199
Misha Brukman54111c42004-01-20 00:20:17 +00001200<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001201 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1202 <dd> This directory holds the core LLVM source files that implement core
1203 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001204
Reid Spencer77d90192004-09-05 20:50:22 +00001205 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1206 <dd>This directory holds the source code for the LLVM assembly language parser
1207 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001208
Reid Spencer77d90192004-09-05 20:50:22 +00001209 <dt><tt><b>llvm/lib/ByteCode/</b></tt></dt>
1210 <dd>This directory holds code for reading and write LLVM bytecode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001211
Reid Spencer77d90192004-09-05 20:50:22 +00001212 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001213 different program analyses, such as Dominator Information, Call Graphs,
1214 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001215 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001216
Reid Spencer77d90192004-09-05 20:50:22 +00001217 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1218 <dd> This directory contains the source code for the LLVM to LLVM program
1219 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1220 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1221 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001222
Reid Spencer77d90192004-09-05 20:50:22 +00001223 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1224 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001225 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1226 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001227 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001228
Reid Spencer77d90192004-09-05 20:50:22 +00001229 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1230 <dd> This directory contains the major parts of the code generator: Instruction
1231 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001232
Reid Spencer77d90192004-09-05 20:50:22 +00001233 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1234 <dd> This directory contains the source level debugger library that makes
1235 it possible to instrument LLVM programs so that a debugger could identify
1236 source code locations at which the program is executing.</dd>
1237
1238 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
1239 <dd> This directory contains libraries for executing LLVM bytecode directly
1240 at runtime in both interpreted and JIT compiled fashions.</dd>
1241
1242 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1243 <dd> This directory contains the source code that corresponds to the header
1244 files located in <tt>llvm/include/Support/</tt>.</dd>
1245
1246 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1247 <dd>This directory contains the operating system abstraction layer that
1248 shields LLVM from platform-specific coding.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001249</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001250
Misha Brukman00c73d22003-11-07 19:43:14 +00001251</div>
John Criswell85ed3612003-06-12 19:34:44 +00001252
Misha Brukman00c73d22003-11-07 19:43:14 +00001253<!-- ======================================================================= -->
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001254<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1255<div class="doc_text">
1256 <p>This directory contains projects that are not strictly part of LLVM but are
1257 shipped with LLVM. This is also the directory where you should create your own
1258 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
1259 to set up your own project. See <tt>llvm/projects/Stacker</tt> for a fully
1260 functional example of a compiler front end.</p>
1261</div>
1262
1263<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001264<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001265<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001266
Misha Brukman00c73d22003-11-07 19:43:14 +00001267<p>This directory contains libraries which are compiled into LLVM bytecode and
1268used when linking programs with the GCC front end. Most of these libraries are
1269skeleton versions of real libraries; for example, libc is a stripped down
1270version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001271
Misha Brukman00c73d22003-11-07 19:43:14 +00001272<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1273end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001274
Misha Brukman00c73d22003-11-07 19:43:14 +00001275</div>
John Criswell85ed3612003-06-12 19:34:44 +00001276
Misha Brukman00c73d22003-11-07 19:43:14 +00001277<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001278<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001279<div class="doc_text">
Reid Spencer77d90192004-09-05 20:50:22 +00001280 <p>This directory contains feature and regression tests and other basic sanity
1281 checks on the LLVM infrastructure. These are intended to run quickly and cover
1282 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001283</div>
John Criswell85ed3612003-06-12 19:34:44 +00001284
Misha Brukman00c73d22003-11-07 19:43:14 +00001285<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001286<div class="doc_subsection"><a name="llvmtest"><tt>llvm-test</tt></a></div>
1287<div class="doc_text">
John Criswell3d8ba512004-12-08 17:53:54 +00001288 <p>This is not a directory in the normal llvm module; it is a separate CVS
Misha Brukmane12215f2004-11-15 23:20:51 +00001289 module that must be checked out (usually to <tt>projects/llvm-test</tt>). This
John Criswell3d8ba512004-12-08 17:53:54 +00001290 module contains a comprehensive correctness, performance, and benchmarking
1291 test
Reid Spencer77d90192004-09-05 20:50:22 +00001292 suite for LLVM. It is a separate CVS module because not every LLVM user is
John Criswell838bce52005-05-09 16:39:27 +00001293 interested in downloading or building such a comprehensive test suite. For
1294 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001295 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001296</div>
John Criswell85ed3612003-06-12 19:34:44 +00001297
Reid Spencer77d90192004-09-05 20:50:22 +00001298<!-- ======================================================================= -->
1299<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001300<div class="doc_text">
John Criswell20d2d3e2003-10-10 14:26:14 +00001301
Misha Brukman00c73d22003-11-07 19:43:14 +00001302<p>The <b>tools</b> directory contains the executables built out of the
1303libraries above, which form the main part of the user interface. You can
1304always get help for a tool by typing <tt>tool_name --help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001305following is a brief introduction to the most important tools. More detailed
1306information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001307
Misha Brukman54111c42004-01-20 00:20:17 +00001308<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001309
Reid Spencer77d90192004-09-05 20:50:22 +00001310 <dt><tt><b>bugpoint</b></tt></dt>
1311 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001312 optimization passes or code generation backends by narrowing down the
1313 given test case to the minimum number of passes and/or instructions that
1314 still cause a problem, whether it is a crash or miscompilation. See <a
1315 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001316 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001317
Reid Spencer77d90192004-09-05 20:50:22 +00001318 <dt><tt><b>llvmc</b></tt></dt>
1319 <dd>The LLVM Compiler Driver. This program can
1320 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1321 pre-processing, translation, optimization, assembly, and linking of programs
1322 all from one command line. <tt>llvmc</tt> also takes care of processing the
1323 dependent libraries found in bytecode. This reduces the need to get the
Reid Spencer079e9452004-12-08 18:00:30 +00001324 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswell8bfe6a72005-05-18 19:43:33 +00001325 note that this tool, while functional, is still experimental and not feature
1326 complete.</dd>
Reid Spencer77d90192004-09-05 20:50:22 +00001327
1328 <dt><tt><b>llvm-ar</b></tt></dt>
1329 <dd>The archiver produces an archive containing
Misha Brukman00c73d22003-11-07 19:43:14 +00001330 the given LLVM bytecode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001331 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001332
Reid Spencer77d90192004-09-05 20:50:22 +00001333 <dt><tt><b>llvm-as</b></tt></dt>
1334 <dd>The assembler transforms the human readable LLVM assembly to LLVM
1335 bytecode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001336
Reid Spencer77d90192004-09-05 20:50:22 +00001337 <dt><tt><b>llvm-dis</b></tt></dt>
1338 <dd>The disassembler transforms the LLVM bytecode to human readable
1339 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001340
Reid Spencer079e9452004-12-08 18:00:30 +00001341 <dt><tt><b>llvm-ld</b></tt></dt>
1342 <dd><tt>llvm-ld</tt> is very similar to gccld and provides a general purpose
1343 and extensible linker for LLVM. This is the linker invoked by <tt>llvmc</tt>.
1344 It allows optimization modules to be loaded so that language specific
John Criswell8bfe6a72005-05-18 19:43:33 +00001345 optimizations can be applied at link time. This tool is considered
1346 experimental.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001347
Reid Spencer77d90192004-09-05 20:50:22 +00001348 <dt><tt><b>llvm-link</b></tt></dt>
1349 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1350 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001351
Reid Spencer77d90192004-09-05 20:50:22 +00001352 <dt><tt><b>lli</b></tt></dt>
1353 <dd><tt>lli</tt> is the LLVM interpreter, which
Misha Brukman00c73d22003-11-07 19:43:14 +00001354 can directly execute LLVM bytecode (although very slowly...). In addition
1355 to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
1356 specifying <tt>-trace</tt> on the command line). Finally, for
John Criswelld9eceee2004-12-08 18:04:14 +00001357 architectures that support it (currently x86, Sparc, and PowerPC), by default,
Misha Brukman00c73d22003-11-07 19:43:14 +00001358 <tt>lli</tt> will function as a Just-In-Time compiler (if the
1359 functionality was compiled in), and will execute the code <i>much</i>
Reid Spencer77d90192004-09-05 20:50:22 +00001360 faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001361
Reid Spencer77d90192004-09-05 20:50:22 +00001362 <dt><tt><b>llc</b></tt></dt>
1363 <dd> <tt>llc</tt> is the LLVM backend compiler, which
John Criswell8bfe6a72005-05-18 19:43:33 +00001364 translates LLVM bytecode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001365 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001366
Reid Spencerd4694f92004-12-22 06:29:07 +00001367 <dt><tt><b>llvm-gcc</b></tt></dt>
1368 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend
Misha Brukman00c73d22003-11-07 19:43:14 +00001369 that has been retargeted to emit LLVM code as the machine code output. It
1370 works just like any other GCC compiler, taking the typical <tt>-c, -S, -E,
1371 -o</tt> options that are typically used. The source code for the
John Criswell8bfe6a72005-05-18 19:43:33 +00001372 <tt>llvm-gcc</tt> tool is available as a separate CVS module.
Misha Brukman54111c42004-01-20 00:20:17 +00001373 <blockquote>
1374 <dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001375 <dt><tt><b>gccas</b></tt></dt>
Reid Spencerd4694f92004-12-22 06:29:07 +00001376 <dd>This tool is invoked by the <tt>llvm-gcc</tt> frontend as the
Reid Spencer77d90192004-09-05 20:50:22 +00001377 "assembler" part of the compiler. This tool actually assembles LLVM
1378 assembly to LLVM bytecode, performs a variety of optimizations, and
1379 outputs LLVM bytecode. Thus when you invoke
Reid Spencerd4694f92004-12-22 06:29:07 +00001380 <tt>llvm-gcc -c x.c -o x.o</tt>, you are causing <tt>gccas</tt> to be
Reid Spencer77d90192004-09-05 20:50:22 +00001381 run, which writes the <tt>x.o</tt> file (which is an LLVM bytecode file
1382 that can be disassembled or manipulated just like any other bytecode
1383 file). The command line interface to <tt>gccas</tt> is designed to be
1384 as close as possible to the <b>system</b> `<tt>as</tt>' utility so that
1385 the gcc frontend itself did not have to be modified to interface to
1386 a "weird" assembler.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001387
Reid Spencer77d90192004-09-05 20:50:22 +00001388 <dt><tt><b>gccld</b></tt></dt>
1389 <dd><tt>gccld</tt> links together several LLVM bytecode files into one
1390 bytecode file and does some optimization. It is the linker invoked by
1391 the GCC frontend when multiple .o files need to be linked together.
1392 Like <tt>gccas</tt>, the command line interface of <tt>gccld</tt> is
1393 designed to match the system linker, to aid interfacing with the GCC
1394 frontend.</dd>
1395 </dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001396 </blockquote>
Reid Spencer77d90192004-09-05 20:50:22 +00001397 </dd>
John Criswell85ed3612003-06-12 19:34:44 +00001398
Reid Spencer77d90192004-09-05 20:50:22 +00001399 <dt><tt><b>opt</b></tt></dt>
Reid Spencer84f82f72006-08-28 00:34:19 +00001400 <dd><tt>opt</tt> reads LLVM bytecode, applies a series of LLVM to LLVM
1401 transformations (which are specified on the command line), and then outputs
1402 the resultant bytecode. The '<tt>opt --help</tt>' command is a good way to
1403 get a list of the program transformations available in LLVM.<br/>
1404 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
1405 LLVM bytecode file and print out the results. It is primarily useful for
1406 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001407</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001408</div>
John Criswell85ed3612003-06-12 19:34:44 +00001409
Misha Brukman00c73d22003-11-07 19:43:14 +00001410<!-- ======================================================================= -->
Reid Spencer77d90192004-09-05 20:50:22 +00001411<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001412<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001413
Misha Brukman00c73d22003-11-07 19:43:14 +00001414<p>This directory contains utilities for working with LLVM source code, and some
1415of the utilities are actually required as part of the build process because they
1416are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001417
Misha Brukman54111c42004-01-20 00:20:17 +00001418<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001419 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001420 that finds differences between code that LLC generates and code that LLI
1421 generates. This is a useful tool if you are debugging one of them,
1422 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001423 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001424
Misha Brukman54111c42004-01-20 00:20:17 +00001425 <dt><tt><b>cvsupdate</b></tt> <dd><tt>cvsupdate</tt> is a script that will
Misha Brukman00c73d22003-11-07 19:43:14 +00001426 update your CVS tree, but produce a much cleaner and more organized output
1427 than simply running <tt>`cvs -z3 up -dP'</tt> will. For example, it will group
1428 together all the new and updated files and modified files in separate
1429 sections, so you can see at a glance what has changed. If you are at the
1430 top of your LLVM CVS tree, running <tt>utils/cvsupdate</tt> is the
Chris Lattner9abd8af2006-09-07 04:19:09 +00001431 preferred way of updating the tree.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001432
Misha Brukman54111c42004-01-20 00:20:17 +00001433 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001434 syntax-highlighting files which will work with Emacs and XEmacs editors,
1435 providing syntax highlighting support for LLVM assembly files and TableGen
1436 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001437 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001438
Misha Brukman54111c42004-01-20 00:20:17 +00001439 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001440 and outputs all non-generated source files, which is useful if one wishes
1441 to do a lot of development across directories and does not want to
1442 individually find each file. One way to use it is to run, for example:
1443 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001444 tree.<br><br>
1445
Reid Spencer77d90192004-09-05 20:50:22 +00001446 <dt><tt><b>llvmgrep</b></tt></dt>
1447 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1448 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1449 line. This is a very efficient way of searching the source base for a
1450 particular regular expression.</dd>
1451
Misha Brukman54111c42004-01-20 00:20:17 +00001452 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001453 files in the current directory and then compiles and links the tool that
1454 is the first argument. For example, assuming you are in the directory
1455 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1456 simply running <tt>makellvm llc</tt> will make a build of the current
1457 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001458 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001459
Misha Brukman00c73d22003-11-07 19:43:14 +00001460 <dt><tt><b>NightlyTest.pl</b></tt> and
Misha Brukman54111c42004-01-20 00:20:17 +00001461 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman00c73d22003-11-07 19:43:14 +00001462 cron script to generate nightly status reports of the functionality of
1463 tools, and the results can be seen by following the appropriate link on
Chris Lattner9abd8af2006-09-07 04:19:09 +00001464 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001465
Misha Brukman54111c42004-01-20 00:20:17 +00001466 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001467 the tool used to generate register descriptions, instruction set
1468 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001469 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001470
Misha Brukman54111c42004-01-20 00:20:17 +00001471 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001472 syntax-highlighting files which will work with the VIM editor, providing
1473 syntax highlighting support for LLVM assembly files and TableGen
1474 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001475 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001476
Misha Brukman00c73d22003-11-07 19:43:14 +00001477</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001478
Misha Brukman00c73d22003-11-07 19:43:14 +00001479</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001480
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001481<!-- ======================================================================= -->
1482<div class="doc_subsection"><a name="win32"><tt>llvm/win32</tt></a></div>
1483<div class="doc_text">
1484 <p>This directory contains build scripts and project files for use with
1485 Visual C++. This allows developers on Windows to build LLVM without the need
John Criswell3d8ba512004-12-08 17:53:54 +00001486 for Cygwin. The contents of this directory should be considered experimental
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001487 at this time.
1488 </p>
1489</div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001490<!-- *********************************************************************** -->
1491<div class="doc_section">
1492 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1493</div>
1494<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001495
Misha Brukman00c73d22003-11-07 19:43:14 +00001496<div class="doc_text">
Chris Lattner5907d402006-08-14 20:45:25 +00001497<p>This section gives an example of using LLVM. Since we are currently
1498transitioning from llvm-gcc3 to llvm-gcc4, we include examples for both.
1499</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001500
1501<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1502from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
1503create bytecode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1504the '--emit-llvm' flag is needed to produce LLVM bytecode output. For <i>makefiles</i> and
1505<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bytecode
1506output.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001507</div>
1508
1509<!-- ======================================================================= -->
Chris Lattner9abd8af2006-09-07 04:19:09 +00001510<div class="doc_subsection"><a name="tutorial4">Example with llvm-gcc4</a></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001511
1512<div class="doc_text">
1513
1514<ol>
1515 <li>First, create a simple C file, name it 'hello.c':
1516 <pre>
1517 #include &lt;stdio.h&gt;
1518 int main() {
1519 printf("hello world\n");
1520 return 0;
1521 }
1522 </pre></li>
1523
1524 <li><p>Next, compile the C file into a native executable:</p>
1525
1526 <p><tt>% llvm-gcc hello.c -o hello</tt></p>
1527
1528 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1529 -c arguments work as usual (producing a native .s or .o file,
1530 respectively). </p>
1531
1532 <li><p>Next, compile the C file into a LLVM bytecode file:</p>
1533 <p><tt>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</tt></p>
1534
1535 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1536 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1537 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
1538 the bytecode file.</p>
1539
1540 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1541 </p></li>
1542
1543 <li><p>Run the program in both forms. To run the program, use:</p>
1544
1545 <p><tt>% ./hello</tt></p>
1546
1547 <p>and</p>
1548
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001549 <p><tt>% lli hello.bc</tt></p>
Chris Lattner5907d402006-08-14 20:45:25 +00001550
1551 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001552 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001553
1554 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1555 code:</p>
1556
Chris Lattner9abd8af2006-09-07 04:19:09 +00001557 <p><tt>% llvm-dis &lt; hello.bc | less</tt><br><br></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001558
1559 <li><p>Compile the program to native assembly using the LLC code
1560 generator:</p>
1561
1562 <p><tt>% llc hello.bc -o hello.s</tt></p>
1563
1564 <li><p>Assemble the native assembly language file into a program:</p>
1565
1566 <p><b>Solaris:</b><tt>% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native</tt></p>
1567 <p><b>Others:</b><tt>% gcc hello.s -o hello.native</tt></p>
1568
1569 <li><p>Execute the native code program:</p>
1570
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001571 <p><tt>% ./hello.native</tt></p>
Chris Lattner5907d402006-08-14 20:45:25 +00001572
1573 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1574 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001575 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001576
1577</ol>
1578
1579</div>
1580
1581<!-- ======================================================================= -->
1582<div class="doc_subsection"><a name="tutorial3">Example with llvm-gcc3</a></div>
1583
1584<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001585
Misha Brukman00c73d22003-11-07 19:43:14 +00001586<ol>
1587 <li>First, create a simple C file, name it 'hello.c':
John Criswell85ed3612003-06-12 19:34:44 +00001588 <pre>
1589 #include &lt;stdio.h&gt;
1590 int main() {
1591 printf("hello world\n");
1592 return 0;
1593 }
Misha Brukman00c73d22003-11-07 19:43:14 +00001594 </pre></li>
John Criswell85ed3612003-06-12 19:34:44 +00001595
Misha Brukman00c73d22003-11-07 19:43:14 +00001596 <li><p>Next, compile the C file into a LLVM bytecode file:</p>
Reid Spencerd4694f92004-12-22 06:29:07 +00001597 <p><tt>% llvm-gcc hello.c -o hello</tt></p>
John Criswell85ed3612003-06-12 19:34:44 +00001598
Misha Brukmanf089cdf2004-06-22 18:48:58 +00001599 <p>Note that you should have already built the tools and they have to be
1600 in your path, at least <tt>gccas</tt> and <tt>gccld</tt>.</p>
1601
Misha Brukman00c73d22003-11-07 19:43:14 +00001602 <p>This will create two result files: <tt>hello</tt> and
John Criswell85ed3612003-06-12 19:34:44 +00001603 <tt>hello.bc</tt>. The <tt>hello.bc</tt> is the LLVM bytecode that
1604 corresponds the the compiled program and the library facilities that it
1605 required. <tt>hello</tt> is a simple shell script that runs the bytecode
Chris Lattnera19a3db2004-05-01 11:40:07 +00001606 file with <tt>lli</tt>, making the result directly executable. Note that
1607 all LLVM optimizations are enabled by default, so there is no need for a
1608 "-O3" switch.</p></li>
John Criswell85ed3612003-06-12 19:34:44 +00001609
Misha Brukman00c73d22003-11-07 19:43:14 +00001610 <li><p>Run the program. To make sure the program ran, execute one of the
1611 following commands:</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001612
Misha Brukman00c73d22003-11-07 19:43:14 +00001613 <p><tt>% ./hello</tt></p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001614
Misha Brukman00c73d22003-11-07 19:43:14 +00001615 <p>or</p>
John Criswell85ed3612003-06-12 19:34:44 +00001616
Misha Brukman00c73d22003-11-07 19:43:14 +00001617 <p><tt>% lli hello.bc</tt></p></li>
John Criswell85ed3612003-06-12 19:34:44 +00001618
Misha Brukman00c73d22003-11-07 19:43:14 +00001619 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1620 code:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001621
Chris Lattner9abd8af2006-09-07 04:19:09 +00001622 <p><tt>% llvm-dis &lt; hello.bc | less</tt><br><br></li>
John Criswell85ed3612003-06-12 19:34:44 +00001623
Chris Lattnerb3bbcba2004-06-02 20:37:02 +00001624 <li><p>Compile the program to native assembly using the LLC code
1625 generator:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001626
Misha Brukman00c73d22003-11-07 19:43:14 +00001627 <p><tt>% llc hello.bc -o hello.s</tt></p>
John Criswell85ed3612003-06-12 19:34:44 +00001628
Chris Lattnerb3bbcba2004-06-02 20:37:02 +00001629 <li><p>Assemble the native assembly language file into a program:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001630
Chris Lattnerb3bbcba2004-06-02 20:37:02 +00001631 <p><b>Solaris:</b><tt>% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native</tt></p>
1632 <p><b>Others:</b><tt>% gcc hello.s -o hello.native</tt></p>
John Criswell85ed3612003-06-12 19:34:44 +00001633
Chris Lattnerb3bbcba2004-06-02 20:37:02 +00001634 <li><p>Execute the native code program:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001635
Chris Lattnerb3bbcba2004-06-02 20:37:02 +00001636 <p><tt>% ./hello.native</tt></p></li>
John Criswell85ed3612003-06-12 19:34:44 +00001637
Misha Brukman00c73d22003-11-07 19:43:14 +00001638</ol>
John Criswell85ed3612003-06-12 19:34:44 +00001639
Misha Brukman00c73d22003-11-07 19:43:14 +00001640</div>
John Criswell85ed3612003-06-12 19:34:44 +00001641
Misha Brukman00c73d22003-11-07 19:43:14 +00001642<!-- *********************************************************************** -->
1643<div class="doc_section">
1644 <a name="problems">Common Problems</a>
1645</div>
1646<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001647
Misha Brukman00c73d22003-11-07 19:43:14 +00001648<div class="doc_text">
John Criswellce760f62003-07-03 16:01:38 +00001649
Misha Brukman00c73d22003-11-07 19:43:14 +00001650<p>If you are having problems building or using LLVM, or if you have any other
1651general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1652Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001653
Misha Brukman00c73d22003-11-07 19:43:14 +00001654</div>
John Criswell85ed3612003-06-12 19:34:44 +00001655
Misha Brukman00c73d22003-11-07 19:43:14 +00001656<!-- *********************************************************************** -->
1657<div class="doc_section">
1658 <a name="links">Links</a>
1659</div>
1660<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001661
Misha Brukman00c73d22003-11-07 19:43:14 +00001662<div class="doc_text">
John Criswell85ed3612003-06-12 19:34:44 +00001663
Misha Brukman00c73d22003-11-07 19:43:14 +00001664<p>This document is just an <b>introduction</b> to how to use LLVM to do
1665some simple things... there are many more interesting and complicated things
1666that you can do that aren't documented here (but we'll gladly accept a patch
1667if you want to write something up!). For more information about LLVM, check
1668out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001669
Misha Brukman00c73d22003-11-07 19:43:14 +00001670<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001671 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1672 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1673 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001674 that Uses LLVM</a></li>
1675</ul>
1676
1677</div>
1678
1679<!-- *********************************************************************** -->
1680
1681<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001682<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001683 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1684 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1685 <a href="http://validator.w3.org/check/referer"><img
1686 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
1687
Misha Brukman142207b2003-11-22 01:30:01 +00001688 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001689 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001690 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001691 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001692</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001693</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001694</html>