Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / d966b2494de7ea9dd25870fd3693376be413e725 / . / llvm / docs / GettingStarted.html
blob: 6587987060a85e083dd2227ee7b7eaf6d6dec3cc [file] [log] [blame]
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shib65a78e2002-07-17 23:05:56 +0000[diff] [blame]3<html>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]4<head>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]6 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]10
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]11<div class="doc_title">
12 Getting Started with the LLVM System
13</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]14
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]15<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +0000[diff] [blame]19 <ol>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]20 <li><a href="#hardware">Hardware</a>
21 <li><a href="#software">Software</a>
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]22 <li><a href="#brokengcc">Broken versions of GCC</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]23 </ol></li>
John Criswell3ef61af2003-06-30 21:59:07 +0000[diff] [blame]24
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]25 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell71139f22003-07-08 20:35:59 +0000[diff] [blame]26 <ol>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]27 <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 Spencerd966b242006-07-27 05:43:30 +0000[diff] [blame^]34 <li><a href="#cross-compile">Compiling LLVM As A Cross-Compiler</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]35 <li><a href="#objfiles">The Location of LLVM Object Files</a>
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]36 <li><a href="#optionalconfig">Optional Configuration Items</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]37 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +0000[diff] [blame]38
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]39 <li><a href="#layout">Program layout</a>
40 <ol>
41 <li><a href="#cvsdir"><tt>CVS</tt> directories</a>
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]42 <li><a href="#examples"><tt>llvm/examples</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]43 <li><a href="#include"><tt>llvm/include</tt></a>
44 <li><a href="#lib"><tt>llvm/lib</tt></a>
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]45 <li><a href="#projects"><tt>llvm/projects</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]46 <li><a href="#runtime"><tt>llvm/runtime</tt></a>
47 <li><a href="#test"><tt>llvm/test</tt></a>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]48 <li><a href="#llvmtest"><tt>llvm-test</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]49 <li><a href="#tools"><tt>llvm/tools</tt></a>
50 <li><a href="#utils"><tt>llvm/utils</tt></a>
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]51 <li><a href="#win32"><tt>llvm/win32</tt></a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]52 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]53
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]54 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
55 <li><a href="#problems">Common Problems</a>
56 <li><a href="#links">Links</a>
57</ul>
58
Chris Lattner020e1fc2004-05-23 21:07:27 +0000[diff] [blame]59<div class="doc_author">
60 <p>Written by:
61 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
62 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
63 <a href="http://misha.brukman.net">Misha Brukman</a>,
64 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
65 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
66 </p>
67</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]68
69
70<!-- *********************************************************************** -->
71<div class="doc_section">
72 <a name="overview"><b>Overview</b></a>
73</div>
74<!-- *********************************************************************** -->
75
76<div class="doc_text">
77
78<p>Welcome to LLVM! In order to get started, you first need to know some
79basic information.</p>
80
81<p>First, LLVM comes in two pieces. The first piece is the LLVM suite. This
82contains all of the tools, libraries, and header files needed to use the low
83level virtual machine. It contains an assembler, disassembler, bytecode
84analyzer, and bytecode optimizer. It also contains a test suite that can be
85used to test the LLVM tools and the GCC front end.</p>
86
87<p>The second piece is the GCC front end. This component provides a version of
88GCC that compiles C and C++ code into LLVM bytecode. Currently, the GCC front
89end is a modified version of GCC 3.4 (we track the GCC 3.4 development). Once
90compiled into LLVM bytecode, a program can be manipulated with the LLVM tools
91from the LLVM suite.</p>
92
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]93<p>
94There is a third, optional piece called llvm-test. It is a suite of programs
95with a testing harness that can be used to further test LLVM's functionality
96and performance.
97</p>
98
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]99</div>
100
101<!-- *********************************************************************** -->
102<div class="doc_section">
103 <a name="quickstart"><b>Getting Started Quickly (A Summary)</b></a>
104</div>
105<!-- *********************************************************************** -->
106
107<div class="doc_text">
108
109<p>Here's the short story for getting up and running quickly with LLVM:</p>
110
111<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000[diff] [blame]112 <li>Read the documentation.</li>
113 <li>Read the documentation.</li>
114 <li>Remember that you were warned twice about reading the documentation.</li>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]115 <li>Install the GCC front end if you intend to compile C or C++:
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]116 <ol>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]117 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]118 <li><tt>gunzip --stdout cfrontend.<i>platform</i>.tar.gz | tar -xvf -</tt>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]119 </li>
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]120 <li><tt>cd cfrontend/<i>platform</i><br>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]121 ./fixheaders</tt></li>
John Criswellcfdeb5c2005-05-09 16:39:27 +0000[diff] [blame]122 <li>Add the cfrontend's "bin" directory to your PATH variable.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]123 </ol></li>
124
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]125 <li>Get the LLVM Source Code
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]126 <ul>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]127 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]128 <ol>
129 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell64f13ab2004-03-12 20:31:37 +0000[diff] [blame]130 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]131 </ol></li>
132
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]133 </ul></li>
134
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]135 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]136 <ul>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]137 <li>With the distributed files (or use <a href="#checkout">CVS</a>):
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]138 <ol>
139 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
140 <li><tt>cd llvm/projects</tt>
141 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]142 </ol></li>
143
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]144 </ul></li>
145
146
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]147 <li>Configure the LLVM Build Environment
148 <ol>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]149 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
150 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
151 Some common options:
152
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]153 <ul>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]154 <li><tt>--prefix=<i>directory</i></tt>
155 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]156 want the LLVM tools and libraries to be installed (default
157 <tt>/usr/local</tt>).</p></li>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000[diff] [blame]158 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
159 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswellcfdeb5c2005-05-09 16:39:27 +0000[diff] [blame]160 C/C++ front end installation to use with this LLVM configuration. If
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000[diff] [blame]161 not specified, the PATH will be searched.</p></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]162 <li><tt>--enable-spec2000=<i>directory</i></tt>
163 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
164 benchmarks should be available in
165 <tt><i>directory</i></tt>.</p></li>
166 </ul>
167 </ol></li>
168
169 <li>Build the LLVM Suite:
170 <ol>
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]171 <li><tt>gmake -k |&amp; tee gnumake.out
172 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
173 <li>If you get an "internal compiler error (ICE)" see <a href="#brokengcc">below</a>.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]174 </ol>
175
176</ol>
177
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000[diff] [blame]178<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]179detailed information on configuring and compiling LLVM. See <a
180href="#environment">Setting Up Your Environment</a> for tips that simplify
181working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
182Layout</a> to learn about the layout of the source code tree.</p>
183
184</div>
185
186<!-- *********************************************************************** -->
187<div class="doc_section">
188 <a name="requirements"><b>Requirements</b></a>
189</div>
190<!-- *********************************************************************** -->
191
192<div class="doc_text">
193
194<p>Before you begin to use the LLVM system, review the requirements given below.
195This may save you some trouble by knowing ahead of time what hardware and
196software you will need.</p>
197
198</div>
199
200<!-- ======================================================================= -->
201<div class="doc_subsection">
202 <a name="hardware"><b>Hardware</b></a>
203</div>
204
205<div class="doc_text">
206
207<p>LLVM is known to work on the following platforms:</p>
208
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]209<table cellpadding="3">
210<tr>
211 <th>OS</th>
212 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]213 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]214</tr>
215<tr>
216 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]217 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]218 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]219</tr>
220<tr>
221 <td>Solaris</td>
222 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]223 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]224</tr>
225<tr>
226 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]227 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]228 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]229</tr>
230<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]231 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]232 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]233 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]234</tr>
235<tr>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000[diff] [blame]236 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
237 <td>x86</td>
238 <td>GCC</td>
239
240</tr>
241<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]242 <td>Cygwin/Win32</td>
Chris Lattner9a964262006-07-21 00:06:27 +0000[diff] [blame]243 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a></sup></td>
Reid Spencera8acd822004-12-23 19:39:54 +0000[diff] [blame]244 <td>GCC 3.4.X, binutils 2.15</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]245</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000[diff] [blame]246<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000[diff] [blame]247 <td>MinGW/Win32</td>
Chris Lattner9a964262006-07-21 00:06:27 +0000[diff] [blame]248 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,<a href="#pf_8">8</a></sup></td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000[diff] [blame]249 <td>GCC 3.4.X, binutils 2.15</td>
250</tr>
251<tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000[diff] [blame]252 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]253 <td>amd64<sup><a href="#pf_3">3</a></sup></td>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000[diff] [blame]254 <td>GCC</td>
255</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]256</table>
257
258<p>LLVM has partial support for the following platforms:</p>
259
260<table>
261<tr>
262 <th>OS</th>
263 <th>Arch</th>
264 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]265</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000[diff] [blame]266<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]267 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]268 <td>x86<sup><a href="#pf_1">1</a></sup></td>
269 <td>Visual Studio .NET<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]270<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]271 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000[diff] [blame]272 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]273 <td>GCC</td>
274</tr>
275<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]276 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]277 <td>PowerPC</td>
278 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000[diff] [blame]279</tr>
John Criswell05990f32005-05-09 16:49:59 +0000[diff] [blame]280
281<tr>
282 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
283 <td>Alpha</td>
284 <td>GCC</td>
285</tr>
286<tr>
287 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
288 <td>Itanium (IA-64)</td>
289 <td>GCC</td>
290</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000[diff] [blame]291<tr>
292 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
293 <td>Itanium (IA-64)</td>
294 <td>HP aCC</td>
295</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000[diff] [blame]296</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]297
Misha Brukman77723092005-02-09 21:01:26 +0000[diff] [blame]298<p><b>Notes:</b></p>
299
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]300<div class="doc_notes">
301<ol>
302<li><a name="pf_1">Code generation supported for Pentium processors and
303up</a></li>
304<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
305<li><a name="pf_3">No native code generation</a></li>
306<li><a name="pf_4">Build is not complete: one or more tools don't link</a></li>
307<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
308<li><a name="pf_6">The port is done using the MSYS shell.
Misha Brukman77723092005-02-09 21:01:26 +0000[diff] [blame]309<a href="http://www.mingw.org/MinGWiki/">Download</a> and install
Chris Lattner9a964262006-07-21 00:06:27 +0000[diff] [blame]310bison (excl. M4.exe) and flex in that order. Build binutils-2.15 from source,
311if necessary. Bison & flex can be also grabbed from GNUWin32 sf.net project</li>
John Criswell05990f32005-05-09 16:49:59 +0000[diff] [blame]312<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Chris Lattner9a964262006-07-21 00:06:27 +0000[diff] [blame]313<li><a name="pf_8">Binutils up to post-2.17 has bug in bfd/cofflink.c
314 preventing LLVM from building correctly. Several workarounds have been
315 introduced into LLVM build system, but the bug can occur anytime in the
316 future. It's highly recommended to rebuild your current binutils with the
317 patch from <a href="http://sourceware.org/bugzilla/show_bug.cgi?id=2659">
318 Binutils bugzilla</a>, if it's wasn't already applied. </a></li>
Misha Brukman77723092005-02-09 21:01:26 +0000[diff] [blame]319</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000[diff] [blame]320</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]321
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]322<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]323mode, depending on the system (it is so large because of all the debugging
324information and the fact that the libraries are statically linked into multiple
325tools). If you do not need many of the tools and you are space-conscious,
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000[diff] [blame]326you can disable them individually in <tt>llvm/tools/Makefile</tt>. The Release
327build requires considerably less space.</p>
328
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]329<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
330guaranteed to do so. If compilation is successful, the LLVM utilities should be
331able to assemble, disassemble, analyze, and optimize LLVM bytecode. Code
332generation should work as well, although the generated native code may not work
333on your platform.</p>
334
335<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman876d5f12004-08-09 19:57:01 +0000[diff] [blame]336to work on another platform, you can download a copy of the source and <a
337href="CFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]338
339</div>
340
341<!-- ======================================================================= -->
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]342<div class="doc_subsection"><a name="software"><b>Software</b></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]343<div class="doc_text">
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]344 <p>Compiling LLVM requires that you have several software packages
345 installed. The table below lists those required packages. The Package column
346 is the usual name for the software package that LLVM depends on. The Version
347 column provides "known to work" versions of the package. The Notes column
348 describes how LLVM uses the package and provides other details.</p>
349 <table>
350 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]351
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]352 <tr>
353 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
354 <td>3.79, 3.79.1</td>
355 <td>Makefile/build processor</td>
356 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]357
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]358 <tr>
359 <td><a href="http://gcc.gnu.org">GCC</a></td>
360 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]361 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]362 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]363
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]364 <tr>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000[diff] [blame]365 <td><a href="http://www.gnu.org/software/texinfo">TeXinfo</a></td>
366 <td>4.5</td>
367 <td>For building the CFE</td>
368 </tr>
369
370 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]371 <td><a href="http://www.gnu.org/software/flex">Flex</a></td>
372 <td>2.5.4</td>
373 <td>LEX compiler</td>
374 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]375
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]376 <tr>
377 <td><a href="http://www.gnu.org/software/bison/bison.html">Bison</a></td>
Jeff Cohen71201072006-01-04 06:51:22 +0000[diff] [blame]378 <td>1.28, 1.35, 1.75, 1.875d, 2.0, or 2.1<br>(not 1.85 or 1.875)</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]379 <td>YACC compiler</td>
380 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]381
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]382 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]383 <td><a href="https://www.cvshome.org/downloads.html">CVS</a></td>
384 <td>&ge;1.11</td>
385 <td>CVS access to LLVM<sup><a href="#sf2">2</a></sup></td>
386 </tr>
387
388 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]389 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
390 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]391 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]392 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]393
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]394 <tr>
395 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
396 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]397 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]398 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]399
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]400 <tr>
401 <td><a href="http://expect.nist.gov/">expect</a></td>
402 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]403 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]404 </tr>
405
406 <tr>
407 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000[diff] [blame]408 <td>&ge;5.6.0</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]409 <td>Nightly tester, utilities</td>
410 </tr>
411
412 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]413 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
414 <td>1.4</td>
415 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]416 </tr>
417
418 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]419 <td><a href="http://www.gnu.org/software/autoconf">GNU Autoconf</a></td>
420 <td>2.59</td>
421 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
422 </tr>
423
424 <tr>
425 <td><a href="http://www.gnu.org/software/automake">GNU Automake</a></td>
426 <td>1.9.2</td>
427 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
428 </tr>
429
430 <tr>
431 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
432 <td>1.5.10</td>
433 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]434 </tr>
435
436 </table>
437
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]438 <p><b>Notes:</b></p>
439 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]440 <ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]441 <li><a name="sf3">Only the C and C++ languages are needed so there's no
442 need to build the other languages for LLVM's purposes.</a> See
443 <a href="#brokengcc">below</a> for specific version info.</li>
444 <li><a name="sf2">You only need CVS if you intend to build from the
445 latest LLVM sources. If you're working from a release distribution, you
446 don't need CVS.</a></li>
447 <li><a name="sf3">Only needed if you want to run the automated test
448 suite in the <tt>llvm/test</tt> directory.</a></li>
449 <li><a name="sf4">If you want to make changes to the configure scripts,
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]450 you will need GNU autoconf (2.59), and consequently, GNU M4 (version 1.4
Reid Spencer098fce42004-12-09 17:55:37 +0000[diff] [blame]451 or higher). You will also need automake (1.9.2). We only use aclocal
452 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]453 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000[diff] [blame]454 </div>
455
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]456 <p>Additionally, your compilation host is expected to have the usual
457 plethora of Unix utilities. Specifically:</p>
458 <ul>
459 <li><b>ar</b> - archive library builder</li>
460 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
461 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
462 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000[diff] [blame]463 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]464 <li><b>cp</b> - copy files</li>
465 <li><b>date</b> - print the current date/time </li>
466 <li><b>echo</b> - print to standard output</li>
467 <li><b>egrep</b> - extended regular expression search utility</li>
468 <li><b>etags</b> - C/C++ tag file creator for vim/emacs</li>
469 <li><b>find</b> - find files/dirs in a file system</li>
470 <li><b>grep</b> - regular expression search utility</li>
471 <li><b>gzip*</b> - gzip command for distribution generation</li>
472 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
473 <li><b>install</b> - install directories/files </li>
474 <li><b>mkdir</b> - create a directory</li>
475 <li><b>mv</b> - move (rename) files</li>
476 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000[diff] [blame]477 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000[diff] [blame]478 <li><b>sed</b> - stream editor for transforming output</li>
479 <li><b>sh</b> - Bourne shell for make build scripts</li>
480 <li><b>tar</b> - tape archive for distribution generation</li>
481 <li><b>test</b> - test things in file system</li>
482 <li><b>unzip*</b> - unzip command for distribution checking</li>
483 <li><b>zip*</b> - zip command for distribution generation</li>
484 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]485</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]486
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]487<!-- ======================================================================= -->
488<div class="doc_subsection">
489 <a name="brokengcc">Broken versions of GCC</a>
490</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]491
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]492<div class="doc_text">
493
494<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
495bugs in the compiler. In particular, several versions of GCC crash when trying
Chris Lattner29052c82006-06-16 17:20:33 +0000[diff] [blame]496to compile LLVM. We routinely use GCC 3.3.3, 3.4.0, and Apple 4.0.1
497successfully with them (however, see below). Other versions of GCC will
498probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]499here are known to not work. If you are using one of these versions, please try
500to upgrade your GCC to something more recent. If you run into a problem with a
501version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
502us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
503of GCC you are using.
504</p>
505
506<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
507problems in the STL that effectively prevent it from compiling LLVM.
508</p>
509
John Criswellfd769452004-11-23 22:06:24 +0000[diff] [blame]510<p><b>GCC 3.2.2</b>: This version of GCC fails to compile LLVM.</p>
511
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]512<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
513href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
514the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000[diff] [blame]515
Chris Lattner58247622005-02-13 22:20:49 +0000[diff] [blame]516<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
517 Cygwin does not work. Please <a href="CFEBuildInstrs.html#cygwin">upgrade
518 to a newer version</a> if possible.</p>
519<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
520 possibly others) does not compile LLVM correctly (it appears that exception
521 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
522 to a newer version of GCC.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000[diff] [blame]523<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
524 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000[diff] [blame]525<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
526 default with ENABLE_OPTIMIZED=1. To work around this, build with
527 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]528</div>
529
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]530
531
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]532<!-- *********************************************************************** -->
533<div class="doc_section">
534 <a name="starting"><b>Getting Started with LLVM</b></a>
535</div>
536<!-- *********************************************************************** -->
537
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]538<div class="doc_text">
539
540<p>The remainder of this guide is meant to get you up and running with
541LLVM and to give you some basic information about the LLVM environment.</p>
542
543<p>The later sections of this guide describe the <a
544href="#layout">general layout</a> of the the LLVM source tree, a <a
545href="#tutorial">simple example</a> using the LLVM tool chain, and <a
546href="#links">links</a> to find more information about LLVM or to get
547help via e-mail.</p>
548</div>
549
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]550<!-- ======================================================================= -->
551<div class="doc_subsection">
552 <a name="terminology">Terminology and Notation</a>
553</div>
554
555<div class="doc_text">
556
557<p>Throughout this manual, the following names are used to denote paths
558specific to the local system and working environment. <i>These are not
559environment variables you need to set but just strings used in the rest
560of this document below</i>. In any of the examples below, simply replace
561each of these names with the appropriate pathname on your local system.
562All these paths are absolute:</p>
563
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]564<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]565 <dt>SRC_ROOT
566 <dd>
567 This is the top level directory of the LLVM source tree.
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]568 <p>
569
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]570 <dt>OBJ_ROOT
571 <dd>
572 This is the top level directory of the LLVM object tree (i.e. the
573 tree where object files and compiled programs will be placed. It
574 can be the same as SRC_ROOT).
575 <p>
576
577 <dt>LLVMGCCDIR
578 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000[diff] [blame]579 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]580 <p>
581 For the pre-built GCC front end binaries, the LLVMGCCDIR is
582 <tt>cfrontend/<i>platform</i>/llvm-gcc</tt>.
583</dl>
584
585</div>
586
587<!-- ======================================================================= -->
588<div class="doc_subsection">
589 <a name="environment">Setting Up Your Environment</a>
590</div>
591
592<div class="doc_text">
593
594<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000[diff] [blame]595In order to compile and use LLVM, you may need to set some environment
596variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]597
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]598<dl>
Reid Spencer360d6b72004-12-15 00:14:01 +0000[diff] [blame]599 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bytecode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000[diff] [blame]600 <dd>[Optional] This environment variable helps LLVM linking tools find the
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]601 locations of your bytecode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000[diff] [blame]602 convenience since you can specify the paths using the -L options of the
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]603 tools and the C/C++ front-end will automatically use the bytecode files
604 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000[diff] [blame]605 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]606</dl>
607
608</div>
609
610<!-- ======================================================================= -->
611<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]612 <a name="unpack">Unpacking the LLVM Archives</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]613</div>
614
615<div class="doc_text">
616
617<p>
618If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]619can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]620suite and the LLVM GCC front end compiled for your platform. There is an
621additional test suite that is optional. Each file is a TAR archive that is
622compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]623</p>
624
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]625<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]626<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]627 <dt><tt>llvm-x.y.tar.gz</tt></dt>
628 <dd>Source release for the LLVM libraries and tools.<br/></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]629
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]630 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Chris Lattnerac648f52005-02-09 21:15:51 +0000[diff] [blame]631 <dd>Source release for the LLVM test suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000[diff] [blame]632
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]633 <dt><tt>cfrontend-x.y.source.tar.gz</tt></dt>
634 <dd>Source release of the GCC front end.<br/></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]635
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]636 <dt><tt>cfrontend-x.y.i686-redhat-linux-gnu.tar.gz</tt></dt>
637 <dd>Binary release of the GCC front end for Linux/x86.<br/></dd>
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]638
Chris Lattner499abb52006-04-20 05:08:23 +0000[diff] [blame]639 <dt><tt>llvm-gcc4-x.y.source.tar.gz</tt></dt>
640 <dd>Source release of the llvm-gcc4 front end. See README.LLVM in the root
641 directory for build instructions.<br/></dd>
642
643 <dt><tt>llvm-gcc4-x.y.powerpc-apple-darwin8.6.0.tar.gz</tt></dt>
644 <dd>Binary release of the llvm-gcc4 front end for MacOS X/PowerPC.<br/></dd>
645
646 <dt><tt>llvm-gcc4-x.y.i686-apple-darwin8.6.1.tar.gz</tt></dt>
647 <dd>Binary release of the llvm-gcc4 front end for MacOS X/X86.<br/></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]648</dl>
649
Jim Laskey34ea26a2006-06-16 23:20:21 +0000[diff] [blame]650<p>It is also possible to download the sources of the llvm-gcc4 front end from
651a read-only subversion mirror at svn://anonsvn.opensource.apple.com/svn/llvm.
652</p>
653
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]654</div>
655
656<!-- ======================================================================= -->
657<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]658 <a name="checkout">Checkout LLVM from CVS</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]659</div>
660
661<div class="doc_text">
662
663<p>If you have access to our CVS repository, you can get a fresh copy of
664the entire source code. All you need to do is check it out from CVS as
665follows:</p>
666
667<ul>
668<li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
669 <li><tt>cvs -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm login</tt>
670 <li>Hit the return key when prompted for the password.
671 <li><tt>cvs -z3 -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co
672 llvm</tt>
673</ul>
674
675<p>This will create an '<tt>llvm</tt>' directory in the current
676directory and fully populate it with the LLVM source code, Makefiles,
677test directories, and local copies of documentation files.</p>
678
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]679<p>If you want to get a specific release (as opposed to the most recent
680revision), you can specify a label. The following releases have the following
Misha Brukmand4528ea2005-02-02 18:01:57 +0000[diff] [blame]681labels:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]682
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]683<ul>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000[diff] [blame]684<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000[diff] [blame]685<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000[diff] [blame]686<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]687<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000[diff] [blame]688<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000[diff] [blame]689<li>Release 1.2: <b>RELEASE_12</b></li>
690<li>Release 1.1: <b>RELEASE_11</b></li>
691<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]692</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]693
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]694<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
695you get it from the CVS repository:</p>
696<pre>
697 cd llvm/projects
698 cvs -z3 -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co llvm-test
699</pre>
700<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000[diff] [blame]701configured by the LLVM configure script as well as automatically updated when
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]702you run <tt>cvs update</tt>.</p>
703
Tanya Lattnerfb762912006-04-20 04:35:34 +0000[diff] [blame]704<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 Brukmanc1aac032004-05-12 19:25:59 +0000[diff] [blame]705
Chris Lattner3337c822004-06-28 17:14:01 +0000[diff] [blame]706<pre>
707 cvs -z3 -d :pserver:anon@llvm-cvs.cs.uiuc.edu:/var/cvs/llvm co llvm-gcc
Misha Brukmanc1aac032004-05-12 19:25:59 +0000[diff] [blame]708</pre>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]709
Chris Lattner3337c822004-06-28 17:14:01 +0000[diff] [blame]710<p>Please note that you must follow <a href="CFEBuildInstrs.html">these
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]711instructions</a> to successfully build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000[diff] [blame]712
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]713</div>
714
715<!-- ======================================================================= -->
716<div class="doc_subsection">
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]717 <a name="installcf">Install the GCC Front End</a>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]718</div>
719
720<div class="doc_text">
721
722<p>Before configuring and compiling the LLVM suite, you need to extract the LLVM
723GCC front end from the binary distribution. It is used for building the
724bytecode libraries later used by the GCC front end for linking programs, and its
725location must be specified when the LLVM suite is configured.</p>
726
727<p>To install the GCC front end, do the following:</p>
728
729<ol>
730 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]731 <li><tt>gunzip --stdout cfrontend-<i>version</i>.<i>platform</i>.tar.gz | tar -xvf
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]732 -</tt></li>
733</ol>
734
John Criswelldfe6a862004-12-10 15:51:16 +0000[diff] [blame]735<p>Next, you will need to fix your system header files:</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]736
John Criswell64f13ab2004-03-12 20:31:37 +0000[diff] [blame]737<p><tt>cd cfrontend/<i>platform</i><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]738 ./fixheaders</tt></p>
739
740<p>The binary versions of the GCC front end may not suit all of your needs. For
741example, the binary distribution may include an old version of a system header
742file, not "fix" a header file that needs to be fixed for GCC, or it may be
743linked with libraries not available on your system.</p>
744
745<p>In cases like these, you may want to try <a
746href="CFEBuildInstrs.html">building the GCC front end from source.</a> This is
747not for the faint of heart, so be forewarned.</p>
748
749</div>
750
751<!-- ======================================================================= -->
752<div class="doc_subsection">
753 <a name="config">Local LLVM Configuration</a>
754</div>
755
756<div class="doc_text">
757
758<p>Once checked out from the CVS repository, the LLVM suite source code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]759configured via the <tt>configure</tt> script. This script sets variables in the
760various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
761<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
762the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]763
764<p>The following environment variables are used by the <tt>configure</tt>
765script to configure the build system:</p>
766
Reid Spencerc3c4c4f2004-11-01 08:19:36 +0000[diff] [blame]767<table>
768 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]769 <tr>
770 <td>CC</td>
771 <td>Tells <tt>configure</tt> which C compiler to use. By default,
772 <tt>configure</tt> will look for the first GCC C compiler in
773 <tt>PATH</tt>. Use this variable to override
774 <tt>configure</tt>'s default behavior.</td>
775 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]776 <tr>
777 <td>CXX</td>
778 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
779 <tt>configure</tt> will look for the first GCC C++ compiler in
780 <tt>PATH</tt>. Use this variable to override
781 <tt>configure</tt>'s default behavior.</td>
782 </tr>
783</table>
784
785<p>The following options can be used to set or enable LLVM specific options:</p>
786
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]787<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000[diff] [blame]788 <dt><i>--with-llvmgccdir</i></dt>
789 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
790 The value of this option should specify the full pathname of the C/C++ Front
791 End to be used. If this option is not provided, the PATH will be searched for
792 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
793 be inferred from the path found. If the option is not given, and no llvm-gcc
794 can be found in the path then a warning will be produced by
795 <tt>configure</tt> indicating this situation. LLVM may still be built with
796 the <tt>tools-only</tt> target but attempting to build the runtime libraries
797 will fail as these libraries require llvm-gcc and llvm-g++. See
798 <a href="#installcf">Install the GCC Front End</a> for details on installing
799 the C/C++ Front End. See
800 <a href="CFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
801 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]802 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]803 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]804 found. Use this if you have multiple tcl installations on your machine and you
805 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
806 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]807 option, the LLVM configure script will search for the tcl 8.4 and 8.3
808 releases.
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]809 <p></p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]810 </dd>
811 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]812 <dd>
813 Enables optimized compilation by default (debugging symbols are removed
814 and GCC optimization flags are enabled). The default is to use an
815 unoptimized build (also known as a debug build).
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]816 <p></p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]817 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +0000[diff] [blame]818 <dt><i>--enable-debug-runtime</i></dt>
819 <dd>
820 Enables debug symbols in the runtime libraries. The default is to strip
821 debug symbols from the runtime libraries.
822 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]823 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]824 <dd>
John Criswell86a3a482003-12-18 16:43:17 +0000[diff] [blame]825 Compile the Just In Time (JIT) compiler functionality. This is not
826 available
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]827 on all platforms. The default is dependent on platform, so it is best
828 to explicitly enable it if you want it.
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]829 <p></p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]830 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000[diff] [blame]831 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
832 <dd>Controls which targets will be built and linked into llc. The default
833 value for <tt>target_options</tt> is "all" which builds and links all
834 available targets. The value "host-only" can be specified to build only a
835 native compiler (no cross-compiler targets available). The "native" target is
836 selected as the target of the build host. You can also specify a comma
837 separated list of target names that you want available in llc. The target
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]838 names use all lower case. The current set of targets is: <br/>
Reid Spencer1e195bd2005-04-22 17:58:03 +0000[diff] [blame]839 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
840 <p></p></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]841 <dt><i>--enable-doxygen</i></dt>
842 <dd>Look for the doxygen program and enable construction of doxygen based
843 documentation from the source code. This is disabled by default because
844 generating the documentation can take a long time and producess 100s of
845 megabytes of output.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]846</dl>
847
848<p>To configure LLVM, follow these steps:</p>
849
850<ol>
851 <li>Change directory into the object root directory:
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]852 <br>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]853 <tt>cd <i>OBJ_ROOT</i></tt>
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]854 <p>
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]855
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]856 <li>Run the <tt>configure</tt> script located in the LLVM source tree:
857 <br>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]858 <tt><i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</tt>
John Criswellf531f312003-10-27 18:18:16 +0000[diff] [blame]859 <p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]860</ol>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]861
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]862</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]863
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]864<!-- ======================================================================= -->
865<div class="doc_subsection">
866 <a name="compile">Compiling the LLVM Suite Source Code</a>
867</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]868
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]869<div class="doc_text">
John Criswell71139f22003-07-08 20:35:59 +0000[diff] [blame]870
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]871<p>Once you have configured LLVM, you can build it. There are three types of
872builds:</p>
John Criswell71139f22003-07-08 20:35:59 +0000[diff] [blame]873
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]874<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]875 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]876 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]877 These builds are the default when one types <tt>gmake</tt> (unless the
878 <tt>--enable-optimized</tt> option was used during configuration). The
879 build system will compile the tools and libraries with debugging
880 information.
881 <p>
882
883 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]884 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]885 These builds are enabled with the <tt>--enable-optimized</tt> option to
886 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
887 <tt>gmake</tt> command line. For these builds, the build system will
888 compile the tools and libraries with GCC optimizations enabled and strip
889 debugging information from the libraries and executables it generates.
890 <p>
891
892 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]893 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]894 These builds are for use with profiling. They compile profiling
895 information into the code for use with programs like <tt>gprof</tt>.
896 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
897 on the <tt>gmake</tt> command line.
898</dl>
John Criswell3ef61af2003-06-30 21:59:07 +0000[diff] [blame]899
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]900<p>Once you have LLVM configured, you can build it by entering the
901<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]902
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]903<p><tt>gmake</tt></p>
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]904
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]905<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]906are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000[diff] [blame]907
908<p>
909If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]910the parallel build options provided by GNU Make. For example, you could use the
911command:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]912
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]913<p><tt>gmake -j2</tt></p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]914
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]915<p>There are several special targets which are useful when working with the LLVM
916source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]917
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]918<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]919 <dt><tt>gmake clean</tt>
920 <dd>
921 Removes all files generated by the build. This includes object files,
922 generated C/C++ files, libraries, and executables.
923 <p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]924
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]925 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]926 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +0000[diff] [blame]927 Removes everything that <tt>gmake clean</tt> does, but also removes files
928 generated by <tt>configure</tt>. It attempts to return the source tree to the
929 original state in which it was shipped.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]930 <p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]931
Misha Brukman62a2c1f2004-08-23 20:25:33 +0000[diff] [blame]932 <dt><tt>gmake install</tt>
933 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]934 Installs LLVM header files, libraries, tools, and documentation in a
935 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]936 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
937 defaults to <tt>/usr/local</tt>.
Misha Brukman62a2c1f2004-08-23 20:25:33 +0000[diff] [blame]938 <p>
939
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]940 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]941 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +0000[diff] [blame]942 Assuming you built LLVM into $OBJDIR, when this command is run, it will
943 install bytecode libraries into the GCC front end's bytecode library
944 directory. If you need to update your bytecode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +0000[diff] [blame]945 this is the target to use once you've built them.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]946 <p>
947</dl>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]948
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]949<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
950details on these <tt>make</tt> targets and descriptions of other targets
951available.</p>
952
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]953<p>It is also possible to override default values from <tt>configure</tt> by
954declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]955
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]956<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]957 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
958 <dd>
959 Perform a Release (Optimized) build.
960 <p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]961
Reid Spencer3dc3ea72006-04-09 23:45:38 +0000[diff] [blame]962 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +0000[diff] [blame]963 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +0000[diff] [blame]964 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner0f546dd2006-03-21 01:10:57 +0000[diff] [blame]965 <p>
966
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]967 <dt><tt>gmake ENABLE_PROFILING=1</tt>
968 <dd>
969 Perform a Profiling build.
970 <p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]971
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]972 <dt><tt>gmake VERBOSE=1</tt>
973 <dd>
974 Print what <tt>gmake</tt> is doing on standard output.
975 <p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]976
977 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
978 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]979 the standard output. This also implies <tt>VERBOSE=1</tt>.
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]980 <p></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]981</dl>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]982
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]983<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
984it and any subdirectories that it contains. Entering any directory inside the
985LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
986that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]987
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]988</div>
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]989
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]990<!-- ======================================================================= -->
991<div class="doc_subsection">
Reid Spencerd966b242006-07-27 05:43:30 +0000[diff] [blame^]992 <a name="cross-compile">Compiling LLVM As A Cross-compiler</a>
993</div>
994
995<div class="doc_text">
996 <p>LLVM can be built as a cross-compiler, however some additional steps are
997 required.<sup><a href="#ccn_1">1</a></sup> To build a cross-compiler, use
998 these instructions:</p>
999 <ol>
1000 <li>Configure and build LLVM Suite as a native compiler. You will need
1001 just <tt>TableGen</tt> from that build.
1002 <ul>
1003 <li>If you have <tt>$LLVM_OBJ_ROOT=$LLVM_SRC_ROOT</tt> just execute
1004 <tt>make -C utils/TableGen</tt> after configuring.</li>
1005 <li>Otherwise you will need to monitor building process and terminate
1006 it just after <tt>TableGen</tt> was built.</li>
1007 </ul>
1008 </li>
1009 <li>Copy the TableGen binary to somewhere safe (out of your build tree).
1010 </li>
1011 <li>Configure LLVM to build as a cross-compiler. To do this, supply the
1012 configure script with <tt>--build</tt> and <tt>--host</tt> options that
1013 are different. The values of these options must be legal target triples and
1014 should specify a processor for which LLVM supports code generation.</li>
1015 <li>Put the saved <tt>TableGen</tt> executable into the
1016 into <tt>$LLVM_OBJ_ROOT/{BUILD_TYPE}/bin</tt> directory (e.g. into
1017 <tt>.../Release/bin</tt> for a Release build).</li>
1018 <li>Build LLVM as usual.</li>
1019 </ol>
1020 <p><b>Notes:</b></p>
1021 <div class="doc_notes">
1022 <ol>
1023 <li><a name="ccn_1">Cross-compiling</a> was tested only with Linux as
1024 build platform and Windows as host using mingw32 cross-compiler. Other
1025 combinations have not been tested.</li>
1026 </ol>
1027 </div>
1028</div>
1029
1030<!-- ======================================================================= -->
1031<div class="doc_subsection">
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1032 <a name="objfiles">The Location of LLVM Object Files</a>
1033</div>
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]1034
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1035<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1036
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1037<p>The LLVM build system is capable of sharing a single LLVM source tree among
1038several LLVM builds. Hence, it is possible to build LLVM for several different
1039platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1040
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1041<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1042
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1043<ul>
1044 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1045
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1046 <p><tt>cd <i>OBJ_ROOT</i></tt></p></li>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1047
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1048 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1049 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1050
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1051 <p><tt><i>SRC_ROOT</i>/configure</tt></p></li>
1052</ul>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1053
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1054<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1055named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1056
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1057<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1058 <dt>Debug Builds
1059 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1060 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1061 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1062 <dd><tt><i>OBJ_ROOT</i>/Debug/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1063 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1064 <dd><tt><i>OBJ_ROOT</i>/Debug/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1065 </dl>
1066 <p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1067
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1068 <dt>Release Builds
1069 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1070 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1071 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1072 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1073 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1074 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1075 </dl>
1076 <p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1077
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1078 <dt>Profile Builds
1079 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1080 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1081 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1082 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1083 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1084 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1085 </dl>
1086</dl>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1087
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1088</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +0000[diff] [blame]1089
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]1090<!-- ======================================================================= -->
1091<div class="doc_subsection">
1092 <a name="optionalconfig">Optional Configuration Items</a>
1093</div>
1094
1095<div class="doc_text">
1096
1097<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]1098If you're running on a Linux system that supports the "<a
Reid Spencerdfcf7902004-12-08 16:51:31 +0000[diff] [blame]1099 href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">
1100 binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]1101module, and you have root access on the system, you can set your system up to
1102execute LLVM bytecode files directly. To do this, use commands like this (the
1103first command may not be required if you are already using the module):</p>
1104
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]1105<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]1106<pre>
1107 $ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]1108 $ echo ':llvm:M::llvm::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]1109 $ chmod u+x hello.bc (if needed)
1110 $ ./hello.bc
1111</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000[diff] [blame]1112</div>
Chris Lattner998c0672004-03-25 20:38:40 +0000[diff] [blame]1113
1114<p>
1115This allows you to execute LLVM bytecode files directly. Thanks to Jack
1116Cummings for pointing this out!
1117</p>
1118
1119</div>
1120
1121
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1122<!-- *********************************************************************** -->
1123<div class="doc_section">
1124 <a name="layout"><b>Program Layout</b></a>
1125</div>
1126<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1127
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1128<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1129
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1130<p>One useful source of information about the LLVM source base is the LLVM <a
John Criswell64f13ab2004-03-12 20:31:37 +0000[diff] [blame]1131href="http://www.doxygen.org">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]1132href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1133The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1134
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1135</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1136
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1137<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1138<div class="doc_subsection"><a name="cvsdir"><tt>CVS</tt> directories</a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1139<div class="doc_text">
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1140<p>Every directory checked out of CVS will contain a <tt>CVS</tt> directory; for
1141the most part these can just be ignored.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]1142</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1143
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]1144<!-- ======================================================================= -->
1145<div class="doc_subsection"><a name="examples"><tt>llvm/examples</tt></a></div>
1146<div class="doc_text">
1147 <p>This directory contains some simple examples of how to use the LLVM IR and
1148 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1149</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1150
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1151<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1152<div class="doc_subsection"><a name="include"><tt>llvm/include</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1153<div class="doc_text">
1154
1155<p>This directory contains public header files exported from the LLVM
1156library. The three main subdirectories of this directory are:</p>
1157
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1158<dl>
1159 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1160 <dd>This directory contains all of the LLVM specific header files. This
1161 directory also has subdirectories for different portions of LLVM:
1162 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1163 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1164
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1165 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1166 <dd>This directory contains generic support libraries that are provided with
1167 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1168 and a Command Line option processing library store their header files here.
1169 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1170
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1171 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1172 <dd>This directory contains header files configured by the <tt>configure</tt>
1173 script. They wrap "standard" UNIX and C header files. Source code can
1174 include these header files which automatically take care of the conditional
1175 #includes that the <tt>configure</tt> script generates.</dd>
1176</dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1177</div>
1178
1179<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1180<div class="doc_subsection"><a name="lib"><tt>llvm/lib</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1181<div class="doc_text">
1182
1183<p>This directory contains most of the source files of the LLVM system. In LLVM,
1184almost all code exists in libraries, making it very easy to share code among the
1185different <a href="#tools">tools</a>.</p>
1186
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1187<dl>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1188 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1189 <dd> This directory holds the core LLVM source files that implement core
1190 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1191
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1192 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1193 <dd>This directory holds the source code for the LLVM assembly language parser
1194 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1195
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1196 <dt><tt><b>llvm/lib/ByteCode/</b></tt></dt>
1197 <dd>This directory holds code for reading and write LLVM bytecode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1198
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1199 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1200 different program analyses, such as Dominator Information, Call Graphs,
1201 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1202 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1203
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1204 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1205 <dd> This directory contains the source code for the LLVM to LLVM program
1206 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1207 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1208 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1209
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1210 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1211 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +0000[diff] [blame]1212 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1213 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]1214 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1215
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1216 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1217 <dd> This directory contains the major parts of the code generator: Instruction
1218 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1219
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1220 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1221 <dd> This directory contains the source level debugger library that makes
1222 it possible to instrument LLVM programs so that a debugger could identify
1223 source code locations at which the program is executing.</dd>
1224
1225 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
1226 <dd> This directory contains libraries for executing LLVM bytecode directly
1227 at runtime in both interpreted and JIT compiled fashions.</dd>
1228
1229 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
1230 <dd> This directory contains the source code that corresponds to the header
1231 files located in <tt>llvm/include/Support/</tt>.</dd>
1232
1233 <dt><tt><b>llvm/lib/System/</b></tt></dt>
1234 <dd>This directory contains the operating system abstraction layer that
1235 shields LLVM from platform-specific coding.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1236</dl>
John Criswell3ef61af2003-06-30 21:59:07 +0000[diff] [blame]1237
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1238</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1239
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1240<!-- ======================================================================= -->
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]1241<div class="doc_subsection"><a name="projects"><tt>llvm/projects</tt></a></div>
1242<div class="doc_text">
1243 <p>This directory contains projects that are not strictly part of LLVM but are
1244 shipped with LLVM. This is also the directory where you should create your own
1245 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
1246 to set up your own project. See <tt>llvm/projects/Stacker</tt> for a fully
1247 functional example of a compiler front end.</p>
1248</div>
1249
1250<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1251<div class="doc_subsection"><a name="runtime"><tt>llvm/runtime</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1252<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1253
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1254<p>This directory contains libraries which are compiled into LLVM bytecode and
1255used when linking programs with the GCC front end. Most of these libraries are
1256skeleton versions of real libraries; for example, libc is a stripped down
1257version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1258
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1259<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1260end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1261
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1262</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1263
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1264<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1265<div class="doc_subsection"><a name="test"><tt>llvm/test</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1266<div class="doc_text">
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1267 <p>This directory contains feature and regression tests and other basic sanity
1268 checks on the LLVM infrastructure. These are intended to run quickly and cover
1269 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1270</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1271
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1272<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1273<div class="doc_subsection"><a name="llvmtest"><tt>llvm-test</tt></a></div>
1274<div class="doc_text">
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]1275 <p>This is not a directory in the normal llvm module; it is a separate CVS
Misha Brukmanb4bd8de2004-11-15 23:20:51 +0000[diff] [blame]1276 module that must be checked out (usually to <tt>projects/llvm-test</tt>). This
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]1277 module contains a comprehensive correctness, performance, and benchmarking
1278 test
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1279 suite for LLVM. It is a separate CVS module because not every LLVM user is
John Criswellcfdeb5c2005-05-09 16:39:27 +0000[diff] [blame]1280 interested in downloading or building such a comprehensive test suite. For
1281 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1282 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1283</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1284
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1285<!-- ======================================================================= -->
1286<div class="doc_subsection"><a name="tools"><tt>llvm/tools</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1287<div class="doc_text">
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]1288
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1289<p>The <b>tools</b> directory contains the executables built out of the
1290libraries above, which form the main part of the user interface. You can
1291always get help for a tool by typing <tt>tool_name --help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +0000[diff] [blame]1292following is a brief introduction to the most important tools. More detailed
1293information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +0000[diff] [blame]1294
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1295<dl>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1296 <dt><tt><b>analyze</b></tt></dt>
1297 <dd><tt>analyze</tt> is used to run a specific
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1298 analysis on an input LLVM bytecode file and print out the results. It is
1299 primarily useful for debugging analyses, or familiarizing yourself with
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1300 what an analysis does.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1301
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1302 <dt><tt><b>bugpoint</b></tt></dt>
1303 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1304 optimization passes or code generation backends by narrowing down the
1305 given test case to the minimum number of passes and/or instructions that
1306 still cause a problem, whether it is a crash or miscompilation. See <a
1307 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1308 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1309
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1310 <dt><tt><b>llvmc</b></tt></dt>
1311 <dd>The LLVM Compiler Driver. This program can
1312 be configured to utilize both LLVM and non-LLVM compilation tools to enable
1313 pre-processing, translation, optimization, assembly, and linking of programs
1314 all from one command line. <tt>llvmc</tt> also takes care of processing the
1315 dependent libraries found in bytecode. This reduces the need to get the
Reid Spencer92815e52004-12-08 18:00:30 +0000[diff] [blame]1316 traditional <tt>-l&lt;name&gt;</tt> options right on the command line. Please
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]1317 note that this tool, while functional, is still experimental and not feature
1318 complete.</dd>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1319
1320 <dt><tt><b>llvm-ar</b></tt></dt>
1321 <dd>The archiver produces an archive containing
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1322 the given LLVM bytecode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1323 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1324
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1325 <dt><tt><b>llvm-as</b></tt></dt>
1326 <dd>The assembler transforms the human readable LLVM assembly to LLVM
1327 bytecode.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1328
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1329 <dt><tt><b>llvm-dis</b></tt></dt>
1330 <dd>The disassembler transforms the LLVM bytecode to human readable
1331 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1332
Reid Spencer92815e52004-12-08 18:00:30 +0000[diff] [blame]1333 <dt><tt><b>llvm-ld</b></tt></dt>
1334 <dd><tt>llvm-ld</tt> is very similar to gccld and provides a general purpose
1335 and extensible linker for LLVM. This is the linker invoked by <tt>llvmc</tt>.
1336 It allows optimization modules to be loaded so that language specific
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]1337 optimizations can be applied at link time. This tool is considered
1338 experimental.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +0000[diff] [blame]1339
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1340 <dt><tt><b>llvm-link</b></tt></dt>
1341 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1342 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1343
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1344 <dt><tt><b>lli</b></tt></dt>
1345 <dd><tt>lli</tt> is the LLVM interpreter, which
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1346 can directly execute LLVM bytecode (although very slowly...). In addition
1347 to a simple interpreter, <tt>lli</tt> also has a tracing mode (entered by
1348 specifying <tt>-trace</tt> on the command line). Finally, for
John Criswell945f8022004-12-08 18:04:14 +0000[diff] [blame]1349 architectures that support it (currently x86, Sparc, and PowerPC), by default,
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1350 <tt>lli</tt> will function as a Just-In-Time compiler (if the
1351 functionality was compiled in), and will execute the code <i>much</i>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1352 faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +0000[diff] [blame]1353
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1354 <dt><tt><b>llc</b></tt></dt>
1355 <dd> <tt>llc</tt> is the LLVM backend compiler, which
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]1356 translates LLVM bytecode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1357 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +0000[diff] [blame]1358
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]1359 <dt><tt><b>llvm-gcc</b></tt></dt>
1360 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1361 that has been retargeted to emit LLVM code as the machine code output. It
1362 works just like any other GCC compiler, taking the typical <tt>-c, -S, -E,
1363 -o</tt> options that are typically used. The source code for the
John Criswelle1a81202005-05-18 19:43:33 +0000[diff] [blame]1364 <tt>llvm-gcc</tt> tool is available as a separate CVS module.
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1365 <blockquote>
1366 <dl>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1367 <dt><tt><b>gccas</b></tt></dt>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]1368 <dd>This tool is invoked by the <tt>llvm-gcc</tt> frontend as the
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1369 "assembler" part of the compiler. This tool actually assembles LLVM
1370 assembly to LLVM bytecode, performs a variety of optimizations, and
1371 outputs LLVM bytecode. Thus when you invoke
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]1372 <tt>llvm-gcc -c x.c -o x.o</tt>, you are causing <tt>gccas</tt> to be
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1373 run, which writes the <tt>x.o</tt> file (which is an LLVM bytecode file
1374 that can be disassembled or manipulated just like any other bytecode
1375 file). The command line interface to <tt>gccas</tt> is designed to be
1376 as close as possible to the <b>system</b> `<tt>as</tt>' utility so that
1377 the gcc frontend itself did not have to be modified to interface to
1378 a "weird" assembler.</dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1379
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1380 <dt><tt><b>gccld</b></tt></dt>
1381 <dd><tt>gccld</tt> links together several LLVM bytecode files into one
1382 bytecode file and does some optimization. It is the linker invoked by
1383 the GCC frontend when multiple .o files need to be linked together.
1384 Like <tt>gccas</tt>, the command line interface of <tt>gccld</tt> is
1385 designed to match the system linker, to aid interfacing with the GCC
1386 frontend.</dd>
1387 </dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1388 </blockquote>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1389 </dd>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1390
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1391 <dt><tt><b>opt</b></tt></dt>
1392 <dd><tt>opt</tt> reads LLVM bytecode, applies a
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1393 series of LLVM to LLVM transformations (which are specified on the command
1394 line), and then outputs the resultant bytecode. The '<tt>opt --help</tt>'
1395 command is a good way to get a list of the program transformations
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1396 available in LLVM.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1397</dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1398</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1399
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1400<!-- ======================================================================= -->
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1401<div class="doc_subsection"><a name="utils"><tt>llvm/utils</tt></a></div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1402<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1403
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1404<p>This directory contains utilities for working with LLVM source code, and some
1405of the utilities are actually required as part of the build process because they
1406are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1407
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1408<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1409 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1410 that finds differences between code that LLC generates and code that LLI
1411 generates. This is a useful tool if you are debugging one of them,
1412 assuming that the other generates correct output. For the full user
1413 manual, run <tt>`perldoc codegen-diff'</tt>.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1414
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1415 <dt><tt><b>cvsupdate</b></tt> <dd><tt>cvsupdate</tt> is a script that will
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1416 update your CVS tree, but produce a much cleaner and more organized output
1417 than simply running <tt>`cvs -z3 up -dP'</tt> will. For example, it will group
1418 together all the new and updated files and modified files in separate
1419 sections, so you can see at a glance what has changed. If you are at the
1420 top of your LLVM CVS tree, running <tt>utils/cvsupdate</tt> is the
1421 preferred way of updating the tree.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1422
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1423 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1424 syntax-highlighting files which will work with Emacs and XEmacs editors,
1425 providing syntax highlighting support for LLVM assembly files and TableGen
1426 description files. For information on how to use the syntax files, consult
1427 the <tt>README</tt> file in that directory.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1428
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1429 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1430 and outputs all non-generated source files, which is useful if one wishes
1431 to do a lot of development across directories and does not want to
1432 individually find each file. One way to use it is to run, for example:
1433 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
1434 tree.<p>
1435
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1436 <dt><tt><b>llvmgrep</b></tt></dt>
1437 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1438 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1439 line. This is a very efficient way of searching the source base for a
1440 particular regular expression.</dd>
1441
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1442 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1443 files in the current directory and then compiles and links the tool that
1444 is the first argument. For example, assuming you are in the directory
1445 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1446 simply running <tt>makellvm llc</tt> will make a build of the current
1447 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
1448 causing a re-linking of LLC.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1449
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1450 <dt><tt><b>NightlyTest.pl</b></tt> and
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1451 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1452 cron script to generate nightly status reports of the functionality of
1453 tools, and the results can be seen by following the appropriate link on
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]1454 the <a href="http://llvm.org/">LLVM homepage</a>.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1455
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1456 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1457 the tool used to generate register descriptions, instruction set
1458 descriptions, and even assemblers from common TableGen description
1459 files.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1460
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1461 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1462 syntax-highlighting files which will work with the VIM editor, providing
1463 syntax highlighting support for LLVM assembly files and TableGen
1464 description files. For information on how to use the syntax files, consult
1465 the <tt>README</tt> file in that directory.<p>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1466
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1467</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1468
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1469</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1470
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]1471<!-- ======================================================================= -->
1472<div class="doc_subsection"><a name="win32"><tt>llvm/win32</tt></a></div>
1473<div class="doc_text">
1474 <p>This directory contains build scripts and project files for use with
1475 Visual C++. This allows developers on Windows to build LLVM without the need
John Criswell6ab273c2004-12-08 17:53:54 +0000[diff] [blame]1476 for Cygwin. The contents of this directory should be considered experimental
Reid Spencer5be4f042004-12-08 16:18:26 +0000[diff] [blame]1477 at this time.
1478 </p>
1479</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1480<!-- *********************************************************************** -->
1481<div class="doc_section">
1482 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
1483</div>
1484<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +0000[diff] [blame]1485
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1486<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1487
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1488<ol>
1489 <li>First, create a simple C file, name it 'hello.c':
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1490 <pre>
1491 #include &lt;stdio.h&gt;
1492 int main() {
1493 printf("hello world\n");
1494 return 0;
1495 }
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1496 </pre></li>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1497
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1498 <li><p>Next, compile the C file into a LLVM bytecode file:</p>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000[diff] [blame]1499 <p><tt>% llvm-gcc hello.c -o hello</tt></p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1500
Misha Brukman6c2cf082004-06-22 18:48:58 +0000[diff] [blame]1501 <p>Note that you should have already built the tools and they have to be
1502 in your path, at least <tt>gccas</tt> and <tt>gccld</tt>.</p>
1503
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1504 <p>This will create two result files: <tt>hello</tt> and
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1505 <tt>hello.bc</tt>. The <tt>hello.bc</tt> is the LLVM bytecode that
1506 corresponds the the compiled program and the library facilities that it
1507 required. <tt>hello</tt> is a simple shell script that runs the bytecode
Chris Lattner15a041c2004-05-01 11:40:07 +0000[diff] [blame]1508 file with <tt>lli</tt>, making the result directly executable. Note that
1509 all LLVM optimizations are enabled by default, so there is no need for a
1510 "-O3" switch.</p></li>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1511
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1512 <li><p>Run the program. To make sure the program ran, execute one of the
1513 following commands:</p>
John Criswell0c951c62003-06-11 20:46:40 +0000[diff] [blame]1514
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1515 <p><tt>% ./hello</tt></p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1516
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1517 <p>or</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1518
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1519 <p><tt>% lli hello.bc</tt></p></li>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1520
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1521 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1522 code:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1523
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1524 <p><tt>% llvm-dis &lt; hello.bc | less</tt><p></li>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1525
Chris Lattner03793512004-06-02 20:37:02 +0000[diff] [blame]1526 <li><p>Compile the program to native assembly using the LLC code
1527 generator:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1528
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1529 <p><tt>% llc hello.bc -o hello.s</tt></p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1530
Chris Lattner03793512004-06-02 20:37:02 +0000[diff] [blame]1531 <li><p>Assemble the native assembly language file into a program:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1532
Chris Lattner03793512004-06-02 20:37:02 +0000[diff] [blame]1533 <p><b>Solaris:</b><tt>% /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native</tt></p>
1534 <p><b>Others:</b><tt>% gcc hello.s -o hello.native</tt></p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1535
Chris Lattner03793512004-06-02 20:37:02 +0000[diff] [blame]1536 <li><p>Execute the native code program:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1537
Chris Lattner03793512004-06-02 20:37:02 +0000[diff] [blame]1538 <p><tt>% ./hello.native</tt></p></li>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1539
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1540</ol>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1541
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1542</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1543
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1544<!-- *********************************************************************** -->
1545<div class="doc_section">
1546 <a name="problems">Common Problems</a>
1547</div>
1548<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1549
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1550<div class="doc_text">
John Criswellc5eb4602003-07-03 16:01:38 +0000[diff] [blame]1551
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1552<p>If you are having problems building or using LLVM, or if you have any other
1553general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1554Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1555
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1556</div>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1557
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1558<!-- *********************************************************************** -->
1559<div class="doc_section">
1560 <a name="links">Links</a>
1561</div>
1562<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1563
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1564<div class="doc_text">
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1565
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1566<p>This document is just an <b>introduction</b> to how to use LLVM to do
1567some simple things... there are many more interesting and complicated things
1568that you can do that aren't documented here (but we'll gladly accept a patch
1569if you want to write something up!). For more information about LLVM, check
1570out:</p>
John Criswell72989a52003-06-12 19:34:44 +0000[diff] [blame]1571
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1572<ul>
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]1573 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1574 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1575 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1576 that Uses LLVM</a></li>
1577</ul>
1578
1579</div>
1580
1581<!-- *********************************************************************** -->
1582
1583<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +0000[diff] [blame]1584<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000[diff] [blame]1585 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
1586 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
1587 <a href="http://validator.w3.org/check/referer"><img
1588 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
1589
Misha Brukman74d4df82003-11-22 01:30:01 +0000[diff] [blame]1590 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +0000[diff] [blame]1591 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
Reid Spencerca058542006-03-14 05:39:39 +0000[diff] [blame]1592 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1593 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +0000[diff] [blame]1594</address>
Misha Brukman560e9892003-11-07 19:43:14 +0000[diff] [blame]1595</body>
Guochun Shib65a78e2002-07-17 23:05:56 +0000[diff] [blame]1596</html>