blob: d78344ad0fa3c0f987525ace4791024e42b6f4f0 [file] [log] [blame]
Misha Brukman00c73d22003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shif4688a82002-07-17 23:05:56 +00003<html>
Misha Brukman00c73d22003-11-07 19:43:14 +00004<head>
Reid Spencer748d82e2004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman00c73d22003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell85ed3612003-06-12 19:34:44 +000010
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000011<h1>
Misha Brukman00c73d22003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000013</h1>
John Criswell85ed3612003-06-12 19:34:44 +000014
Misha Brukman00c73d22003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattner96768ea2003-02-14 04:22:13 +000019 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000023 </ol></li>
John Criswell7a73b802003-06-30 21:59:07 +000024
Misha Brukman00c73d22003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell0b459202003-07-08 20:35:59 +000026 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner269f80c2007-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 Brukman00c73d22003-11-07 19:43:14 +000038 </ol></li>
John Criswell0b459202003-07-08 20:35:59 +000039
Misha Brukman00c73d22003-11-07 19:43:14 +000040 <li><a href="#layout">Program layout</a>
41 <ol>
Chris Lattner269f80c2007-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 Trickbcf01162010-09-23 20:26:44 +000048 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner269f80c2007-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 Brukman00c73d22003-11-07 19:43:14 +000051 </ol></li>
John Criswell0f6d7c02003-10-27 18:18:16 +000052
Misha Brukman00c73d22003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner9abd8af2006-09-07 04:19:09 +000054 <ol>
55 <li><a href="#tutorial4">Example with llvm-gcc4</a></li>
Chris Lattner9abd8af2006-09-07 04:19:09 +000056 </ol>
Misha Brukman00c73d22003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner7911ce22004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
NAKAMURA Takumib9a33632011-04-09 02:13:37 +000065 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner7911ce22004-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 Brukman00c73d22003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000073<h2>
74 <a name="overview">Overview</a>
75</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +000076<!-- *********************************************************************** -->
77
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +000078<div>
Misha Brukman00c73d22003-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 Trickbcf01162010-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
85needed to use the low level virtual machine. It contains an
86assembler, disassembler, bitcode analyzer and bitcode optimizer. It
87also contains basic regression tests that can be used to test the LLVM
88tools and the GCC front end.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000089
90<p>The second piece is the GCC front end. This component provides a version of
Gabor Greif04367bf2007-07-06 22:07:22 +000091GCC that compiles C and C++ code into LLVM bitcode. Currently, the GCC front
Chris Lattner82ad9f12007-03-06 06:27:34 +000092end uses the GCC parser to convert code to LLVM. Once
Gabor Greif04367bf2007-07-06 22:07:22 +000093compiled into LLVM bitcode, a program can be manipulated with the LLVM tools
Misha Brukman00c73d22003-11-07 19:43:14 +000094from the LLVM suite.</p>
95
John Criswell3d8ba512004-12-08 17:53:54 +000096<p>
Andrew Trickbcf01162010-09-23 20:26:44 +000097There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell3d8ba512004-12-08 17:53:54 +000098with a testing harness that can be used to further test LLVM's functionality
99and performance.
100</p>
101
Misha Brukman00c73d22003-11-07 19:43:14 +0000102</div>
103
104<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000105<h2>
106 <a name="quickstart">Getting Started Quickly (A Summary)</a>
107</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000108<!-- *********************************************************************** -->
109
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000110<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000111
112<p>Here's the short story for getting up and running quickly with LLVM:</p>
113
114<ol>
Reid Spencer9f547912004-11-08 00:29:22 +0000115 <li>Read the documentation.</li>
116 <li>Read the documentation.</li>
117 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000118 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000119 (see <a href="#installcf">Install the GCC Front End</a> for details):
Misha Brukman00c73d22003-11-07 19:43:14 +0000120 <ol>
Reid Spencerd4694f92004-12-22 06:29:07 +0000121 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000122 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
123 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
124 <li>Note: If the binary extension is "<tt>.bz</tt>" use <tt>bunzip2</tt> instead of <tt>gunzip</tt>.</li>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000125 <li>Note: On Windows, use <a href="http://www.7-zip.org/">7-Zip</a> or a similar archiving tool.</li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000126 <li>Add <tt>llvm-gcc</tt>'s "<tt>bin</tt>" directory to your <tt>PATH</tt> environment variable.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000127 </ol></li>
128
Misha Brukman9106eca2005-02-03 22:25:23 +0000129 <li>Get the LLVM Source Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000130 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000131 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman00c73d22003-11-07 19:43:14 +0000132 <ol>
133 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell364cec42004-03-12 20:31:37 +0000134 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000135 </ol></li>
136
Misha Brukman00c73d22003-11-07 19:43:14 +0000137 </ul></li>
138
Misha Brukman9106eca2005-02-03 22:25:23 +0000139 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswell9e2485c2004-12-10 15:51:16 +0000140 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000141 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswell9e2485c2004-12-10 15:51:16 +0000142 <ol>
143 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
144 <li><tt>cd llvm/projects</tt>
145 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000146 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswell9e2485c2004-12-10 15:51:16 +0000147 </ol></li>
148
John Criswell9e2485c2004-12-10 15:51:16 +0000149 </ul></li>
150
151
Misha Brukman00c73d22003-11-07 19:43:14 +0000152 <li>Configure the LLVM Build Environment
153 <ol>
Misha Brukman9106eca2005-02-03 22:25:23 +0000154 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
155 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
156 Some common options:
157
Misha Brukman00c73d22003-11-07 19:43:14 +0000158 <ul>
Reid Spencerd4694f92004-12-22 06:29:07 +0000159 <li><tt>--prefix=<i>directory</i></tt>
160 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000161 want the LLVM tools and libraries to be installed (default
162 <tt>/usr/local</tt>).</p></li>
Reid Spencerfef93b72004-12-26 05:47:26 +0000163 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
164 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswell838bce52005-05-09 16:39:27 +0000165 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sandsdc223762009-04-18 12:40:19 +0000166 not specified, the PATH will be searched. This is only needed if you
Andrew Trickbcf01162010-09-23 20:26:44 +0000167 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000168 <li><tt>--enable-spec2000=<i>directory</i></tt>
169 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
170 benchmarks should be available in
171 <tt><i>directory</i></tt>.</p></li>
172 </ul>
173 </ol></li>
174
175 <li>Build the LLVM Suite:
176 <ol>
Chris Lattner95e92582004-07-18 22:32:22 +0000177 <li><tt>gmake -k |&amp; tee gnumake.out
178 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000179 <li>If you get an "internal compiler error (ICE)" or test failures, see
180 <a href="#brokengcc">below</a>.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000181 </ol>
182
183</ol>
184
Chris Lattnerfcd37252004-06-21 22:52:48 +0000185<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000186detailed information on configuring and compiling LLVM. See <a
187href="#environment">Setting Up Your Environment</a> for tips that simplify
188working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
189Layout</a> to learn about the layout of the source code tree.</p>
190
191</div>
192
193<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000194<h2>
195 <a name="requirements">Requirements</a>
196</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000197<!-- *********************************************************************** -->
198
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000199<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000200
201<p>Before you begin to use the LLVM system, review the requirements given below.
202This may save you some trouble by knowing ahead of time what hardware and
203software you will need.</p>
204
Misha Brukman00c73d22003-11-07 19:43:14 +0000205<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000206<h3>
207 <a name="hardware">Hardware</a>
208</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000209
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000210<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000211
212<p>LLVM is known to work on the following platforms:</p>
213
Chris Lattner9abd8af2006-09-07 04:19:09 +0000214<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000215<tr>
216 <th>OS</th>
217 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000218 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000219</tr>
220<tr>
Chris Lattnerd8afc462009-07-22 04:21:40 +0000221 <td>AuroraUX</td>
222 <td>x86<sup><a href="#pf_1">1</a></sup></td>
223 <td>GCC</td>
Chris Lattner3e7b5ca2009-07-21 22:47:03 +0000224</tr>
225<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000226 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000227 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000228 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000229</tr>
230<tr>
Edward O'Callaghan37442b72009-08-04 05:24:28 +0000231 <td>Linux</td>
232 <td>amd64</td>
233 <td>GCC</td>
234</tr>
235<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000236 <td>Solaris</td>
237 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000238 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000239</tr>
240<tr>
241 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000242 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000243 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000244</tr>
245<tr>
Bill Wendlingf7226992010-12-15 01:35:55 +0000246 <td>FreeBSD</td>
247 <td>amd64</td>
248 <td>GCC</td>
249</tr>
250<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000251 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000252 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000253 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000254</tr>
255<tr>
Scott Michel050bc812008-03-18 23:13:26 +0000256 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000257 <td>x86</td>
258 <td>GCC</td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000259</tr>
260<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000261 <td>Cygwin/Win32</td>
Anton Korobeynikov16f16922009-12-09 17:26:02 +0000262 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
263 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000264 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman69def742004-11-19 21:53:22 +0000265</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000266<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000267 <td>MinGW/Win32</td>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000268 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000269 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
270 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000271 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000272</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000273</table>
274
275<p>LLVM has partial support for the following platforms:</p>
276
Chris Lattner9abd8af2006-09-07 04:19:09 +0000277<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000278<tr>
279 <th>OS</th>
280 <th>Arch</th>
281 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000282</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000283<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000284 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000285 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruth2929de42011-11-16 19:52:13 +0000286 <td>Visual Studio 2008 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000287<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000288 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000289 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000290 <td>GCC</td>
291</tr>
292<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000293 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000294 <td>PowerPC</td>
295 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000296</tr>
John Criswell75162552005-05-09 16:49:59 +0000297
298<tr>
299 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
300 <td>Alpha</td>
301 <td>GCC</td>
302</tr>
303<tr>
304 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
305 <td>Itanium (IA-64)</td>
306 <td>GCC</td>
307</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000308<tr>
309 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
310 <td>Itanium (IA-64)</td>
311 <td>HP aCC</td>
312</tr>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000313<tr>
314 <td>Windows x64</td>
315 <td>x86-64</td>
316 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
317</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000318</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000319
Misha Brukmana892ead2005-02-09 21:01:26 +0000320<p><b>Notes:</b></p>
321
Misha Brukman6d8e1532005-02-09 22:38:47 +0000322<div class="doc_notes">
323<ol>
324<li><a name="pf_1">Code generation supported for Pentium processors and
325up</a></li>
326<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
327<li><a name="pf_3">No native code generation</a></li>
Nick Lewycky28ea4f62008-12-08 00:45:02 +0000328<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000329<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner01bb8b02009-01-02 07:10:51 +0000330<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell75162552005-05-09 16:49:59 +0000331<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000332<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
333 generated by LLVM properly.</a></li>
Chris Lattner22b91d72008-11-09 17:19:14 +0000334<li><a name="pf_9">XCode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel050bc812008-03-18 23:13:26 +0000335 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner22b91d72008-11-09 17:19:14 +0000336 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
337 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel050bc812008-03-18 23:13:26 +0000338 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000339<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
340 version of the perl package, and be sure it appears in your path
341 before any Windows-based versions such as Strawberry Perl and
342 ActivePerl, as these have Windows-specifics that will cause the
343 build to fail.</a></li>
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000344<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000345 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000346<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000347 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000348</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000349</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000350
Misha Brukman69def742004-11-19 21:53:22 +0000351<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswell8bfe6a72005-05-18 19:43:33 +0000352mode, depending on the system (it is so large because of all the debugging
353information and the fact that the libraries are statically linked into multiple
Chris Lattner06942902009-04-25 22:08:52 +0000354tools). If you do not need many of the tools and you are space-conscious, you
355can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
356requires considerably less space.</p>
Misha Brukman69def742004-11-19 21:53:22 +0000357
Misha Brukman00c73d22003-11-07 19:43:14 +0000358<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
359guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greif04367bf2007-07-06 22:07:22 +0000360able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000361generation should work as well, although the generated native code may not work
362on your platform.</p>
363
364<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman22e9e332004-08-09 19:57:01 +0000365to work on another platform, you can download a copy of the source and <a
Duncan Sands8655b152008-02-14 17:53:22 +0000366href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000367
368</div>
369
370<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000371<h3>
372 <a name="software">Software</a>
373</h3>
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000374<div>
Reid Spencer748d82e2004-11-15 21:15:12 +0000375 <p>Compiling LLVM requires that you have several software packages
376 installed. The table below lists those required packages. The Package column
377 is the usual name for the software package that LLVM depends on. The Version
378 column provides "known to work" versions of the package. The Notes column
379 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000380 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000381 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000382
Reid Spencer748d82e2004-11-15 21:15:12 +0000383 <tr>
384 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
385 <td>3.79, 3.79.1</td>
386 <td>Makefile/build processor</td>
387 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000388
Reid Spencer748d82e2004-11-15 21:15:12 +0000389 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000390 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000391 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000392 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000393 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000394
Reid Spencer748d82e2004-11-15 21:15:12 +0000395 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000396 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattner2286cab2005-09-06 04:07:15 +0000397 <td>4.5</td>
398 <td>For building the CFE</td>
399 </tr>
400
401 <tr>
John Criswell9c29bfb2007-06-29 19:12:31 +0000402 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
403 <td>&ge;1.3</td>
404 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000405 </tr>
406
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +0000407 <!-- FIXME:
408 Do we support dg?
409 Are DejaGnu and expect obsolete?
410 Shall we mention Python? -->
411
Misha Brukman6d8e1532005-02-09 22:38:47 +0000412 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000413 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
414 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000415 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000416 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000417
Reid Spencer748d82e2004-11-15 21:15:12 +0000418 <tr>
419 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
420 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000421 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000422 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000423
Reid Spencer748d82e2004-11-15 21:15:12 +0000424 <tr>
425 <td><a href="http://expect.nist.gov/">expect</a></td>
426 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000427 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000428 </tr>
429
430 <tr>
431 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000432 <td>&ge;5.6.0</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000433 <td>Nightly tester, utilities</td>
434 </tr>
435
436 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000437 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
438 <td>1.4</td>
439 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000440 </tr>
441
442 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000443 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000444 <td>2.60</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000445 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
446 </tr>
447
448 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000449 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000450 <td>1.9.6</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000451 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
452 </tr>
453
454 <tr>
455 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000456 <td>1.5.22</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000457 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000458 </tr>
459
460 </table>
461
Misha Brukman6d8e1532005-02-09 22:38:47 +0000462 <p><b>Notes:</b></p>
463 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000464 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000465 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000466 need to build the other languages for LLVM's purposes.</a> See
467 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell9c29bfb2007-06-29 19:12:31 +0000468 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman6d8e1532005-02-09 22:38:47 +0000469 latest LLVM sources. If you're working from a release distribution, you
John Criswell9c29bfb2007-06-29 19:12:31 +0000470 don't need Subversion.</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000471 <li><a name="sf3">Only needed if you want to run the automated test
472 suite in the <tt>llvm/test</tt> directory.</a></li>
473 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser0560ce42010-05-19 07:00:17 +0000474 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
475 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer200d93b2004-12-09 17:55:37 +0000476 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000477 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000478 </div>
479
Reid Spencer748d82e2004-11-15 21:15:12 +0000480 <p>Additionally, your compilation host is expected to have the usual
481 plethora of Unix utilities. Specifically:</p>
482 <ul>
483 <li><b>ar</b> - archive library builder</li>
484 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
485 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
486 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000487 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000488 <li><b>cp</b> - copy files</li>
489 <li><b>date</b> - print the current date/time </li>
490 <li><b>echo</b> - print to standard output</li>
491 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000492 <li><b>find</b> - find files/dirs in a file system</li>
493 <li><b>grep</b> - regular expression search utility</li>
494 <li><b>gzip*</b> - gzip command for distribution generation</li>
495 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
496 <li><b>install</b> - install directories/files </li>
497 <li><b>mkdir</b> - create a directory</li>
498 <li><b>mv</b> - move (rename) files</li>
499 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000500 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000501 <li><b>sed</b> - stream editor for transforming output</li>
502 <li><b>sh</b> - Bourne shell for make build scripts</li>
503 <li><b>tar</b> - tape archive for distribution generation</li>
504 <li><b>test</b> - test things in file system</li>
505 <li><b>unzip*</b> - unzip command for distribution checking</li>
506 <li><b>zip*</b> - zip command for distribution generation</li>
507 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000508</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000509
Chris Lattner95e92582004-07-18 22:32:22 +0000510<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000511<h3>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000512 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000513</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000514
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000515<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000516
517<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
518bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenek0ba11792011-10-31 21:23:15 +0000519to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
520Other versions of GCC will probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000521here are known to not work. If you are using one of these versions, please try
522to upgrade your GCC to something more recent. If you run into a problem with a
523version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
524us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
525of GCC you are using.
526</p>
527
528<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
529problems in the STL that effectively prevent it from compiling LLVM.
530</p>
531
Chris Lattner82f0a092008-02-13 17:50:24 +0000532<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
533a bogus template error. This was fixed in later GCCs.</p>
John Criswell294ba022004-11-23 22:06:24 +0000534
Chris Lattner95e92582004-07-18 22:32:22 +0000535<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
536href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
537the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000538
Chris Lattner8e64f152005-02-13 22:20:49 +0000539<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands8655b152008-02-14 17:53:22 +0000540 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner8e64f152005-02-13 22:20:49 +0000541 to a newer version</a> if possible.</p>
542<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
543 possibly others) does not compile LLVM correctly (it appears that exception
544 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
545 to a newer version of GCC.</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000546<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000547 code generator, causing an infinite loop in the llvm-gcc build when built
548 with optimizations enabled (i.e. a release build).</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000549<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000550 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
551 correctly compiles LLVM at -O2. A work around is to build release LLVM
552 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000553<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner77c2af62007-04-01 20:14:46 +0000554 miscompiles portions of LLVM</a>.</p>
Chris Lattner269f80c2007-11-01 04:20:16 +0000555<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
556 when building with optimizations enabled. It appears to work with
557 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
558 build.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000559<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
560 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000561<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
562 default with ENABLE_OPTIMIZED=1. To work around this, build with
563 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000564<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
565 compiling some files. At the time of this writing, GCC mainline (4.2)
566 did not share the problem.</p>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000567<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
568 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
569 code. LLVM will appear to mostly work but will be buggy, e.g. failing
570 portions of its testsuite.</p>
Reid Spencer72f92f02007-04-11 21:28:31 +0000571<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
572platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbarb7dfaf92008-10-11 18:40:33 +0000573<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
574to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
575about symbols remaining in the table on destruction.</p>
Nuno Lopesf82242d2008-12-10 16:11:10 +0000576<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes58dc0b52008-12-10 16:01:22 +0000577as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Mike Stumpfe095f32009-05-04 18:40:41 +0000578<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
579 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
580 with link errors when using this GCC version.</p>
Chris Lattner478e71d2009-09-10 16:25:02 +0000581<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewycky3bf2d032009-07-17 06:32:10 +0000582<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
583when optimizations are turned on. The symptom is an infinite loop in
Chris Lattner478e71d2009-09-10 16:25:02 +0000584FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewycky256f9602010-10-07 22:30:47 +0000585<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5861</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
587one symptom of the problem.
Reid Spencer7a119082006-11-04 00:33:42 +0000588<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
589long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
590defined in a discarded section. You can safely ignore these messages as they are
591erroneous and the linkage is correct. These messages disappear using ld
5922.17.</p>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000593
594<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
595href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
596causes huge link times (minutes instead of seconds) when building LLVM. We
597recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
598
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000599<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000600<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
601which causes intermittent failures when building LLVM with position independent
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000602code. The symptom is an error about cyclic dependencies. We recommend
603upgrading to a newer version of Gold.</p>
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000604
Misha Brukman00c73d22003-11-07 19:43:14 +0000605</div>
606
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000607</div>
Chris Lattner95e92582004-07-18 22:32:22 +0000608
Misha Brukman00c73d22003-11-07 19:43:14 +0000609<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000610<h2>
611 <a name="starting">Getting Started with LLVM</a>
612</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000613<!-- *********************************************************************** -->
614
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000615<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000616
617<p>The remainder of this guide is meant to get you up and running with
618LLVM and to give you some basic information about the LLVM environment.</p>
619
620<p>The later sections of this guide describe the <a
621href="#layout">general layout</a> of the the LLVM source tree, a <a
622href="#tutorial">simple example</a> using the LLVM tool chain, and <a
623href="#links">links</a> to find more information about LLVM or to get
624help via e-mail.</p>
Chris Lattner95e92582004-07-18 22:32:22 +0000625
Misha Brukman00c73d22003-11-07 19:43:14 +0000626<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000627<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000628 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000629</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000630
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000631<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000632
633<p>Throughout this manual, the following names are used to denote paths
634specific to the local system and working environment. <i>These are not
635environment variables you need to set but just strings used in the rest
636of this document below</i>. In any of the examples below, simply replace
637each of these names with the appropriate pathname on your local system.
638All these paths are absolute:</p>
639
Misha Brukman54111c42004-01-20 00:20:17 +0000640<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000641 <dt>SRC_ROOT
642 <dd>
643 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000644 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000645
Misha Brukman00c73d22003-11-07 19:43:14 +0000646 <dt>OBJ_ROOT
647 <dd>
648 This is the top level directory of the LLVM object tree (i.e. the
649 tree where object files and compiled programs will be placed. It
650 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000651 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000652
653 <dt>LLVMGCCDIR
654 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000655 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000656 <p>
657 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000658 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +0000659</dl>
660
661</div>
662
663<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000664<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000665 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000666</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000667
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000668<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000669
670<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000671In order to compile and use LLVM, you may need to set some environment
672variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000673
Misha Brukman54111c42004-01-20 00:20:17 +0000674<dl>
Gabor Greif04367bf2007-07-06 22:07:22 +0000675 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000676 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greif04367bf2007-07-06 22:07:22 +0000677 locations of your bitcode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000678 convenience since you can specify the paths using the -L options of the
Gabor Greif04367bf2007-07-06 22:07:22 +0000679 tools and the C/C++ front-end will automatically use the bitcode files
John Criswell8bfe6a72005-05-18 19:43:33 +0000680 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000681 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000682</dl>
683
684</div>
685
686<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000687<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000688 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000689</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000690
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000691<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000692
693<p>
694If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000695can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000696suite and the LLVM GCC front end compiled for your platform. There is an
697additional test suite that is optional. Each file is a TAR archive that is
698compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000699</p>
700
Misha Brukman3ce11032005-02-02 18:01:57 +0000701<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000702<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000703 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000704 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000705
Misha Brukman3ce11032005-02-02 18:01:57 +0000706 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000707 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000708
Misha Brukmanccd02952008-12-29 19:38:58 +0000709 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
710 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000711 directory for build instructions.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000712
Misha Brukmanccd02952008-12-29 19:38:58 +0000713 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
714 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000715
Misha Brukman00c73d22003-11-07 19:43:14 +0000716</dl>
717
718</div>
719
720<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000721<h3>
John Criswell9c29bfb2007-06-29 19:12:31 +0000722 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000723</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000724
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000725<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000726
John Criswell9c29bfb2007-06-29 19:12:31 +0000727<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000728the entire source code. All you need to do is check it out from Subversion as
Misha Brukman00c73d22003-11-07 19:43:14 +0000729follows:</p>
730
731<ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000732 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov98044e42007-06-29 20:56:49 +0000733 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
734 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell9c29bfb2007-06-29 19:12:31 +0000735 llvm</tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000736</ul>
737
John Criswell9c29bfb2007-06-29 19:12:31 +0000738
Misha Brukman00c73d22003-11-07 19:43:14 +0000739<p>This will create an '<tt>llvm</tt>' directory in the current
740directory and fully populate it with the LLVM source code, Makefiles,
741test directories, and local copies of documentation files.</p>
742
Misha Brukman54111c42004-01-20 00:20:17 +0000743<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikovd933fa92007-06-29 23:13:42 +0000744revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikovd724dc82007-06-30 00:00:57 +0000745'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman9474d012008-12-17 16:27:23 +0000746subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000747
John Criswelld000e1d2003-12-18 16:43:17 +0000748<ul>
Bill Wendlingc3b94fb2011-04-04 23:42:51 +0000749<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc44c2452010-10-06 23:50:30 +0000750<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner994526c2010-10-06 05:36:01 +0000751<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattnerf08803b2009-10-23 06:20:06 +0000752<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000753<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman9474d012008-12-17 16:27:23 +0000754<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattnerb37ef512008-06-09 06:02:09 +0000755<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattnerdd50f0f2008-02-12 02:42:55 +0000756<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner76385652007-09-28 22:50:54 +0000757<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattner1dcadec2007-05-22 06:06:22 +0000758<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner134693a2006-11-20 06:07:10 +0000759<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000760<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattner993b9802006-04-20 04:35:34 +0000761<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000762<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000763<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000764<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000765<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000766<li>Release 1.2: <b>RELEASE_12</b></li>
767<li>Release 1.1: <b>RELEASE_11</b></li>
768<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000769</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000770
Reid Spencer66db92e2004-12-08 16:51:31 +0000771<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell9c29bfb2007-06-29 19:12:31 +0000772you get it from the Subversion repository:</p>
Bill Wendling77f74692007-07-16 08:44:39 +0000773
774<div class="doc_code">
Reid Spencer66db92e2004-12-08 16:51:31 +0000775<pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000776% cd llvm/projects
Andrew Trickbcf01162010-09-23 20:26:44 +0000777% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencer66db92e2004-12-08 16:51:31 +0000778</pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000779</div>
780
Reid Spencer66db92e2004-12-08 16:51:31 +0000781<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000782configured by the LLVM configure script as well as automatically updated when
John Criswell9c29bfb2007-06-29 19:12:31 +0000783you run <tt>svn update</tt>.</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000784
Chris Lattner82ad9f12007-03-06 06:27:34 +0000785<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands8655b152008-02-14 17:53:22 +0000786and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner82ad9f12007-03-06 06:27:34 +0000787instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000788
Misha Brukman00c73d22003-11-07 19:43:14 +0000789</div>
790
791<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000792<h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000793 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000794</h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000795
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000796<div>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000797
798<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
799 sync automatically with each Subversion commit and contain all necessary
800 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
801 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000802 read-only GIT clone of LLVM via:</p>
803
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000804<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000805git clone http://llvm.org/git/llvm.git
806</pre>
807
808<p>If you want to check out clang too, run:</p>
809
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000810<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000811git clone http://llvm.org/git/llvm.git
812cd llvm/tools
813git clone http://llvm.org/git/clang.git
814</pre>
815
NAKAMURA Takumi7a362f42011-08-12 07:48:01 +0000816<p>
817Since the upstream repository is in Subversion, you should use
818<tt>&quot;git pull --rebase&quot;</tt>
819instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
820history in your clone.
821To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
822on the master branch, run the following command:
823</p>
824
825<pre class="doc_code">
826git config branch.master.rebase true
827</pre>
828
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000829<h4>Sending patches with Git</h4>
830<div>
831<p>
832Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
833</p>
834
835<p>
836Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
837working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
838At first you may check sanity of whitespaces:
839</p>
840
841<pre class="doc_code">
842git diff --check master..mybranch
843</pre>
844
845<p>
846The easiest way to generate a patch is as below:
847</p>
848
849<pre class="doc_code">
850git diff master..mybranch &gt; /path/to/mybranch.diff
851</pre>
852
853<p>
854It is a little different from svn-generated diff. git-diff-generated diff has
855prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
856know it could be accepted with <tt>patch -p1 -N</tt>.
857</p>
858
859<p>
860But you may generate patchset with git-format-patch. It generates
861by-each-commit patchset. To generate patch files to attach to your article:
862</p>
863
864<pre class="doc_code">
865git format-patch --no-attach master..mybranch -o /path/to/your/patchset
866</pre>
867
868<p>
869If you would like to send patches directly, you may use git-send-email or
870git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
871</p>
872
873<pre class="doc_code">
874git format-patch --attach master..mybranch --stdout | git imap-send
875</pre>
876
877<p>
878Then, your .git/config should have [imap] sections.
879</p>
880
881<pre class="doc_code">
882[imap]
883 host = imaps://imap.gmail.com
884 user = <em>your.gmail.account</em>@gmail.com
885 pass = <em>himitsu!</em>
886 port = 993
887 sslverify = false
888; in English
889 folder = "[Gmail]/Drafts"
890; example for Japanese, "Modified UTF-7" encoded.
891 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumi0dd4f102011-11-06 06:51:58 +0000892; example for Traditional Chinese
893 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000894</pre>
895
896</div>
897
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000898<h4>For developers to work with git-svn</h4>
899<div>
900
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000901<p>To set up clone from which you can submit code using
902 <tt>git-svn</tt>, run:</p>
903
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000904<pre class="doc_code">
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000905git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000906cd llvm
907git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
908git config svn-remote.svn.fetch :refs/remotes/origin/master
909git svn rebase -l # -l avoids fetching ahead of the git mirror.
910
911# If you have clang too:
912cd tools
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000913git clone http://llvm.org/git/clang.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000914cd clang
915git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
916git config svn-remote.svn.fetch :refs/remotes/origin/master
917git svn rebase -l
918</pre>
919
920<p>To update this clone without generating git-svn tags that conflict
921with the upstream git repo, run:</p>
922
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000923<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000924git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
925git checkout master
926git svn rebase -l
927(cd tools/clang &&
928 git checkout master &&
929 git svn rebase -l)
930</pre>
931
932<p>This leaves your working directories on their master branches, so
933you'll need to <tt>checkout</tt> each working branch individually and
934<tt>rebase</tt> it on top of its parent branch. (Note: This script is
935intended for relative newbies to git. If you have more experience,
936you can likely improve on it.)</p>
937
938<p>The git-svn metadata can get out of sync after you mess around with
939branches and <code>dcommit</code>. When that happens, <code>git svn
940dcommit</code> stops working, complaining about files with uncommitted
941changes. The fix is to rebuild the metadata:</p>
942
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000943<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000944rm -rf .git/svn
945git svn rebase -l
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000946</pre>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000947
948</div>
949
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000950</div>
951
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000952<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000953<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000954 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000955</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000956
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000957<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000958
Jim Grosbach18df1d42009-12-17 17:18:11 +0000959<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
960GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trickbcf01162010-09-23 20:26:44 +0000961It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach18df1d42009-12-17 17:18:11 +0000962you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000963main LLVM repository.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000964
Jim Grosbach18df1d42009-12-17 17:18:11 +0000965<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000966like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000967
968<ol>
969 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukmanccd02952008-12-29 19:38:58 +0000970 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman00c73d22003-11-07 19:43:14 +0000971 -</tt></li>
972</ol>
973
Jim Grosbach18df1d42009-12-17 17:18:11 +0000974<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
975<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
976Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
977to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
978<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
979
980<p>If you now want to build LLVM from source, when you configure LLVM, it will
981automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trickbcf01162010-09-23 20:26:44 +0000982use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach18df1d42009-12-17 17:18:11 +0000983point after building the main LLVM repository: just reconfigure llvm and
Andrew Trickbcf01162010-09-23 20:26:44 +0000984test-suite will pick it up.
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000985</p>
986
Jim Grosbach18df1d42009-12-17 17:18:11 +0000987<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
988versions of the required w32api and mingw-runtime binaries. The last remaining step for
989Windows users is to simply uncompress the binary binutils package from
990<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
991front end installation steps are not quite the same as a typical manual MinGW installation,
992they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000993
Jim Grosbach18df1d42009-12-17 17:18:11 +0000994<p>To install binutils on Windows:</p>
995
996<ol>
997 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
998 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
999 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
1000</ol>
1001
1002<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
1003example, the binary distribution may include an old version of a system header
1004file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
1005libraries not available on your system. In cases like these, you may want to try
1006<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
1007this is much easier now than it was in the past.</p>
1008
1009<p>We also do not currently support updating of the GCC front end by manually overlaying
1010newer versions of the w32api and mingw-runtime binary packages that may become available
1011from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
1012a self-contained convenience package that requires Windows users to simply download and
1013uncompress the GNU Binutils binary package from the MinGW project.</p>
1014
1015<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
1016binaries is not as easy as previously described, or you would like to suggest improvements,
1017please let us know how you would like to see things improved by dropping us a note on our
1018<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001019
1020</div>
1021
1022<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001023<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001024 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001025</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001026
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001027<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001028
John Criswell9c29bfb2007-06-29 19:12:31 +00001029 <p>Once checked out from the Subversion repository, the LLVM suite source
1030 code must be
Reid Spencer66db92e2004-12-08 16:51:31 +00001031configured via the <tt>configure</tt> script. This script sets variables in the
1032various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
1033<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
1034the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001035
1036<p>The following environment variables are used by the <tt>configure</tt>
1037script to configure the build system:</p>
1038
Chris Lattner9abd8af2006-09-07 04:19:09 +00001039<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +00001040 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001041 <tr>
1042 <td>CC</td>
1043 <td>Tells <tt>configure</tt> which C compiler to use. By default,
1044 <tt>configure</tt> will look for the first GCC C compiler in
1045 <tt>PATH</tt>. Use this variable to override
1046 <tt>configure</tt>'s default behavior.</td>
1047 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001048 <tr>
1049 <td>CXX</td>
1050 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
1051 <tt>configure</tt> will look for the first GCC C++ compiler in
1052 <tt>PATH</tt>. Use this variable to override
1053 <tt>configure</tt>'s default behavior.</td>
1054 </tr>
1055</table>
1056
1057<p>The following options can be used to set or enable LLVM specific options:</p>
1058
Misha Brukman54111c42004-01-20 00:20:17 +00001059<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +00001060 <dt><i>--with-llvmgccdir</i></dt>
1061 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
1062 The value of this option should specify the full pathname of the C/C++ Front
1063 End to be used. If this option is not provided, the PATH will be searched for
1064 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
1065 be inferred from the path found. If the option is not given, and no llvm-gcc
1066 can be found in the path then a warning will be produced by
1067 <tt>configure</tt> indicating this situation. LLVM may still be built with
1068 the <tt>tools-only</tt> target but attempting to build the runtime libraries
1069 will fail as these libraries require llvm-gcc and llvm-g++. See
1070 <a href="#installcf">Install the GCC Front End</a> for details on installing
1071 the C/C++ Front End. See
Duncan Sands8655b152008-02-14 17:53:22 +00001072 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencerfef93b72004-12-26 05:47:26 +00001073 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001074 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +00001075 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +00001076 found. Use this if you have multiple tcl installations on your machine and you
1077 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
1078 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +00001079 option, the LLVM configure script will search for the tcl 8.4 and 8.3
1080 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001081 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001082 </dd>
1083 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001084 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001085 Enables optimized compilation (debugging symbols are removed
1086 and GCC optimization flags are enabled). Note that this is the default
1087 setting if you are using the LLVM distribution. The default behavior
1088 of an Subversion checkout is to use an unoptimized build (also known as a
1089 debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +00001090 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001091 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +00001092 <dt><i>--enable-debug-runtime</i></dt>
1093 <dd>
1094 Enables debug symbols in the runtime libraries. The default is to strip
1095 debug symbols from the runtime libraries.
1096 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001097 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001098 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +00001099 Compile the Just In Time (JIT) compiler functionality. This is not
1100 available
Misha Brukman00c73d22003-11-07 19:43:14 +00001101 on all platforms. The default is dependent on platform, so it is best
1102 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001103 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001104 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +00001105 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1106 <dd>Controls which targets will be built and linked into llc. The default
1107 value for <tt>target_options</tt> is "all" which builds and links all
1108 available targets. The value "host-only" can be specified to build only a
1109 native compiler (no cross-compiler targets available). The "native" target is
1110 selected as the target of the build host. You can also specify a comma
1111 separated list of target names that you want available in llc. The target
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001112 names use all lower case. The current set of targets is: <br>
Reid Spencer2dedcf52005-04-22 17:58:03 +00001113 <tt>alpha, ia64, powerpc, skeleton, sparc, x86</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001114 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001115 <dt><i>--enable-doxygen</i></dt>
1116 <dd>Look for the doxygen program and enable construction of doxygen based
1117 documentation from the source code. This is disabled by default because
1118 generating the documentation can take a long time and producess 100s of
1119 megabytes of output.</dd>
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +00001120 <dt><i>--with-udis86</i></dt>
1121 <dd>LLVM can use external disassembler library for various purposes (now it's
1122 used only for examining code produced by JIT). This option will enable usage
1123 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1124 bits) disassembler library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001125</dl>
1126
1127<p>To configure LLVM, follow these steps:</p>
1128
1129<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001130 <li><p>Change directory into the object root directory:</p>
John Criswell0f6d7c02003-10-27 18:18:16 +00001131
Bill Wendling77f74692007-07-16 08:44:39 +00001132 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1133
1134 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1135 tree:</p>
1136
1137 <div class="doc_code">
1138 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1139 </div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001140</ol>
John Criswell85ed3612003-06-12 19:34:44 +00001141
Misha Brukman00c73d22003-11-07 19:43:14 +00001142</div>
John Criswell85ed3612003-06-12 19:34:44 +00001143
Misha Brukman00c73d22003-11-07 19:43:14 +00001144<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001145<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001146 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001147</h3>
John Criswell85ed3612003-06-12 19:34:44 +00001148
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001149<div>
John Criswell0b459202003-07-08 20:35:59 +00001150
Misha Brukman00c73d22003-11-07 19:43:14 +00001151<p>Once you have configured LLVM, you can build it. There are three types of
1152builds:</p>
John Criswell0b459202003-07-08 20:35:59 +00001153
Misha Brukman54111c42004-01-20 00:20:17 +00001154<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001155 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +00001156 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001157 These builds are the default when one is using an Subversion checkout and
1158 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1159 used during configuration). The build system will compile the tools and
1160 libraries with debugging information. To get a Debug Build using the
1161 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1162 to <tt>configure</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001163 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001164
1165 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +00001166 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001167 These builds are enabled with the <tt>--enable-optimized</tt> option to
1168 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1169 <tt>gmake</tt> command line. For these builds, the build system will
1170 compile the tools and libraries with GCC optimizations enabled and strip
1171 debugging information from the libraries and executables it generates.
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001172 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001173 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001174
1175 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +00001176 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001177 These builds are for use with profiling. They compile profiling
1178 information into the code for use with programs like <tt>gprof</tt>.
1179 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1180 on the <tt>gmake</tt> command line.
1181</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001182
Misha Brukman00c73d22003-11-07 19:43:14 +00001183<p>Once you have LLVM configured, you can build it by entering the
1184<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001185
Bill Wendling77f74692007-07-16 08:44:39 +00001186<div class="doc_code"><pre>% gmake</pre></div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001187
Chris Lattner95e92582004-07-18 22:32:22 +00001188<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +00001189are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +00001190
1191<p>
1192If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +00001193the parallel build options provided by GNU Make. For example, you could use the
1194command:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001195
Bill Wendling77f74692007-07-16 08:44:39 +00001196<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellce760f62003-07-03 16:01:38 +00001197
Misha Brukman00c73d22003-11-07 19:43:14 +00001198<p>There are several special targets which are useful when working with the LLVM
1199source code:</p>
John Criswellce760f62003-07-03 16:01:38 +00001200
Misha Brukman54111c42004-01-20 00:20:17 +00001201<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001202 <dt><tt>gmake clean</tt>
1203 <dd>
1204 Removes all files generated by the build. This includes object files,
1205 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001206 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001207
Reid Spencer66db92e2004-12-08 16:51:31 +00001208 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001209 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +00001210 Removes everything that <tt>gmake clean</tt> does, but also removes files
1211 generated by <tt>configure</tt>. It attempts to return the source tree to the
1212 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001213 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001214
Misha Brukmane51c3562004-08-23 20:25:33 +00001215 <dt><tt>gmake install</tt>
1216 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +00001217 Installs LLVM header files, libraries, tools, and documentation in a
1218 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +00001219 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1220 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001221 <br><br>
1222
Reid Spencer66db92e2004-12-08 16:51:31 +00001223 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001224 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +00001225 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greif04367bf2007-07-06 22:07:22 +00001226 install bitcode libraries into the GCC front end's bitcode library
1227 directory. If you need to update your bitcode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +00001228 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001229 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001230</dl>
John Criswellce760f62003-07-03 16:01:38 +00001231
Reid Spencer66db92e2004-12-08 16:51:31 +00001232<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1233details on these <tt>make</tt> targets and descriptions of other targets
1234available.</p>
1235
Misha Brukman00c73d22003-11-07 19:43:14 +00001236<p>It is also possible to override default values from <tt>configure</tt> by
1237declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +00001238
Misha Brukman54111c42004-01-20 00:20:17 +00001239<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001240 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1241 <dd>
1242 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001243 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001244
Reid Spencer004ba032006-04-09 23:45:38 +00001245 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +00001246 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +00001247 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001248 <br><br>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001249
1250 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1251 <dd>
1252 Perform a Debug build.
1253 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +00001254
Misha Brukman00c73d22003-11-07 19:43:14 +00001255 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1256 <dd>
1257 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001258 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001259
Misha Brukman00c73d22003-11-07 19:43:14 +00001260 <dt><tt>gmake VERBOSE=1</tt>
1261 <dd>
1262 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001263 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001264
1265 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1266 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +00001267 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001268 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001269</dl>
John Criswellce760f62003-07-03 16:01:38 +00001270
Misha Brukman00c73d22003-11-07 19:43:14 +00001271<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1272it and any subdirectories that it contains. Entering any directory inside the
1273LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1274that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +00001275
Misha Brukman00c73d22003-11-07 19:43:14 +00001276</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001277
Misha Brukman00c73d22003-11-07 19:43:14 +00001278<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001279<h3>
Reid Spencerd30a9712006-07-27 06:41:31 +00001280 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001281</h3>
Reid Spencer17850ef2006-07-27 05:43:30 +00001282
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001283<div>
Jim Grosbach5bea8222009-04-17 17:25:16 +00001284 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1285 executables and libraries to be hosted on a platform different from the
1286 platform where they are build (a Canadian Cross build). To configure a
1287 cross-compile, supply the configure script with <tt>--build</tt> and
1288 <tt>--host</tt> options that are different. The values of these options must
1289 be legal target triples that your GCC compiler supports.</p>
1290
1291 <p>The result of such a build is executables that are not runnable on
1292 on the build host (--build option) but can be executed on the compile host
Reid Spencerd30a9712006-07-27 06:41:31 +00001293 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001294</div>
1295
1296<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001297<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001298 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001299</h3>
John Criswell20d2d3e2003-10-10 14:26:14 +00001300
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001301<div>
John Criswellce760f62003-07-03 16:01:38 +00001302
Misha Brukman00c73d22003-11-07 19:43:14 +00001303<p>The LLVM build system is capable of sharing a single LLVM source tree among
1304several LLVM builds. Hence, it is possible to build LLVM for several different
1305platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001306
Misha Brukman00c73d22003-11-07 19:43:14 +00001307<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001308
Misha Brukman00c73d22003-11-07 19:43:14 +00001309<ul>
1310 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001311
Bill Wendling77f74692007-07-16 08:44:39 +00001312 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellce760f62003-07-03 16:01:38 +00001313
Misha Brukman00c73d22003-11-07 19:43:14 +00001314 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1315 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001316
Bill Wendling77f74692007-07-16 08:44:39 +00001317 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001318</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001319
Misha Brukman00c73d22003-11-07 19:43:14 +00001320<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1321named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001322
Misha Brukman54111c42004-01-20 00:20:17 +00001323<dl>
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001324 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman00c73d22003-11-07 19:43:14 +00001325 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001326 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001327 <dt>Tools
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001328 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001329 <dt>Libraries
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001330 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001331 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001332 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001333
Misha Brukman00c73d22003-11-07 19:43:14 +00001334 <dt>Release Builds
1335 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001336 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001337 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001338 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001339 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001340 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001341 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001342 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001343
Misha Brukman00c73d22003-11-07 19:43:14 +00001344 <dt>Profile Builds
1345 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001346 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001347 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001348 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001349 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001350 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001351 </dl>
1352</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001353
Misha Brukman00c73d22003-11-07 19:43:14 +00001354</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001355
Chris Lattnera553f622004-03-25 20:38:40 +00001356<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001357<h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001358 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001359</h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001360
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001361<div>
Chris Lattnera553f622004-03-25 20:38:40 +00001362
1363<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001364If you're running on a Linux system that supports the "<a
Bill Wendling22e37c32007-07-16 08:46:40 +00001365href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001366module, and you have root access on the system, you can set your system up to
Bill Wendling22e37c32007-07-16 08:46:40 +00001367execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattnera553f622004-03-25 20:38:40 +00001368first command may not be required if you are already using the module):</p>
1369
Misha Brukman9106eca2005-02-03 22:25:23 +00001370<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001371<pre>
Bill Wendling77f74692007-07-16 08:44:39 +00001372$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckye6b5a522009-11-04 06:15:28 +00001373$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendling77f74692007-07-16 08:44:39 +00001374$ chmod u+x hello.bc (if needed)
1375$ ./hello.bc
Chris Lattnera553f622004-03-25 20:38:40 +00001376</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001377</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001378
1379<p>
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001380This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +00001381can also use this command instead of the 'echo' command above:
Chris Lattnera553f622004-03-25 20:38:40 +00001382</p>
1383
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001384<div class="doc_code">
1385<pre>
1386$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1387</pre>
1388</div>
1389
Chris Lattnera553f622004-03-25 20:38:40 +00001390</div>
1391
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001392</div>
1393
Misha Brukman00c73d22003-11-07 19:43:14 +00001394<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001395<h2>
1396 <a name="layout">Program Layout</a>
1397</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001398<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001399
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001400<div>
John Criswell85ed3612003-06-12 19:34:44 +00001401
Misha Brukman00c73d22003-11-07 19:43:14 +00001402<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001403href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001404href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001405The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001406
Misha Brukman00c73d22003-11-07 19:43:14 +00001407<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001408<h3>
1409 <a name="examples"><tt>llvm/examples</tt></a>
1410</h3>
1411
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001412<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001413 <p>This directory contains some simple examples of how to use the LLVM IR and
1414 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001415</div>
John Criswell85ed3612003-06-12 19:34:44 +00001416
Misha Brukman00c73d22003-11-07 19:43:14 +00001417<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001418<h3>
1419 <a name="include"><tt>llvm/include</tt></a>
1420</h3>
1421
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001422<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001423
1424<p>This directory contains public header files exported from the LLVM
1425library. The three main subdirectories of this directory are:</p>
1426
Reid Spencer77d90192004-09-05 20:50:22 +00001427<dl>
1428 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1429 <dd>This directory contains all of the LLVM specific header files. This
1430 directory also has subdirectories for different portions of LLVM:
1431 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1432 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001433
Reid Spencer77d90192004-09-05 20:50:22 +00001434 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1435 <dd>This directory contains generic support libraries that are provided with
1436 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1437 and a Command Line option processing library store their header files here.
1438 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001439
Reid Spencer77d90192004-09-05 20:50:22 +00001440 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1441 <dd>This directory contains header files configured by the <tt>configure</tt>
1442 script. They wrap "standard" UNIX and C header files. Source code can
1443 include these header files which automatically take care of the conditional
1444 #includes that the <tt>configure</tt> script generates.</dd>
1445</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001446</div>
1447
1448<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001449<h3>
1450 <a name="lib"><tt>llvm/lib</tt></a>
1451</h3>
1452
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001453<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001454
1455<p>This directory contains most of the source files of the LLVM system. In LLVM,
1456almost all code exists in libraries, making it very easy to share code among the
1457different <a href="#tools">tools</a>.</p>
1458
Misha Brukman54111c42004-01-20 00:20:17 +00001459<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001460 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1461 <dd> This directory holds the core LLVM source files that implement core
1462 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001463
Reid Spencer77d90192004-09-05 20:50:22 +00001464 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1465 <dd>This directory holds the source code for the LLVM assembly language parser
1466 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001467
Gabor Greif04367bf2007-07-06 22:07:22 +00001468 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1469 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001470
Reid Spencer77d90192004-09-05 20:50:22 +00001471 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001472 different program analyses, such as Dominator Information, Call Graphs,
1473 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001474 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001475
Reid Spencer77d90192004-09-05 20:50:22 +00001476 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1477 <dd> This directory contains the source code for the LLVM to LLVM program
1478 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1479 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1480 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001481
Reid Spencer77d90192004-09-05 20:50:22 +00001482 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1483 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001484 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1485 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001486 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001487
Reid Spencer77d90192004-09-05 20:50:22 +00001488 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1489 <dd> This directory contains the major parts of the code generator: Instruction
1490 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001491
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +00001492 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1493 <dd>(FIXME: T.B.D.)</dd>
1494
1495 <!--FIXME: obsoleted -->
Reid Spencer77d90192004-09-05 20:50:22 +00001496 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1497 <dd> This directory contains the source level debugger library that makes
1498 it possible to instrument LLVM programs so that a debugger could identify
1499 source code locations at which the program is executing.</dd>
1500
1501 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001502 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer77d90192004-09-05 20:50:22 +00001503 at runtime in both interpreted and JIT compiled fashions.</dd>
1504
1505 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar2c607b62011-10-11 20:02:52 +00001506 <dd> This directory contains the source code that corresponds to the header
1507 files located in <tt>llvm/include/ADT/</tt>
1508 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001509</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001510
Misha Brukman00c73d22003-11-07 19:43:14 +00001511</div>
John Criswell85ed3612003-06-12 19:34:44 +00001512
Misha Brukman00c73d22003-11-07 19:43:14 +00001513<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001514<h3>
1515 <a name="projects"><tt>llvm/projects</tt></a>
1516</h3>
1517
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001518<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001519 <p>This directory contains projects that are not strictly part of LLVM but are
1520 shipped with LLVM. This is also the directory where you should create your own
1521 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner4630e4d2008-08-11 06:13:31 +00001522 to set up your own project.</p>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001523</div>
1524
1525<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001526<h3>
1527 <a name="runtime"><tt>llvm/runtime</tt></a>
1528</h3>
1529
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001530<div>
John Criswell85ed3612003-06-12 19:34:44 +00001531
Gabor Greif04367bf2007-07-06 22:07:22 +00001532<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman00c73d22003-11-07 19:43:14 +00001533used when linking programs with the GCC front end. Most of these libraries are
1534skeleton versions of real libraries; for example, libc is a stripped down
1535version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001536
Misha Brukman00c73d22003-11-07 19:43:14 +00001537<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1538end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001539
Misha Brukman00c73d22003-11-07 19:43:14 +00001540</div>
John Criswell85ed3612003-06-12 19:34:44 +00001541
Misha Brukman00c73d22003-11-07 19:43:14 +00001542<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001543<h3>
1544 <a name="test"><tt>llvm/test</tt></a>
1545</h3>
1546
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001547<div>
Reid Spencer77d90192004-09-05 20:50:22 +00001548 <p>This directory contains feature and regression tests and other basic sanity
1549 checks on the LLVM infrastructure. These are intended to run quickly and cover
1550 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001551</div>
John Criswell85ed3612003-06-12 19:34:44 +00001552
Misha Brukman00c73d22003-11-07 19:43:14 +00001553<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001554<h3>
1555 <a name="test-suite"><tt>test-suite</tt></a>
1556</h3>
1557
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001558<div>
John Criswell9c29bfb2007-06-29 19:12:31 +00001559 <p>This is not a directory in the normal llvm module; it is a separate
1560 Subversion
1561 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1562 This
John Criswell3d8ba512004-12-08 17:53:54 +00001563 module contains a comprehensive correctness, performance, and benchmarking
1564 test
John Criswell9c29bfb2007-06-29 19:12:31 +00001565 suite for LLVM. It is a separate Subversion module because not every LLVM
1566 user is
John Criswell838bce52005-05-09 16:39:27 +00001567 interested in downloading or building such a comprehensive test suite. For
1568 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001569 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001570</div>
John Criswell85ed3612003-06-12 19:34:44 +00001571
Reid Spencer77d90192004-09-05 20:50:22 +00001572<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001573<h3>
1574 <a name="tools"><tt>llvm/tools</tt></a>
1575</h3>
1576
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001577<div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001578
Misha Brukman00c73d22003-11-07 19:43:14 +00001579<p>The <b>tools</b> directory contains the executables built out of the
1580libraries above, which form the main part of the user interface. You can
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001581always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001582following is a brief introduction to the most important tools. More detailed
1583information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001584
Misha Brukman54111c42004-01-20 00:20:17 +00001585<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001586
Reid Spencer77d90192004-09-05 20:50:22 +00001587 <dt><tt><b>bugpoint</b></tt></dt>
1588 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001589 optimization passes or code generation backends by narrowing down the
1590 given test case to the minimum number of passes and/or instructions that
1591 still cause a problem, whether it is a crash or miscompilation. See <a
1592 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001593 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001594
Reid Spencer77d90192004-09-05 20:50:22 +00001595 <dt><tt><b>llvm-ar</b></tt></dt>
1596 <dd>The archiver produces an archive containing
Gabor Greif04367bf2007-07-06 22:07:22 +00001597 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001598 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001599
Reid Spencer77d90192004-09-05 20:50:22 +00001600 <dt><tt><b>llvm-as</b></tt></dt>
1601 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001602 bitcode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001603
Reid Spencer77d90192004-09-05 20:50:22 +00001604 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001605 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer77d90192004-09-05 20:50:22 +00001606 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001607
Reid Spencer079e9452004-12-08 18:00:30 +00001608 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001609 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Eric Christopher78d08352011-09-20 00:42:28 +00001610 It performs standard link time optimizations and allows optimization
1611 modules to be loaded and run so that language specific optimizations can
1612 be applied at link time.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001613
Reid Spencer77d90192004-09-05 20:50:22 +00001614 <dt><tt><b>llvm-link</b></tt></dt>
1615 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1616 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001617
Reid Spencer77d90192004-09-05 20:50:22 +00001618 <dt><tt><b>lli</b></tt></dt>
1619 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky64270d52007-12-03 01:58:01 +00001620 can directly execute LLVM bitcode (although very slowly...). For architectures
1621 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1622 will function as a Just-In-Time compiler (if the functionality was compiled
1623 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001624
Reid Spencer77d90192004-09-05 20:50:22 +00001625 <dt><tt><b>llc</b></tt></dt>
1626 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greif04367bf2007-07-06 22:07:22 +00001627 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001628 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001629
Reid Spencerd4694f92004-12-22 06:29:07 +00001630 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001631 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1632 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001633 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencer434262a2007-02-09 15:59:08 +00001634 usual machine code output. It works just like any other GCC compiler,
1635 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1636 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell9c29bfb2007-06-29 19:12:31 +00001637 separate Subversion module.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001638
Reid Spencer77d90192004-09-05 20:50:22 +00001639 <dt><tt><b>opt</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001640 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer84f82f72006-08-28 00:34:19 +00001641 transformations (which are specified on the command line), and then outputs
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001642 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001643 get a list of the program transformations available in LLVM.<br>
Reid Spencer84f82f72006-08-28 00:34:19 +00001644 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greif04367bf2007-07-06 22:07:22 +00001645 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer84f82f72006-08-28 00:34:19 +00001646 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001647</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001648</div>
John Criswell85ed3612003-06-12 19:34:44 +00001649
Misha Brukman00c73d22003-11-07 19:43:14 +00001650<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001651<h3>
1652 <a name="utils"><tt>llvm/utils</tt></a>
1653</h3>
1654
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001655<div>
John Criswell85ed3612003-06-12 19:34:44 +00001656
Misha Brukman00c73d22003-11-07 19:43:14 +00001657<p>This directory contains utilities for working with LLVM source code, and some
1658of the utilities are actually required as part of the build process because they
1659are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001660
Misha Brukman54111c42004-01-20 00:20:17 +00001661<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001662 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001663 that finds differences between code that LLC generates and code that LLI
1664 generates. This is a useful tool if you are debugging one of them,
1665 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001666 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001667
Misha Brukman54111c42004-01-20 00:20:17 +00001668 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001669 syntax-highlighting files which will work with Emacs and XEmacs editors,
1670 providing syntax highlighting support for LLVM assembly files and TableGen
1671 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001672 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001673
Misha Brukman54111c42004-01-20 00:20:17 +00001674 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001675 and outputs all non-generated source files, which is useful if one wishes
1676 to do a lot of development across directories and does not want to
1677 individually find each file. One way to use it is to run, for example:
1678 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001679 tree.<br><br>
1680
Reid Spencer77d90192004-09-05 20:50:22 +00001681 <dt><tt><b>llvmgrep</b></tt></dt>
1682 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1683 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1684 line. This is a very efficient way of searching the source base for a
1685 particular regular expression.</dd>
1686
Misha Brukman54111c42004-01-20 00:20:17 +00001687 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001688 files in the current directory and then compiles and links the tool that
1689 is the first argument. For example, assuming you are in the directory
1690 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1691 simply running <tt>makellvm llc</tt> will make a build of the current
1692 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001693 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001694
Tanya Lattner7a857dd2007-05-22 06:12:51 +00001695 <dt><tt><b>NewNightlyTest.pl</b></tt> and
Misha Brukman54111c42004-01-20 00:20:17 +00001696 <tt><b>NightlyTestTemplate.html</b></tt> <dd>These files are used in a
Misha Brukman00c73d22003-11-07 19:43:14 +00001697 cron script to generate nightly status reports of the functionality of
1698 tools, and the results can be seen by following the appropriate link on
Chris Lattner9abd8af2006-09-07 04:19:09 +00001699 the <a href="http://llvm.org/">LLVM homepage</a>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001700
Misha Brukman54111c42004-01-20 00:20:17 +00001701 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001702 the tool used to generate register descriptions, instruction set
1703 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001704 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001705
Misha Brukman54111c42004-01-20 00:20:17 +00001706 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001707 syntax-highlighting files which will work with the VIM editor, providing
1708 syntax highlighting support for LLVM assembly files and TableGen
1709 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001710 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001711
Misha Brukman00c73d22003-11-07 19:43:14 +00001712</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001713
Misha Brukman00c73d22003-11-07 19:43:14 +00001714</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001715
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001716</div>
1717
Misha Brukman00c73d22003-11-07 19:43:14 +00001718<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001719<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001720 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001721</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001722<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001723
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001724<div>
Chris Lattner59075882007-01-04 07:08:27 +00001725<p>This section gives an example of using LLVM. llvm-gcc3 is now obsolete,
Chris Lattnerb357f042009-04-10 15:38:51 +00001726so we only include instructions for llvm-gcc4.
Chris Lattner5907d402006-08-14 20:45:25 +00001727</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001728
1729<p><b>Note:</b> The <i>gcc4</i> frontend's invocation is <b><i>considerably different</i></b>
1730from the previous <i>gcc3</i> frontend. In particular, the <i>gcc4</i> frontend <b><i>does not</i></b>
Gabor Greif04367bf2007-07-06 22:07:22 +00001731create bitcode by default: <i>gcc4</i> produces native code. As the example below illustrates,
1732the '--emit-llvm' flag is needed to produce LLVM bitcode output. For <i>makefiles</i> and
1733<i>configure</i> scripts, the CFLAGS variable needs '--emit-llvm' to produce bitcode
Chris Lattner9abd8af2006-09-07 04:19:09 +00001734output.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001735
1736<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001737<h3>
1738 <a name="tutorial4">Example with llvm-gcc4</a>
1739</h3>
Chris Lattner5907d402006-08-14 20:45:25 +00001740
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001741<div>
Chris Lattner5907d402006-08-14 20:45:25 +00001742
1743<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001744 <li><p>First, create a simple C file, name it 'hello.c':</p>
1745
1746<div class="doc_code">
1747<pre>
1748#include &lt;stdio.h&gt;
1749
1750int main() {
1751 printf("hello world\n");
1752 return 0;
1753}
1754</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001755
1756 <li><p>Next, compile the C file into a native executable:</p>
1757
Bill Wendling77f74692007-07-16 08:44:39 +00001758 <div class="doc_code"><pre>% llvm-gcc hello.c -o hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001759
1760 <p>Note that llvm-gcc works just like GCC by default. The standard -S and
1761 -c arguments work as usual (producing a native .s or .o file,
Bill Wendling77f74692007-07-16 08:44:39 +00001762 respectively).</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001763
Gabor Greif04367bf2007-07-06 22:07:22 +00001764 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendling77f74692007-07-16 08:44:39 +00001765
1766 <div class="doc_code">
1767 <pre>% llvm-gcc -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001768
1769 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1770 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1771 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Gabor Greif04367bf2007-07-06 22:07:22 +00001772 the bitcode file.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001773
1774 <p>Unlike llvm-gcc3, llvm-gcc4 correctly responds to -O[0123] arguments.
1775 </p></li>
1776
1777 <li><p>Run the program in both forms. To run the program, use:</p>
1778
Bill Wendling77f74692007-07-16 08:44:39 +00001779 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001780
1781 <p>and</p>
1782
Bill Wendling77f74692007-07-16 08:44:39 +00001783 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001784
1785 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001786 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001787
1788 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1789 code:</p>
1790
Bill Wendling77f74692007-07-16 08:44:39 +00001791<div class="doc_code">
1792<pre>llvm-dis &lt; hello.bc | less</pre>
1793</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001794
1795 <li><p>Compile the program to native assembly using the LLC code
1796 generator:</p>
1797
Bill Wendling77f74692007-07-16 08:44:39 +00001798 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001799
1800 <li><p>Assemble the native assembly language file into a program:</p>
1801
Bill Wendling77f74692007-07-16 08:44:39 +00001802<div class="doc_code">
1803<pre>
1804<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1805
1806<b>Others:</b> % gcc hello.s -o hello.native
1807</pre>
1808</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001809
1810 <li><p>Execute the native code program:</p>
1811
Bill Wendling77f74692007-07-16 08:44:39 +00001812 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001813
1814 <p>Note that using llvm-gcc to compile directly to native code (i.e. when
1815 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001816 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001817
1818</ol>
1819
1820</div>
1821
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001822</div>
John Criswell85ed3612003-06-12 19:34:44 +00001823
Misha Brukman00c73d22003-11-07 19:43:14 +00001824<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001825<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001826 <a name="problems">Common Problems</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001827</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001828<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001829
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001830<div>
John Criswellce760f62003-07-03 16:01:38 +00001831
Misha Brukman00c73d22003-11-07 19:43:14 +00001832<p>If you are having problems building or using LLVM, or if you have any other
1833general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1834Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001835
Misha Brukman00c73d22003-11-07 19:43:14 +00001836</div>
John Criswell85ed3612003-06-12 19:34:44 +00001837
Misha Brukman00c73d22003-11-07 19:43:14 +00001838<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001839<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001840 <a name="links">Links</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001841</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001842<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001843
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001844<div>
John Criswell85ed3612003-06-12 19:34:44 +00001845
Bill Wendling2d4c2152008-07-22 01:10:25 +00001846<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman00c73d22003-11-07 19:43:14 +00001847some simple things... there are many more interesting and complicated things
1848that you can do that aren't documented here (but we'll gladly accept a patch
1849if you want to write something up!). For more information about LLVM, check
1850out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001851
Misha Brukman00c73d22003-11-07 19:43:14 +00001852<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001853 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1854 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1855 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001856 that Uses LLVM</a></li>
1857</ul>
1858
1859</div>
1860
1861<!-- *********************************************************************** -->
1862
1863<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001864<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001865 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001866 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001867 <a href="http://validator.w3.org/check/referer"><img
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001868 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001869
Misha Brukman142207b2003-11-22 01:30:01 +00001870 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001871 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001872 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001873 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001874</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001875</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001876</html>