blob: 06a9a60f355b6f690cdce540defe791cdd88ef3e [file] [log] [blame]
Misha Brukman560e9892003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shib65a78e2002-07-17 23:05:56 +00003<html>
Misha Brukman560e9892003-11-07 19:43:14 +00004<head>
Reid Spencer38fcf302004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman560e9892003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +000010
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000011<h1>
Misha Brukman560e9892003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000013</h1>
John Criswell72989a52003-06-12 19:34:44 +000014
Misha Brukman560e9892003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +000019 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000023 </ol></li>
John Criswell3ef61af2003-06-30 21:59:07 +000024
Misha Brukman560e9892003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell71139f22003-07-08 20:35:59 +000026 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000032 <li><a href="#installcf">Install the GCC Front End</a></li>
33 <li><a href="#config">Local LLVM Configuration</a></li>
34 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
35 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
36 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
37 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000038 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +000039
Misha Brukman560e9892003-11-07 19:43:14 +000040 <li><a href="#layout">Program layout</a>
41 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
43 <li><a href="#include"><tt>llvm/include</tt></a></li>
44 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
45 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
46 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
47 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trick68aa18e42010-09-23 20:26:44 +000048 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
50 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000051 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +000052
Misha Brukman560e9892003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000054 <ol>
55 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000056 </ol>
Misha Brukman560e9892003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner020e1fc2004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +000065 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner020e1fc2004-05-23 21:07:27 +000066 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
67 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
68 </p>
69</div>
Misha Brukman560e9892003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000073<h2>
74 <a name="overview">Overview</a>
75</h2>
Misha Brukman560e9892003-11-07 19:43:14 +000076<!-- *********************************************************************** -->
77
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +000078<div>
Misha Brukman560e9892003-11-07 19:43:14 +000079
80<p>Welcome to LLVM! In order to get started, you first need to know some
81basic information.</p>
82
Andrew Trick68aa18e42010-09-23 20:26:44 +000083<p>First, LLVM comes in three pieces. The first piece is the LLVM
84suite. This contains all of the tools, libraries, and header files
Jim Grosbach65e24652012-01-25 22:00:23 +000085needed to use LLVM. It contains an assembler, disassembler, bitcode
86analyzer and bitcode optimizer. It also contains basic regression tests that
87can be used to test the LLVM tools and the GCC front end.</p>
Misha Brukman560e9892003-11-07 19:43:14 +000088
89<p>The second piece is the GCC front end. This component provides a version of
Gabor Greifa54634a2007-07-06 22:07:22 +000090GCC that compiles C and C++ code into LLVM bitcode. Currently, the GCC front
Chris Lattner40872ad2007-03-06 06:27:34 +000091end uses the GCC parser to convert code to LLVM. Once
Gabor Greifa54634a2007-07-06 22:07:22 +000092compiled into LLVM bitcode, a program can be manipulated with the LLVM tools
Misha Brukman560e9892003-11-07 19:43:14 +000093from the LLVM suite.</p>
94
John Criswell6ab273c2004-12-08 17:53:54 +000095<p>
Andrew Trick68aa18e42010-09-23 20:26:44 +000096There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell6ab273c2004-12-08 17:53:54 +000097with a testing harness that can be used to further test LLVM's functionality
98and performance.
99</p>
100
Misha Brukman560e9892003-11-07 19:43:14 +0000101</div>
102
103<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000104<h2>
105 <a name="quickstart">Getting Started Quickly (A Summary)</a>
106</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000107<!-- *********************************************************************** -->
108
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000109<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000110
111<p>Here's the short story for getting up and running quickly with LLVM:</p>
112
113<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000114 <li>Read the documentation.</li>
115 <li>Read the documentation.</li>
116 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000117 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000118 (see <a href="#installcf">Install the GCC Front End</a> for details):
Misha Brukman560e9892003-11-07 19:43:14 +0000119 <ol>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000120 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000121 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
122 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
123 <li>Note: If the binary extension is "<tt>.bz</tt>" use <tt>bunzip2</tt> instead of <tt>gunzip</tt>.</li>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000124 <li>Note: On Windows, use <a href="http://www.7-zip.org/">7-Zip</a> or a similar archiving tool.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000125 <li>Add <tt>llvm-gcc</tt>'s "<tt>bin</tt>" directory to your <tt>PATH</tt> environment variable.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000126 </ol></li>
127
Misha Brukman20b8a6562005-02-03 22:25:23 +0000128 <li>Get the LLVM Source Code
Misha Brukman560e9892003-11-07 19:43:14 +0000129 <ul>
John Criswell58594852007-06-29 19:12:31 +0000130 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman560e9892003-11-07 19:43:14 +0000131 <ol>
132 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell64f13ab2004-03-12 20:31:37 +0000133 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000134 </ol></li>
135
Misha Brukman560e9892003-11-07 19:43:14 +0000136 </ul></li>
137
Misha Brukman20b8a6562005-02-03 22:25:23 +0000138 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswelldfe6a862004-12-10 15:51:16 +0000139 <ul>
John Criswell58594852007-06-29 19:12:31 +0000140 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswelldfe6a862004-12-10 15:51:16 +0000141 <ol>
142 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
143 <li><tt>cd llvm/projects</tt>
144 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000145 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswelldfe6a862004-12-10 15:51:16 +0000146 </ol></li>
147
John Criswelldfe6a862004-12-10 15:51:16 +0000148 </ul></li>
149
150
Misha Brukman560e9892003-11-07 19:43:14 +0000151 <li>Configure the LLVM Build Environment
152 <ol>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000153 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
154 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
155 Some common options:
156
Misha Brukman560e9892003-11-07 19:43:14 +0000157 <ul>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000158 <li><tt>--prefix=<i>directory</i></tt>
159 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000160 want the LLVM tools and libraries to be installed (default
161 <tt>/usr/local</tt>).</p></li>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000162 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
163 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswellcfdeb5c2005-05-09 16:39:27 +0000164 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sands10961cd2009-04-18 12:40:19 +0000165 not specified, the PATH will be searched. This is only needed if you
Andrew Trick68aa18e42010-09-23 20:26:44 +0000166 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000167 <li><tt>--enable-spec2000=<i>directory</i></tt>
168 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
169 benchmarks should be available in
170 <tt><i>directory</i></tt>.</p></li>
171 </ul>
172 </ol></li>
173
174 <li>Build the LLVM Suite:
175 <ol>
Chris Lattnere0050f02004-07-18 22:32:22 +0000176 <li><tt>gmake -k |&amp; tee gnumake.out
177 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner13ce9182007-01-04 07:06:05 +0000178 <li>If you get an "internal compiler error (ICE)" or test failures, see
179 <a href="#brokengcc">below</a>.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000180 </ol>
181
182</ol>
183
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000184<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000185detailed information on configuring and compiling LLVM. See <a
186href="#environment">Setting Up Your Environment</a> for tips that simplify
187working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
188Layout</a> to learn about the layout of the source code tree.</p>
189
190</div>
191
192<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000193<h2>
194 <a name="requirements">Requirements</a>
195</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000196<!-- *********************************************************************** -->
197
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000198<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000199
200<p>Before you begin to use the LLVM system, review the requirements given below.
201This may save you some trouble by knowing ahead of time what hardware and
202software you will need.</p>
203
Misha Brukman560e9892003-11-07 19:43:14 +0000204<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000205<h3>
206 <a name="hardware">Hardware</a>
207</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000208
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000209<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000210
211<p>LLVM is known to work on the following platforms:</p>
212
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000213<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000214<tr>
215 <th>OS</th>
216 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000217 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000218</tr>
219<tr>
Chris Lattner6bad1372009-07-22 04:21:40 +0000220 <td>AuroraUX</td>
221 <td>x86<sup><a href="#pf_1">1</a></sup></td>
222 <td>GCC</td>
Chris Lattner3a56ae82009-07-21 22:47:03 +0000223</tr>
224<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000225 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000226 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000227 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000228</tr>
229<tr>
Edward O'Callaghanab8a04c2009-08-04 05:24:28 +0000230 <td>Linux</td>
231 <td>amd64</td>
232 <td>GCC</td>
233</tr>
234<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000235 <td>Solaris</td>
236 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000237 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000238</tr>
239<tr>
240 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000241 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000242 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000243</tr>
244<tr>
Bill Wendling5d32b702010-12-15 01:35:55 +0000245 <td>FreeBSD</td>
246 <td>amd64</td>
247 <td>GCC</td>
248</tr>
249<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000250 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000251 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000252 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000253</tr>
254<tr>
Scott Michel4799ea72008-03-18 23:13:26 +0000255 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000256 <td>x86</td>
257 <td>GCC</td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000258</tr>
259<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000260 <td>Cygwin/Win32</td>
Anton Korobeynikovd0a0bc32009-12-09 17:26:02 +0000261 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
262 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000263 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000264</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000265<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000266 <td>MinGW/Win32</td>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000267 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000268 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
269 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000270 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000271</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000272</table>
273
274<p>LLVM has partial support for the following platforms:</p>
275
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000276<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000277<tr>
278 <th>OS</th>
279 <th>Arch</th>
280 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000281</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000282<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000283 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000284 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruthd1eafe12011-11-16 19:52:13 +0000285 <td>Visual Studio 2008 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000286<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000287 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000288 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000289 <td>GCC</td>
290</tr>
291<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000292 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000293 <td>PowerPC</td>
294 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000295</tr>
John Criswell05990f32005-05-09 16:49:59 +0000296
297<tr>
298 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
299 <td>Alpha</td>
300 <td>GCC</td>
301</tr>
302<tr>
303 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
304 <td>Itanium (IA-64)</td>
305 <td>GCC</td>
306</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000307<tr>
308 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
309 <td>Itanium (IA-64)</td>
310 <td>HP aCC</td>
311</tr>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000312<tr>
313 <td>Windows x64</td>
314 <td>x86-64</td>
315 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
316</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000317</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000318
Misha Brukman77723092005-02-09 21:01:26 +0000319<p><b>Notes:</b></p>
320
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000321<div class="doc_notes">
322<ol>
323<li><a name="pf_1">Code generation supported for Pentium processors and
324up</a></li>
325<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
326<li><a name="pf_3">No native code generation</a></li>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000327<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000328<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattnerb7481cf2009-01-02 07:10:51 +0000329<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell05990f32005-05-09 16:49:59 +0000330<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000331<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
332 generated by LLVM properly.</a></li>
Chris Lattner26c74442008-11-09 17:19:14 +0000333<li><a name="pf_9">XCode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel4799ea72008-03-18 23:13:26 +0000334 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner26c74442008-11-09 17:19:14 +0000335 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
336 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel4799ea72008-03-18 23:13:26 +0000337 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000338<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
339 version of the perl package, and be sure it appears in your path
340 before any Windows-based versions such as Strawberry Perl and
341 ActivePerl, as these have Windows-specifics that will cause the
342 build to fail.</a></li>
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000343<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000344 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000345<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000346 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukman77723092005-02-09 21:01:26 +0000347</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000348</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000349
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000350<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 +0000351mode, depending on the system (it is so large because of all the debugging
352information and the fact that the libraries are statically linked into multiple
Chris Lattner0cb89772009-04-25 22:08:52 +0000353tools). If you do not need many of the tools and you are space-conscious, you
354can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
355requires considerably less space.</p>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000356
Misha Brukman560e9892003-11-07 19:43:14 +0000357<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
358guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greifa54634a2007-07-06 22:07:22 +0000359able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman560e9892003-11-07 19:43:14 +0000360generation should work as well, although the generated native code may not work
361on your platform.</p>
362
363<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 +0000364to work on another platform, you can download a copy of the source and <a
Duncan Sands551d3e62008-02-14 17:53:22 +0000365href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000366
367</div>
368
369<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000370<h3>
371 <a name="software">Software</a>
372</h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000373<div>
Reid Spencer38fcf302004-11-15 21:15:12 +0000374 <p>Compiling LLVM requires that you have several software packages
375 installed. The table below lists those required packages. The Package column
376 is the usual name for the software package that LLVM depends on. The Version
377 column provides "known to work" versions of the package. The Notes column
378 describes how LLVM uses the package and provides other details.</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000379 <table summary="Packages required to compile LLVM">
Reid Spencer38fcf302004-11-15 21:15:12 +0000380 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000381
Reid Spencer38fcf302004-11-15 21:15:12 +0000382 <tr>
383 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
384 <td>3.79, 3.79.1</td>
385 <td>Makefile/build processor</td>
386 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000387
Reid Spencer38fcf302004-11-15 21:15:12 +0000388 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000389 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000390 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000391 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000392 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000393
Reid Spencer38fcf302004-11-15 21:15:12 +0000394 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000395 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000396 <td>4.5</td>
397 <td>For building the CFE</td>
398 </tr>
399
400 <tr>
John Criswell58594852007-06-29 19:12:31 +0000401 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
402 <td>&ge;1.3</td>
403 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000404 </tr>
405
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +0000406 <!-- FIXME:
407 Do we support dg?
408 Are DejaGnu and expect obsolete?
409 Shall we mention Python? -->
410
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000411 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000412 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
413 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000414 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000415 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000416
Reid Spencer38fcf302004-11-15 21:15:12 +0000417 <tr>
418 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
419 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000420 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000421 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000422
Reid Spencer38fcf302004-11-15 21:15:12 +0000423 <tr>
424 <td><a href="http://expect.nist.gov/">expect</a></td>
425 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000426 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000427 </tr>
428
429 <tr>
430 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000431 <td>&ge;5.6.0</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000432 <td>Nightly tester, utilities</td>
433 </tr>
434
435 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000436 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
437 <td>1.4</td>
438 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000439 </tr>
440
441 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000442 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000443 <td>2.60</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000444 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
445 </tr>
446
447 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000448 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000449 <td>1.9.6</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000450 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
451 </tr>
452
453 <tr>
454 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000455 <td>1.5.22</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000456 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000457 </tr>
458
459 </table>
460
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000461 <p><b>Notes:</b></p>
462 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000463 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000464 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000465 need to build the other languages for LLVM's purposes.</a> See
466 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell58594852007-06-29 19:12:31 +0000467 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000468 latest LLVM sources. If you're working from a release distribution, you
John Criswell58594852007-06-29 19:12:31 +0000469 don't need Subversion.</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000470 <li><a name="sf3">Only needed if you want to run the automated test
471 suite in the <tt>llvm/test</tt> directory.</a></li>
472 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser4518c862010-05-19 07:00:17 +0000473 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
474 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer098fce42004-12-09 17:55:37 +0000475 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000476 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000477 </div>
478
Reid Spencer38fcf302004-11-15 21:15:12 +0000479 <p>Additionally, your compilation host is expected to have the usual
480 plethora of Unix utilities. Specifically:</p>
481 <ul>
482 <li><b>ar</b> - archive library builder</li>
483 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
484 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
485 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000486 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000487 <li><b>cp</b> - copy files</li>
488 <li><b>date</b> - print the current date/time </li>
489 <li><b>echo</b> - print to standard output</li>
490 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000491 <li><b>find</b> - find files/dirs in a file system</li>
492 <li><b>grep</b> - regular expression search utility</li>
493 <li><b>gzip*</b> - gzip command for distribution generation</li>
494 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
495 <li><b>install</b> - install directories/files </li>
496 <li><b>mkdir</b> - create a directory</li>
497 <li><b>mv</b> - move (rename) files</li>
498 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000499 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000500 <li><b>sed</b> - stream editor for transforming output</li>
501 <li><b>sh</b> - Bourne shell for make build scripts</li>
502 <li><b>tar</b> - tape archive for distribution generation</li>
503 <li><b>test</b> - test things in file system</li>
504 <li><b>unzip*</b> - unzip command for distribution checking</li>
505 <li><b>zip*</b> - zip command for distribution generation</li>
506 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000507</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000508
Chris Lattnere0050f02004-07-18 22:32:22 +0000509<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000510<h3>
Chris Lattner55514822007-06-19 05:52:36 +0000511 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000512</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000513
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000514<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000515
516<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
517bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenekaff36402011-10-31 21:23:15 +0000518to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
519Other versions of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000520here are known to not work. If you are using one of these versions, please try
521to upgrade your GCC to something more recent. If you run into a problem with a
522version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
523us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
524of GCC you are using.
525</p>
526
527<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
528problems in the STL that effectively prevent it from compiling LLVM.
529</p>
530
Chris Lattner419df4e2008-02-13 17:50:24 +0000531<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
532a bogus template error. This was fixed in later GCCs.</p>
John Criswellfd769452004-11-23 22:06:24 +0000533
Chris Lattnere0050f02004-07-18 22:32:22 +0000534<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
535href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
536the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000537
Chris Lattner58247622005-02-13 22:20:49 +0000538<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands551d3e62008-02-14 17:53:22 +0000539 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner58247622005-02-13 22:20:49 +0000540 to a newer version</a> if possible.</p>
541<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
542 possibly others) does not compile LLVM correctly (it appears that exception
543 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
544 to a newer version of GCC.</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000545<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000546 code generator, causing an infinite loop in the llvm-gcc build when built
547 with optimizations enabled (i.e. a release build).</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000548<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000549 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
550 correctly compiles LLVM at -O2. A work around is to build release LLVM
551 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000552<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner489ad332007-04-01 20:14:46 +0000553 miscompiles portions of LLVM</a>.</p>
Chris Lattner059a8df2007-11-01 04:20:16 +0000554<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
555 when building with optimizations enabled. It appears to work with
556 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
557 build.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000558<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
559 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000560<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
561 default with ENABLE_OPTIMIZED=1. To work around this, build with
562 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000563<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
564 compiling some files. At the time of this writing, GCC mainline (4.2)
565 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000566<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
567 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
568 code. LLVM will appear to mostly work but will be buggy, e.g. failing
569 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000570<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
571platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbar2a575452008-10-11 18:40:33 +0000572<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
573to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
574about symbols remaining in the table on destruction.</p>
Nuno Lopes94993852008-12-10 16:11:10 +0000575<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes65e877e2008-12-10 16:01:22 +0000576as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Anton Korobeynikovdad58712009-05-04 10:24:46 +0000577<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
578 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
579 with link errors when using this GCC version.</p>
Chris Lattnereba6c722009-09-10 16:25:02 +0000580<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewyckyd562ab12009-07-17 06:32:10 +0000581<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
582when optimizations are turned on. The symptom is an infinite loop in
Chris Lattnereba6c722009-09-10 16:25:02 +0000583FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewyckyabe8c132010-10-07 22:30:47 +0000584<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5851</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
586one symptom of the problem.
Reid Spencer6291ddc2006-11-04 00:33:42 +0000587<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
588long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
589defined in a discarded section. You can safely ignore these messages as they are
590erroneous and the linkage is correct. These messages disappear using ld
5912.17.</p>
Chris Lattner55514822007-06-19 05:52:36 +0000592
593<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
594href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
595causes huge link times (minutes instead of seconds) when building LLVM. We
596recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
597
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000598<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewycky2db07612009-02-25 06:29:47 +0000599<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
600which causes intermittent failures when building LLVM with position independent
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000601code. The symptom is an error about cyclic dependencies. We recommend
602upgrading to a newer version of Gold.</p>
Nick Lewycky2db07612009-02-25 06:29:47 +0000603
Misha Brukman560e9892003-11-07 19:43:14 +0000604</div>
605
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000606</div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000607
Misha Brukman560e9892003-11-07 19:43:14 +0000608<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000609<h2>
610 <a name="starting">Getting Started with LLVM</a>
611</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000612<!-- *********************************************************************** -->
613
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000614<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000615
616<p>The remainder of this guide is meant to get you up and running with
617LLVM and to give you some basic information about the LLVM environment.</p>
618
619<p>The later sections of this guide describe the <a
620href="#layout">general layout</a> of the the LLVM source tree, a <a
621href="#tutorial">simple example</a> using the LLVM tool chain, and <a
622href="#links">links</a> to find more information about LLVM or to get
623help via e-mail.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000624
Misha Brukman560e9892003-11-07 19:43:14 +0000625<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000626<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000627 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000628</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000629
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000630<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000631
632<p>Throughout this manual, the following names are used to denote paths
633specific to the local system and working environment. <i>These are not
634environment variables you need to set but just strings used in the rest
635of this document below</i>. In any of the examples below, simply replace
636each of these names with the appropriate pathname on your local system.
637All these paths are absolute:</p>
638
Misha Brukmand3de5c62004-01-20 00:20:17 +0000639<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000640 <dt>SRC_ROOT
641 <dd>
642 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000643 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000644
Misha Brukman560e9892003-11-07 19:43:14 +0000645 <dt>OBJ_ROOT
646 <dd>
647 This is the top level directory of the LLVM object tree (i.e. the
648 tree where object files and compiled programs will be placed. It
649 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000650 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000651
652 <dt>LLVMGCCDIR
653 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000654 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000655 <p>
656 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000657 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000658</dl>
659
660</div>
661
662<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000663<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000664 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000665</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000666
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000667<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000668
669<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000670In order to compile and use LLVM, you may need to set some environment
671variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000672
Misha Brukmand3de5c62004-01-20 00:20:17 +0000673<dl>
Gabor Greifa54634a2007-07-06 22:07:22 +0000674 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000675 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greifa54634a2007-07-06 22:07:22 +0000676 locations of your bitcode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000677 convenience since you can specify the paths using the -L options of the
Gabor Greifa54634a2007-07-06 22:07:22 +0000678 tools and the C/C++ front-end will automatically use the bitcode files
John Criswelle1a81202005-05-18 19:43:33 +0000679 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000680 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000681</dl>
682
683</div>
684
685<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000686<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000687 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000688</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000689
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000690<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000691
692<p>
693If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000694can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000695suite and the LLVM GCC front end compiled for your platform. There is an
696additional test suite that is optional. Each file is a TAR archive that is
697compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000698</p>
699
Misha Brukmand4528ea2005-02-02 18:01:57 +0000700<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000701<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000702 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukman21a63702008-12-11 18:23:24 +0000703 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000704
Misha Brukmand4528ea2005-02-02 18:01:57 +0000705 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000706 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000707
Misha Brukman4050d152008-12-29 19:38:58 +0000708 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
709 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukman21a63702008-12-11 18:23:24 +0000710 directory for build instructions.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000711
Misha Brukman4050d152008-12-29 19:38:58 +0000712 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
713 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000714
Misha Brukman560e9892003-11-07 19:43:14 +0000715</dl>
716
717</div>
718
719<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000720<h3>
John Criswell58594852007-06-29 19:12:31 +0000721 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000722</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000723
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000724<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000725
John Criswell58594852007-06-29 19:12:31 +0000726<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattner1c1595f2009-04-25 22:24:49 +0000727the entire source code. All you need to do is check it out from Subversion as
Misha Brukman560e9892003-11-07 19:43:14 +0000728follows:</p>
729
730<ul>
John Criswell58594852007-06-29 19:12:31 +0000731 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov4c04a93332007-06-29 20:56:49 +0000732 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
733 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell58594852007-06-29 19:12:31 +0000734 llvm</tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000735</ul>
736
John Criswell58594852007-06-29 19:12:31 +0000737
Misha Brukman560e9892003-11-07 19:43:14 +0000738<p>This will create an '<tt>llvm</tt>' directory in the current
739directory and fully populate it with the LLVM source code, Makefiles,
740test directories, and local copies of documentation files.</p>
741
Misha Brukmand3de5c62004-01-20 00:20:17 +0000742<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikoveaa836b2007-06-29 23:13:42 +0000743revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikov09ca62d2007-06-30 00:00:57 +0000744'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman52757bf2008-12-17 16:27:23 +0000745subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000746
John Criswell86a3a482003-12-18 16:43:17 +0000747<ul>
Bill Wendlingdb624242011-04-04 23:42:51 +0000748<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc4735872010-10-06 23:50:30 +0000749<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner3d7ec7b2010-10-06 05:36:01 +0000750<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattner9d3ba88b2009-10-23 06:20:06 +0000751<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000752<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman52757bf2008-12-17 16:27:23 +0000753<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattner610e89d2008-06-09 06:02:09 +0000754<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattner779593c2008-02-12 02:42:55 +0000755<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner586eb8e2007-09-28 22:50:54 +0000756<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000757<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000758<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000759<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000760<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000761<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000762<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000763<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000764<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000765<li>Release 1.2: <b>RELEASE_12</b></li>
766<li>Release 1.1: <b>RELEASE_11</b></li>
767<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000768</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000769
Reid Spencerdfcf7902004-12-08 16:51:31 +0000770<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell58594852007-06-29 19:12:31 +0000771you get it from the Subversion repository:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000772
773<div class="doc_code">
Reid Spencerdfcf7902004-12-08 16:51:31 +0000774<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000775% cd llvm/projects
Andrew Trick68aa18e42010-09-23 20:26:44 +0000776% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencerdfcf7902004-12-08 16:51:31 +0000777</pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000778</div>
779
Reid Spencerdfcf7902004-12-08 16:51:31 +0000780<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000781configured by the LLVM configure script as well as automatically updated when
John Criswell58594852007-06-29 19:12:31 +0000782you run <tt>svn update</tt>.</p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000783
Chris Lattner40872ad2007-03-06 06:27:34 +0000784<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands551d3e62008-02-14 17:53:22 +0000785and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner40872ad2007-03-06 06:27:34 +0000786instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000787
Misha Brukman560e9892003-11-07 19:43:14 +0000788</div>
789
790<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000791<h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000792 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000793</h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000794
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000795<div>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000796
797<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
798 sync automatically with each Subversion commit and contain all necessary
799 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
800 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000801 read-only GIT clone of LLVM via:</p>
802
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000803<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000804git clone http://llvm.org/git/llvm.git
805</pre>
806
807<p>If you want to check out clang too, run:</p>
808
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000809<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000810git clone http://llvm.org/git/llvm.git
811cd llvm/tools
812git clone http://llvm.org/git/clang.git
813</pre>
814
NAKAMURA Takumid92a5fe2011-08-12 07:48:01 +0000815<p>
816Since the upstream repository is in Subversion, you should use
817<tt>&quot;git pull --rebase&quot;</tt>
818instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
819history in your clone.
820To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
821on the master branch, run the following command:
822</p>
823
824<pre class="doc_code">
825git config branch.master.rebase true
826</pre>
827
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000828<h4>Sending patches with Git</h4>
829<div>
830<p>
831Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
832</p>
833
834<p>
835Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
836working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
837At first you may check sanity of whitespaces:
838</p>
839
840<pre class="doc_code">
841git diff --check master..mybranch
842</pre>
843
844<p>
845The easiest way to generate a patch is as below:
846</p>
847
848<pre class="doc_code">
849git diff master..mybranch &gt; /path/to/mybranch.diff
850</pre>
851
852<p>
853It is a little different from svn-generated diff. git-diff-generated diff has
854prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
855know it could be accepted with <tt>patch -p1 -N</tt>.
856</p>
857
858<p>
859But you may generate patchset with git-format-patch. It generates
860by-each-commit patchset. To generate patch files to attach to your article:
861</p>
862
863<pre class="doc_code">
864git format-patch --no-attach master..mybranch -o /path/to/your/patchset
865</pre>
866
867<p>
868If you would like to send patches directly, you may use git-send-email or
869git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
870</p>
871
872<pre class="doc_code">
873git format-patch --attach master..mybranch --stdout | git imap-send
874</pre>
875
876<p>
877Then, your .git/config should have [imap] sections.
878</p>
879
880<pre class="doc_code">
881[imap]
882 host = imaps://imap.gmail.com
883 user = <em>your.gmail.account</em>@gmail.com
884 pass = <em>himitsu!</em>
885 port = 993
886 sslverify = false
887; in English
888 folder = "[Gmail]/Drafts"
889; example for Japanese, "Modified UTF-7" encoded.
890 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumia61f0cc2011-11-06 06:51:58 +0000891; example for Traditional Chinese
892 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000893</pre>
894
895</div>
896
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000897<h4>For developers to work with git-svn</h4>
898<div>
899
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000900<p>To set up clone from which you can submit code using
901 <tt>git-svn</tt>, run:</p>
902
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000903<pre class="doc_code">
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000904git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000905cd llvm
906git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
907git config svn-remote.svn.fetch :refs/remotes/origin/master
908git svn rebase -l # -l avoids fetching ahead of the git mirror.
909
910# If you have clang too:
911cd tools
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000912git clone http://llvm.org/git/clang.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000913cd clang
914git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
915git config svn-remote.svn.fetch :refs/remotes/origin/master
916git svn rebase -l
917</pre>
918
919<p>To update this clone without generating git-svn tags that conflict
920with the upstream git repo, run:</p>
921
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000922<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000923git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
924git checkout master
925git svn rebase -l
926(cd tools/clang &&
927 git checkout master &&
928 git svn rebase -l)
929</pre>
930
931<p>This leaves your working directories on their master branches, so
932you'll need to <tt>checkout</tt> each working branch individually and
933<tt>rebase</tt> it on top of its parent branch. (Note: This script is
934intended for relative newbies to git. If you have more experience,
935you can likely improve on it.)</p>
936
937<p>The git-svn metadata can get out of sync after you mess around with
938branches and <code>dcommit</code>. When that happens, <code>git svn
939dcommit</code> stops working, complaining about files with uncommitted
940changes. The fix is to rebuild the metadata:</p>
941
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000942<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000943rm -rf .git/svn
944git svn rebase -l
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000945</pre>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000946
947</div>
948
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000949</div>
950
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000951<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000952<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000953 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000954</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000955
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000956<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000957
Jim Grosbach67584fe2009-12-17 17:18:11 +0000958<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
959GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trick68aa18e42010-09-23 20:26:44 +0000960It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach67584fe2009-12-17 17:18:11 +0000961you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattner24b71352007-02-14 07:33:00 +0000962main LLVM repository.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000963
Jim Grosbach67584fe2009-12-17 17:18:11 +0000964<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000965like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000966
967<ol>
968 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukman4050d152008-12-29 19:38:58 +0000969 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman560e9892003-11-07 19:43:14 +0000970 -</tt></li>
971</ol>
972
Jim Grosbach67584fe2009-12-17 17:18:11 +0000973<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
974<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
975Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
976to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
977<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
978
979<p>If you now want to build LLVM from source, when you configure LLVM, it will
980automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trick68aa18e42010-09-23 20:26:44 +0000981use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach67584fe2009-12-17 17:18:11 +0000982point after building the main LLVM repository: just reconfigure llvm and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000983test-suite will pick it up.
Chris Lattner24b71352007-02-14 07:33:00 +0000984</p>
985
Jim Grosbach67584fe2009-12-17 17:18:11 +0000986<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
987versions of the required w32api and mingw-runtime binaries. The last remaining step for
988Windows users is to simply uncompress the binary binutils package from
989<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
990front end installation steps are not quite the same as a typical manual MinGW installation,
991they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000992
Jim Grosbach67584fe2009-12-17 17:18:11 +0000993<p>To install binutils on Windows:</p>
994
995<ol>
996 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
997 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
998 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
999</ol>
1000
1001<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
1002example, the binary distribution may include an old version of a system header
1003file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
1004libraries not available on your system. In cases like these, you may want to try
1005<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
1006this is much easier now than it was in the past.</p>
1007
1008<p>We also do not currently support updating of the GCC front end by manually overlaying
1009newer versions of the w32api and mingw-runtime binary packages that may become available
1010from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
1011a self-contained convenience package that requires Windows users to simply download and
1012uncompress the GNU Binutils binary package from the MinGW project.</p>
1013
1014<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
1015binaries is not as easy as previously described, or you would like to suggest improvements,
1016please let us know how you would like to see things improved by dropping us a note on our
1017<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001018
1019</div>
1020
1021<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001022<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001023 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001024</h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001025
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001026<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001027
John Criswell58594852007-06-29 19:12:31 +00001028 <p>Once checked out from the Subversion repository, the LLVM suite source
1029 code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +00001030configured via the <tt>configure</tt> script. This script sets variables in the
1031various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
1032<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
1033the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001034
1035<p>The following environment variables are used by the <tt>configure</tt>
1036script to configure the build system:</p>
1037
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001038<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +00001039 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +00001040 <tr>
1041 <td>CC</td>
1042 <td>Tells <tt>configure</tt> which C compiler to use. By default,
1043 <tt>configure</tt> will look for the first GCC C compiler in
1044 <tt>PATH</tt>. Use this variable to override
1045 <tt>configure</tt>'s default behavior.</td>
1046 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +00001047 <tr>
1048 <td>CXX</td>
1049 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
1050 <tt>configure</tt> will look for the first GCC C++ compiler in
1051 <tt>PATH</tt>. Use this variable to override
1052 <tt>configure</tt>'s default behavior.</td>
1053 </tr>
1054</table>
1055
1056<p>The following options can be used to set or enable LLVM specific options:</p>
1057
Misha Brukmand3de5c62004-01-20 00:20:17 +00001058<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +00001059 <dt><i>--with-llvmgccdir</i></dt>
1060 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
1061 The value of this option should specify the full pathname of the C/C++ Front
1062 End to be used. If this option is not provided, the PATH will be searched for
1063 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
1064 be inferred from the path found. If the option is not given, and no llvm-gcc
1065 can be found in the path then a warning will be produced by
1066 <tt>configure</tt> indicating this situation. LLVM may still be built with
1067 the <tt>tools-only</tt> target but attempting to build the runtime libraries
1068 will fail as these libraries require llvm-gcc and llvm-g++. See
1069 <a href="#installcf">Install the GCC Front End</a> for details on installing
1070 the C/C++ Front End. See
Duncan Sands551d3e62008-02-14 17:53:22 +00001071 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencer6bfa7a42004-12-26 05:47:26 +00001072 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001073 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +00001074 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +00001075 found. Use this if you have multiple tcl installations on your machine and you
1076 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
1077 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +00001078 option, the LLVM configure script will search for the tcl 8.4 and 8.3
1079 releases.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001080 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001081 </dd>
1082 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +00001083 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001084 Enables optimized compilation (debugging symbols are removed
1085 and GCC optimization flags are enabled). Note that this is the default
1086 setting if you are using the LLVM distribution. The default behavior
1087 of an Subversion checkout is to use an unoptimized build (also known as a
1088 debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001089 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001090 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +00001091 <dt><i>--enable-debug-runtime</i></dt>
1092 <dd>
1093 Enables debug symbols in the runtime libraries. The default is to strip
1094 debug symbols from the runtime libraries.
1095 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001096 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +00001097 <dd>
John Criswell86a3a482003-12-18 16:43:17 +00001098 Compile the Just In Time (JIT) compiler functionality. This is not
1099 available
Misha Brukman560e9892003-11-07 19:43:14 +00001100 on all platforms. The default is dependent on platform, so it is best
1101 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001102 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001103 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +00001104 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1105 <dd>Controls which targets will be built and linked into llc. The default
1106 value for <tt>target_options</tt> is "all" which builds and links all
1107 available targets. The value "host-only" can be specified to build only a
1108 native compiler (no cross-compiler targets available). The "native" target is
1109 selected as the target of the build host. You can also specify a comma
1110 separated list of target names that you want available in llc. The target
Misha Brukman21a63702008-12-11 18:23:24 +00001111 names use all lower case. The current set of targets is: <br>
Reid Spencer1e195bd2005-04-22 17:58:03 +00001112 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001113 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001114 <dt><i>--enable-doxygen</i></dt>
1115 <dd>Look for the doxygen program and enable construction of doxygen based
1116 documentation from the source code. This is disabled by default because
1117 generating the documentation can take a long time and producess 100s of
1118 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +00001119 <dt><i>--with-udis86</i></dt>
1120 <dd>LLVM can use external disassembler library for various purposes (now it's
1121 used only for examining code produced by JIT). This option will enable usage
1122 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1123 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001124</dl>
1125
1126<p>To configure LLVM, follow these steps:</p>
1127
1128<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001129 <li><p>Change directory into the object root directory:</p>
John Criswellf531f312003-10-27 18:18:16 +00001130
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001131 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1132
1133 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1134 tree:</p>
1135
1136 <div class="doc_code">
1137 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1138 </div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001139</ol>
John Criswell72989a52003-06-12 19:34:44 +00001140
Misha Brukman560e9892003-11-07 19:43:14 +00001141</div>
John Criswell72989a52003-06-12 19:34:44 +00001142
Misha Brukman560e9892003-11-07 19:43:14 +00001143<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001144<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001145 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001146</h3>
John Criswell72989a52003-06-12 19:34:44 +00001147
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001148<div>
John Criswell71139f22003-07-08 20:35:59 +00001149
Misha Brukman560e9892003-11-07 19:43:14 +00001150<p>Once you have configured LLVM, you can build it. There are three types of
1151builds:</p>
John Criswell71139f22003-07-08 20:35:59 +00001152
Misha Brukmand3de5c62004-01-20 00:20:17 +00001153<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001154 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001155 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001156 These builds are the default when one is using an Subversion checkout and
1157 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1158 used during configuration). The build system will compile the tools and
1159 libraries with debugging information. To get a Debug Build using the
1160 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1161 to <tt>configure</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001162 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001163
1164 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001165 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001166 These builds are enabled with the <tt>--enable-optimized</tt> option to
1167 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1168 <tt>gmake</tt> command line. For these builds, the build system will
1169 compile the tools and libraries with GCC optimizations enabled and strip
1170 debugging information from the libraries and executables it generates.
Chris Lattner1c1595f2009-04-25 22:24:49 +00001171 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001172 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001173
1174 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001175 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001176 These builds are for use with profiling. They compile profiling
1177 information into the code for use with programs like <tt>gprof</tt>.
1178 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1179 on the <tt>gmake</tt> command line.
1180</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001181
Misha Brukman560e9892003-11-07 19:43:14 +00001182<p>Once you have LLVM configured, you can build it by entering the
1183<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001184
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001185<div class="doc_code"><pre>% gmake</pre></div>
John Criswell38cc2b52003-10-10 14:26:14 +00001186
Chris Lattnere0050f02004-07-18 22:32:22 +00001187<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +00001188are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +00001189
1190<p>
1191If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +00001192the parallel build options provided by GNU Make. For example, you could use the
1193command:</p>
John Criswell72989a52003-06-12 19:34:44 +00001194
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001195<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellc5eb4602003-07-03 16:01:38 +00001196
Misha Brukman560e9892003-11-07 19:43:14 +00001197<p>There are several special targets which are useful when working with the LLVM
1198source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001199
Misha Brukmand3de5c62004-01-20 00:20:17 +00001200<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001201 <dt><tt>gmake clean</tt>
1202 <dd>
1203 Removes all files generated by the build. This includes object files,
1204 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001205 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001206
Reid Spencerdfcf7902004-12-08 16:51:31 +00001207 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001208 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +00001209 Removes everything that <tt>gmake clean</tt> does, but also removes files
1210 generated by <tt>configure</tt>. It attempts to return the source tree to the
1211 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001212 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001213
Misha Brukman62a2c1f2004-08-23 20:25:33 +00001214 <dt><tt>gmake install</tt>
1215 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +00001216 Installs LLVM header files, libraries, tools, and documentation in a
1217 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +00001218 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1219 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001220 <br><br>
1221
Reid Spencerdfcf7902004-12-08 16:51:31 +00001222 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001223 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +00001224 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greifa54634a2007-07-06 22:07:22 +00001225 install bitcode libraries into the GCC front end's bitcode library
1226 directory. If you need to update your bitcode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +00001227 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001228 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001229</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001230
Reid Spencerdfcf7902004-12-08 16:51:31 +00001231<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1232details on these <tt>make</tt> targets and descriptions of other targets
1233available.</p>
1234
Misha Brukman560e9892003-11-07 19:43:14 +00001235<p>It is also possible to override default values from <tt>configure</tt> by
1236declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001237
Misha Brukmand3de5c62004-01-20 00:20:17 +00001238<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001239 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1240 <dd>
1241 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001242 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001243
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001244 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001245 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001246 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001247 <br><br>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001248
1249 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1250 <dd>
1251 Perform a Debug build.
1252 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001253
Misha Brukman560e9892003-11-07 19:43:14 +00001254 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1255 <dd>
1256 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001257 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001258
Misha Brukman560e9892003-11-07 19:43:14 +00001259 <dt><tt>gmake VERBOSE=1</tt>
1260 <dd>
1261 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001262 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001263
1264 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1265 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001266 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001267 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001268</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001269
Misha Brukman560e9892003-11-07 19:43:14 +00001270<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1271it and any subdirectories that it contains. Entering any directory inside the
1272LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1273that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001274
Misha Brukman560e9892003-11-07 19:43:14 +00001275</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001276
Misha Brukman560e9892003-11-07 19:43:14 +00001277<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001278<h3>
Reid Spencer734b74f2006-07-27 06:41:31 +00001279 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001280</h3>
Reid Spencerd966b242006-07-27 05:43:30 +00001281
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001282<div>
Jim Grosbach7da1b902009-04-17 17:25:16 +00001283 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1284 executables and libraries to be hosted on a platform different from the
1285 platform where they are build (a Canadian Cross build). To configure a
1286 cross-compile, supply the configure script with <tt>--build</tt> and
1287 <tt>--host</tt> options that are different. The values of these options must
1288 be legal target triples that your GCC compiler supports.</p>
1289
1290 <p>The result of such a build is executables that are not runnable on
1291 on the build host (--build option) but can be executed on the compile host
Reid Spencer734b74f2006-07-27 06:41:31 +00001292 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001293</div>
1294
1295<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001296<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001297 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001298</h3>
John Criswell38cc2b52003-10-10 14:26:14 +00001299
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001300<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001301
Misha Brukman560e9892003-11-07 19:43:14 +00001302<p>The LLVM build system is capable of sharing a single LLVM source tree among
1303several LLVM builds. Hence, it is possible to build LLVM for several different
1304platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001305
Misha Brukman560e9892003-11-07 19:43:14 +00001306<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001307
Misha Brukman560e9892003-11-07 19:43:14 +00001308<ul>
1309 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001310
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001311 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001312
Misha Brukman560e9892003-11-07 19:43:14 +00001313 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1314 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001315
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001316 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001317</ul>
John Criswell72989a52003-06-12 19:34:44 +00001318
Misha Brukman560e9892003-11-07 19:43:14 +00001319<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1320named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001321
Misha Brukmand3de5c62004-01-20 00:20:17 +00001322<dl>
Duncan Sands1567f0f2010-07-08 08:27:18 +00001323 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman560e9892003-11-07 19:43:14 +00001324 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001325 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001326 <dt>Tools
Duncan Sands1567f0f2010-07-08 08:27:18 +00001327 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001328 <dt>Libraries
Duncan Sands1567f0f2010-07-08 08:27:18 +00001329 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001330 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001331 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001332
Misha Brukman560e9892003-11-07 19:43:14 +00001333 <dt>Release Builds
1334 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001335 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001336 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001337 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001338 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001339 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001340 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001341 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001342
Misha Brukman560e9892003-11-07 19:43:14 +00001343 <dt>Profile Builds
1344 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001345 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001346 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001347 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001348 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001349 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001350 </dl>
1351</dl>
John Criswell72989a52003-06-12 19:34:44 +00001352
Misha Brukman560e9892003-11-07 19:43:14 +00001353</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001354
Chris Lattner998c0672004-03-25 20:38:40 +00001355<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001356<h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001357 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001358</h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001359
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001360<div>
Chris Lattner998c0672004-03-25 20:38:40 +00001361
1362<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001363If you're running on a Linux system that supports the "<a
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001364href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001365module, and you have root access on the system, you can set your system up to
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001366execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattner998c0672004-03-25 20:38:40 +00001367first command may not be required if you are already using the module):</p>
1368
Misha Brukman20b8a6562005-02-03 22:25:23 +00001369<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001370<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001371$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckyb8c923b2009-11-04 06:15:28 +00001372$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001373$ chmod u+x hello.bc (if needed)
1374$ ./hello.bc
Chris Lattner998c0672004-03-25 20:38:40 +00001375</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001376</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001377
1378<p>
Chris Lattnerb5c11742010-02-17 18:33:13 +00001379This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +00001380can also use this command instead of the 'echo' command above:
Chris Lattner998c0672004-03-25 20:38:40 +00001381</p>
1382
Chris Lattnerb5c11742010-02-17 18:33:13 +00001383<div class="doc_code">
1384<pre>
1385$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1386</pre>
1387</div>
1388
Chris Lattner998c0672004-03-25 20:38:40 +00001389</div>
1390
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001391</div>
1392
Misha Brukman560e9892003-11-07 19:43:14 +00001393<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001394<h2>
1395 <a name="layout">Program Layout</a>
1396</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001397<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001398
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001399<div>
John Criswell72989a52003-06-12 19:34:44 +00001400
Misha Brukman560e9892003-11-07 19:43:14 +00001401<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001402href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001403href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001404The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001405
Misha Brukman560e9892003-11-07 19:43:14 +00001406<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001407<h3>
1408 <a name="examples"><tt>llvm/examples</tt></a>
1409</h3>
1410
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001411<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001412 <p>This directory contains some simple examples of how to use the LLVM IR and
1413 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001414</div>
John Criswell72989a52003-06-12 19:34:44 +00001415
Misha Brukman560e9892003-11-07 19:43:14 +00001416<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001417<h3>
1418 <a name="include"><tt>llvm/include</tt></a>
1419</h3>
1420
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001421<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001422
1423<p>This directory contains public header files exported from the LLVM
1424library. The three main subdirectories of this directory are:</p>
1425
Reid Spencer075de232004-09-05 20:50:22 +00001426<dl>
1427 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1428 <dd>This directory contains all of the LLVM specific header files. This
1429 directory also has subdirectories for different portions of LLVM:
1430 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1431 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001432
Reid Spencer075de232004-09-05 20:50:22 +00001433 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1434 <dd>This directory contains generic support libraries that are provided with
1435 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1436 and a Command Line option processing library store their header files here.
1437 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001438
Reid Spencer075de232004-09-05 20:50:22 +00001439 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1440 <dd>This directory contains header files configured by the <tt>configure</tt>
1441 script. They wrap "standard" UNIX and C header files. Source code can
1442 include these header files which automatically take care of the conditional
1443 #includes that the <tt>configure</tt> script generates.</dd>
1444</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001445</div>
1446
1447<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001448<h3>
1449 <a name="lib"><tt>llvm/lib</tt></a>
1450</h3>
1451
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001452<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001453
1454<p>This directory contains most of the source files of the LLVM system. In LLVM,
1455almost all code exists in libraries, making it very easy to share code among the
1456different <a href="#tools">tools</a>.</p>
1457
Misha Brukmand3de5c62004-01-20 00:20:17 +00001458<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001459 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1460 <dd> This directory holds the core LLVM source files that implement core
1461 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001462
Reid Spencer075de232004-09-05 20:50:22 +00001463 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1464 <dd>This directory holds the source code for the LLVM assembly language parser
1465 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001466
Gabor Greifa54634a2007-07-06 22:07:22 +00001467 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1468 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001469
Reid Spencer075de232004-09-05 20:50:22 +00001470 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001471 different program analyses, such as Dominator Information, Call Graphs,
1472 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001473 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001474
Reid Spencer075de232004-09-05 20:50:22 +00001475 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1476 <dd> This directory contains the source code for the LLVM to LLVM program
1477 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1478 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1479 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001480
Reid Spencer075de232004-09-05 20:50:22 +00001481 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1482 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001483 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1484 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +00001485 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001486
Reid Spencer075de232004-09-05 20:50:22 +00001487 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1488 <dd> This directory contains the major parts of the code generator: Instruction
1489 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001490
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +00001491 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1492 <dd>(FIXME: T.B.D.)</dd>
1493
1494 <!--FIXME: obsoleted -->
Reid Spencer075de232004-09-05 20:50:22 +00001495 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1496 <dd> This directory contains the source level debugger library that makes
1497 it possible to instrument LLVM programs so that a debugger could identify
1498 source code locations at which the program is executing.</dd>
1499
1500 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001501 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer075de232004-09-05 20:50:22 +00001502 at runtime in both interpreted and JIT compiled fashions.</dd>
1503
1504 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar037fc932011-10-11 20:02:52 +00001505 <dd> This directory contains the source code that corresponds to the header
1506 files located in <tt>llvm/include/ADT/</tt>
1507 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001508</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001509
Misha Brukman560e9892003-11-07 19:43:14 +00001510</div>
John Criswell72989a52003-06-12 19:34:44 +00001511
Misha Brukman560e9892003-11-07 19:43:14 +00001512<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001513<h3>
1514 <a name="projects"><tt>llvm/projects</tt></a>
1515</h3>
1516
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001517<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001518 <p>This directory contains projects that are not strictly part of LLVM but are
1519 shipped with LLVM. This is also the directory where you should create your own
1520 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner7b7b6782008-08-11 06:13:31 +00001521 to set up your own project.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001522</div>
1523
1524<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001525<h3>
1526 <a name="runtime"><tt>llvm/runtime</tt></a>
1527</h3>
1528
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001529<div>
John Criswell72989a52003-06-12 19:34:44 +00001530
Gabor Greifa54634a2007-07-06 22:07:22 +00001531<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman560e9892003-11-07 19:43:14 +00001532used when linking programs with the GCC front end. Most of these libraries are
1533skeleton versions of real libraries; for example, libc is a stripped down
1534version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001535
Misha Brukman560e9892003-11-07 19:43:14 +00001536<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1537end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001538
Misha Brukman560e9892003-11-07 19:43:14 +00001539</div>
John Criswell72989a52003-06-12 19:34:44 +00001540
Misha Brukman560e9892003-11-07 19:43:14 +00001541<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001542<h3>
1543 <a name="test"><tt>llvm/test</tt></a>
1544</h3>
1545
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001546<div>
Reid Spencer075de232004-09-05 20:50:22 +00001547 <p>This directory contains feature and regression tests and other basic sanity
1548 checks on the LLVM infrastructure. These are intended to run quickly and cover
1549 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001550</div>
John Criswell72989a52003-06-12 19:34:44 +00001551
Misha Brukman560e9892003-11-07 19:43:14 +00001552<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001553<h3>
1554 <a name="test-suite"><tt>test-suite</tt></a>
1555</h3>
1556
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001557<div>
John Criswell58594852007-06-29 19:12:31 +00001558 <p>This is not a directory in the normal llvm module; it is a separate
1559 Subversion
1560 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1561 This
John Criswell6ab273c2004-12-08 17:53:54 +00001562 module contains a comprehensive correctness, performance, and benchmarking
1563 test
John Criswell58594852007-06-29 19:12:31 +00001564 suite for LLVM. It is a separate Subversion module because not every LLVM
1565 user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001566 interested in downloading or building such a comprehensive test suite. For
1567 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001568 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001569</div>
John Criswell72989a52003-06-12 19:34:44 +00001570
Reid Spencer075de232004-09-05 20:50:22 +00001571<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001572<h3>
1573 <a name="tools"><tt>llvm/tools</tt></a>
1574</h3>
1575
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001576<div>
John Criswell38cc2b52003-10-10 14:26:14 +00001577
Misha Brukman560e9892003-11-07 19:43:14 +00001578<p>The <b>tools</b> directory contains the executables built out of the
1579libraries above, which form the main part of the user interface. You can
Duncan Sands142b9ed2010-02-18 14:08:13 +00001580always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001581following is a brief introduction to the most important tools. More detailed
1582information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001583
Misha Brukmand3de5c62004-01-20 00:20:17 +00001584<dl>
John Criswell72989a52003-06-12 19:34:44 +00001585
Reid Spencer075de232004-09-05 20:50:22 +00001586 <dt><tt><b>bugpoint</b></tt></dt>
1587 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001588 optimization passes or code generation backends by narrowing down the
1589 given test case to the minimum number of passes and/or instructions that
1590 still cause a problem, whether it is a crash or miscompilation. See <a
1591 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001592 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001593
Reid Spencer075de232004-09-05 20:50:22 +00001594 <dt><tt><b>llvm-ar</b></tt></dt>
1595 <dd>The archiver produces an archive containing
Gabor Greifa54634a2007-07-06 22:07:22 +00001596 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001597 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001598
Reid Spencer075de232004-09-05 20:50:22 +00001599 <dt><tt><b>llvm-as</b></tt></dt>
1600 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001601 bitcode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001602
Reid Spencer075de232004-09-05 20:50:22 +00001603 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001604 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer075de232004-09-05 20:50:22 +00001605 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001606
Reid Spencer92815e52004-12-08 18:00:30 +00001607 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001608 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Eric Christophercafab2e2011-09-20 00:42:28 +00001609 It performs standard link time optimizations and allows optimization
1610 modules to be loaded and run so that language specific optimizations can
1611 be applied at link time.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +00001612
Reid Spencer075de232004-09-05 20:50:22 +00001613 <dt><tt><b>llvm-link</b></tt></dt>
1614 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1615 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001616
Reid Spencer075de232004-09-05 20:50:22 +00001617 <dt><tt><b>lli</b></tt></dt>
1618 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky97467822007-12-03 01:58:01 +00001619 can directly execute LLVM bitcode (although very slowly...). For architectures
1620 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1621 will function as a Just-In-Time compiler (if the functionality was compiled
1622 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001623
Reid Spencer075de232004-09-05 20:50:22 +00001624 <dt><tt><b>llc</b></tt></dt>
1625 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greifa54634a2007-07-06 22:07:22 +00001626 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001627 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001628
Reid Spencer788b0fd2004-12-22 06:29:07 +00001629 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001630 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1631 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001632 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencera7974cc2007-02-09 15:59:08 +00001633 usual machine code output. It works just like any other GCC compiler,
1634 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1635 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell58594852007-06-29 19:12:31 +00001636 separate Subversion module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001637
Reid Spencer075de232004-09-05 20:50:22 +00001638 <dt><tt><b>opt</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001639 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer80f843d2006-08-28 00:34:19 +00001640 transformations (which are specified on the command line), and then outputs
Duncan Sands142b9ed2010-02-18 14:08:13 +00001641 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukman21a63702008-12-11 18:23:24 +00001642 get a list of the program transformations available in LLVM.<br>
Reid Spencer80f843d2006-08-28 00:34:19 +00001643 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greifa54634a2007-07-06 22:07:22 +00001644 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer80f843d2006-08-28 00:34:19 +00001645 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001646</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001647</div>
John Criswell72989a52003-06-12 19:34:44 +00001648
Misha Brukman560e9892003-11-07 19:43:14 +00001649<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001650<h3>
1651 <a name="utils"><tt>llvm/utils</tt></a>
1652</h3>
1653
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001654<div>
John Criswell72989a52003-06-12 19:34:44 +00001655
Misha Brukman560e9892003-11-07 19:43:14 +00001656<p>This directory contains utilities for working with LLVM source code, and some
1657of the utilities are actually required as part of the build process because they
1658are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001659
Misha Brukmand3de5c62004-01-20 00:20:17 +00001660<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001661 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001662 that finds differences between code that LLC generates and code that LLI
1663 generates. This is a useful tool if you are debugging one of them,
1664 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001665 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001666
Misha Brukmand3de5c62004-01-20 00:20:17 +00001667 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001668 syntax-highlighting files which will work with Emacs and XEmacs editors,
1669 providing syntax highlighting support for LLVM assembly files and TableGen
1670 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001671 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001672
Misha Brukmand3de5c62004-01-20 00:20:17 +00001673 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001674 and outputs all non-generated source files, which is useful if one wishes
1675 to do a lot of development across directories and does not want to
1676 individually find each file. One way to use it is to run, for example:
1677 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001678 tree.<br><br>
1679
Reid Spencer075de232004-09-05 20:50:22 +00001680 <dt><tt><b>llvmgrep</b></tt></dt>
1681 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1682 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1683 line. This is a very efficient way of searching the source base for a
1684 particular regular expression.</dd>
1685
Misha Brukmand3de5c62004-01-20 00:20:17 +00001686 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001687 files in the current directory and then compiles and links the tool that
1688 is the first argument. For example, assuming you are in the directory
1689 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1690 simply running <tt>makellvm llc</tt> will make a build of the current
1691 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001692 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001693
Tanya Lattner3e852072007-05-22 06:12:51 +00001694 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukmand3de5c62004-01-20 00:20:17 +00001695 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman560e9892003-11-07 19:43:14 +00001696 cron script to generate nightly status reports of the functionality of
1697 tools, and the results can be seen by following the appropriate link on
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001698 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001699
Misha Brukmand3de5c62004-01-20 00:20:17 +00001700 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001701 the tool used to generate register descriptions, instruction set
1702 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001703 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001704
Misha Brukmand3de5c62004-01-20 00:20:17 +00001705 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001706 syntax-highlighting files which will work with the VIM editor, providing
1707 syntax highlighting support for LLVM assembly files and TableGen
1708 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001709 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001710
Misha Brukman560e9892003-11-07 19:43:14 +00001711</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001712
Misha Brukman560e9892003-11-07 19:43:14 +00001713</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001714
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001715</div>
1716
Misha Brukman560e9892003-11-07 19:43:14 +00001717<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001718<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001719 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001720</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001721<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001722
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001723<div>
Chris Lattner424d4dc2007-01-04 07:08:27 +00001724<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
Chris Lattner4c445302009-04-10 15:38:51 +00001725so we only include instructions for llvm-gcc4.
Chris Lattner5b560d92006-08-14 20:45:25 +00001726</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001727
1728<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1729from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
Gabor Greifa54634a2007-07-06 22:07:22 +00001730create bitcode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1731the '--emit-llvm' flag is needed to produce LLVM bitcode output. For <i>makefiles</i> and
1732<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bitcode
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001733output.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001734
1735<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001736<h3>
1737 <a name="tutorial4">Example with llvm-gcc4</a>
1738</h3>
Chris Lattner5b560d92006-08-14 20:45:25 +00001739
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001740<div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001741
1742<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001743 <li><p>First, create a simple C file, name it 'hello.c':</p>
1744
1745<div class="doc_code">
1746<pre>
1747#include &lt;stdio.h&gt;
1748
1749int main() {
1750 printf("hello world\n");
1751 return 0;
1752}
1753</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001754
1755 <li><p>Next, compile the C file into a native executable:</p>
1756
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001757 <div class="doc_code"><pre>% llvm-gcc hello.c -o hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001758
1759 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1760 -c arguments work as usual (producing a native .s or .o file,
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001761 respectively).</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001762
Gabor Greifa54634a2007-07-06 22:07:22 +00001763 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001764
1765 <div class="doc_code">
1766 <pre>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001767
1768 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1769 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1770 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Gabor Greifa54634a2007-07-06 22:07:22 +00001771 the bitcode file.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001772
1773 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1774 </p></li>
1775
1776 <li><p>Run the program in both forms. To run the program, use:</p>
1777
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001778 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001779
1780 <p>and</p>
1781
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001782 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001783
1784 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001785 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001786
1787 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1788 code:</p>
1789
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001790<div class="doc_code">
1791<pre>llvm-dis &lt; hello.bc | less</pre>
1792</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001793
1794 <li><p>Compile the program to native assembly using the LLC code
1795 generator:</p>
1796
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001797 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001798
1799 <li><p>Assemble the native assembly language file into a program:</p>
1800
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001801<div class="doc_code">
1802<pre>
1803<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1804
1805<b>Others:</b> % gcc hello.s -o hello.native
1806</pre>
1807</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001808
1809 <li><p>Execute the native code program:</p>
1810
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001811 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001812
1813 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1814 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001815 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001816
1817</ol>
1818
1819</div>
1820
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001821</div>
John Criswell72989a52003-06-12 19:34:44 +00001822
Misha Brukman560e9892003-11-07 19:43:14 +00001823<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001824<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001825 <a name="problems">Common Problems</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001826</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001827<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001828
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001829<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001830
Misha Brukman560e9892003-11-07 19:43:14 +00001831<p>If you are having problems building or using LLVM, or if you have any other
1832general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1833Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001834
Misha Brukman560e9892003-11-07 19:43:14 +00001835</div>
John Criswell72989a52003-06-12 19:34:44 +00001836
Misha Brukman560e9892003-11-07 19:43:14 +00001837<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001838<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001839 <a name="links">Links</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001840</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001841<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001842
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001843<div>
John Criswell72989a52003-06-12 19:34:44 +00001844
Bill Wendlingcb13d702008-07-22 01:10:25 +00001845<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman560e9892003-11-07 19:43:14 +00001846some simple things... there are many more interesting and complicated things
1847that you can do that aren't documented here (but we'll gladly accept a patch
1848if you want to write something up!). For more information about LLVM, check
1849out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001850
Misha Brukman560e9892003-11-07 19:43:14 +00001851<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001852 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1853 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1854 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001855 that Uses LLVM</a></li>
1856</ul>
1857
1858</div>
1859
1860<!-- *********************************************************************** -->
1861
1862<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001863<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001864 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001865 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001866 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +00001867 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001868
Misha Brukman74d4df82003-11-22 01:30:01 +00001869 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001870 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001871 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001872 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001873</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001874</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001875</html>