blob: 9db9bb26034197e391e1c5626f709e52d6871e18 [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>
Chad Rosier372b8222012-02-26 21:31:25 +000055 <li><a href="#tutorial4">Example with Clang</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
Jim Grosbachc48d4dc2012-01-25 22:00:23 +000085needed to use LLVM. It contains an assembler, disassembler, bitcode
86analyzer and bitcode optimizer. It also contains basic regression tests that
Chad Rosier372b8222012-02-26 21:31:25 +000087can be used to test the LLVM tools and the Clang front end.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000088
Chad Rosier483454f2012-02-26 21:34:02 +000089<p>The second piece is the <a href="http://clang.llvm.org/">Clang</a> front end.
90This component compiles C, C++, Objective C, and Objective C++ code into LLVM
91bitcode. Once compiled into LLVM bitcode, a program can be manipulated with the
92LLVM tools from the LLVM suite.
Chad Rosier372b8222012-02-26 21:31:25 +000093</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000094
John Criswell3d8ba512004-12-08 17:53:54 +000095<p>
Andrew Trickbcf01162010-09-23 20:26:44 +000096There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell3d8ba512004-12-08 17:53:54 +000097with a testing harness that can be used to further test LLVM's functionality
98and performance.
99</p>
100
Misha Brukman00c73d22003-11-07 19:43:14 +0000101</div>
102
103<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000104<h2>
105 <a name="quickstart">Getting Started Quickly (A Summary)</a>
106</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000107<!-- *********************************************************************** -->
108
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000109<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000110
Chad Rosier8ce6b7d2012-02-23 21:23:24 +0000111<p>The LLVM Getting Started documentation is <b>wildly</b> out of date and is
Chad Rosier89c5d262012-02-23 23:21:22 +0000112in dire need of an update. Most notably, Clang has replaced the GCC front end
Chad Rosier8ce6b7d2012-02-23 21:23:24 +0000113entirely and building with the LLVM GCC front end is no longer supported.
114The Clang <a href="http://clang.llvm.org/get_started.html">Getting Started</a>
115page might be a better place to start.</p>
116
Misha Brukman00c73d22003-11-07 19:43:14 +0000117<p>Here's the short story for getting up and running quickly with LLVM:</p>
118
119<ol>
Reid Spencer9f547912004-11-08 00:29:22 +0000120 <li>Read the documentation.</li>
121 <li>Read the documentation.</li>
122 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000123 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000124 (see <a href="#installcf">Install the GCC Front End</a> for details):
Misha Brukman00c73d22003-11-07 19:43:14 +0000125 <ol>
Reid Spencerd4694f92004-12-22 06:29:07 +0000126 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach18df1d42009-12-17 17:18:11 +0000127 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
128 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
129 <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 +0000130 <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 +0000131 <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 +0000132 </ol></li>
133
Misha Brukman9106eca2005-02-03 22:25:23 +0000134 <li>Get the LLVM Source Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000135 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000136 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman00c73d22003-11-07 19:43:14 +0000137 <ol>
138 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell364cec42004-03-12 20:31:37 +0000139 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +0000140 </ol></li>
141
Misha Brukman00c73d22003-11-07 19:43:14 +0000142 </ul></li>
143
Misha Brukman9106eca2005-02-03 22:25:23 +0000144 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswell9e2485c2004-12-10 15:51:16 +0000145 <ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000146 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswell9e2485c2004-12-10 15:51:16 +0000147 <ol>
148 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
149 <li><tt>cd llvm/projects</tt>
150 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000151 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswell9e2485c2004-12-10 15:51:16 +0000152 </ol></li>
153
John Criswell9e2485c2004-12-10 15:51:16 +0000154 </ul></li>
155
156
Misha Brukman00c73d22003-11-07 19:43:14 +0000157 <li>Configure the LLVM Build Environment
158 <ol>
Misha Brukman9106eca2005-02-03 22:25:23 +0000159 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
160 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
161 Some common options:
162
Misha Brukman00c73d22003-11-07 19:43:14 +0000163 <ul>
Reid Spencerd4694f92004-12-22 06:29:07 +0000164 <li><tt>--prefix=<i>directory</i></tt>
165 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000166 want the LLVM tools and libraries to be installed (default
167 <tt>/usr/local</tt>).</p></li>
Reid Spencerfef93b72004-12-26 05:47:26 +0000168 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
169 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswell838bce52005-05-09 16:39:27 +0000170 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sandsdc223762009-04-18 12:40:19 +0000171 not specified, the PATH will be searched. This is only needed if you
Andrew Trickbcf01162010-09-23 20:26:44 +0000172 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000173 <li><tt>--enable-spec2000=<i>directory</i></tt>
174 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
175 benchmarks should be available in
176 <tt><i>directory</i></tt>.</p></li>
177 </ul>
178 </ol></li>
179
180 <li>Build the LLVM Suite:
181 <ol>
Chris Lattner95e92582004-07-18 22:32:22 +0000182 <li><tt>gmake -k |&amp; tee gnumake.out
183 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000184 <li>If you get an "internal compiler error (ICE)" or test failures, see
185 <a href="#brokengcc">below</a>.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000186 </ol>
187
188</ol>
189
Chris Lattnerfcd37252004-06-21 22:52:48 +0000190<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000191detailed information on configuring and compiling LLVM. See <a
192href="#environment">Setting Up Your Environment</a> for tips that simplify
193working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
194Layout</a> to learn about the layout of the source code tree.</p>
195
196</div>
197
198<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000199<h2>
200 <a name="requirements">Requirements</a>
201</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000202<!-- *********************************************************************** -->
203
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000204<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000205
206<p>Before you begin to use the LLVM system, review the requirements given below.
207This may save you some trouble by knowing ahead of time what hardware and
208software you will need.</p>
209
Misha Brukman00c73d22003-11-07 19:43:14 +0000210<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000211<h3>
212 <a name="hardware">Hardware</a>
213</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000214
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000215<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000216
217<p>LLVM is known to work on the following platforms:</p>
218
Chris Lattner9abd8af2006-09-07 04:19:09 +0000219<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000220<tr>
221 <th>OS</th>
222 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000223 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000224</tr>
225<tr>
Chris Lattnerd8afc462009-07-22 04:21:40 +0000226 <td>AuroraUX</td>
227 <td>x86<sup><a href="#pf_1">1</a></sup></td>
228 <td>GCC</td>
Chris Lattner3e7b5ca2009-07-21 22:47:03 +0000229</tr>
230<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000231 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000232 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000233 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000234</tr>
235<tr>
Edward O'Callaghan37442b72009-08-04 05:24:28 +0000236 <td>Linux</td>
237 <td>amd64</td>
238 <td>GCC</td>
239</tr>
240<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000241 <td>Solaris</td>
242 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000243 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000244</tr>
245<tr>
246 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000247 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000248 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000249</tr>
250<tr>
Bill Wendlingf7226992010-12-15 01:35:55 +0000251 <td>FreeBSD</td>
252 <td>amd64</td>
253 <td>GCC</td>
254</tr>
255<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000256 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000257 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000258 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000259</tr>
260<tr>
Scott Michel050bc812008-03-18 23:13:26 +0000261 <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 +0000262 <td>x86</td>
263 <td>GCC</td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000264</tr>
265<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000266 <td>Cygwin/Win32</td>
Anton Korobeynikov16f16922009-12-09 17:26:02 +0000267 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
268 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000269 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman69def742004-11-19 21:53:22 +0000270</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000271<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000272 <td>MinGW/Win32</td>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000273 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000274 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
275 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000276 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000277</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000278</table>
279
280<p>LLVM has partial support for the following platforms:</p>
281
Chris Lattner9abd8af2006-09-07 04:19:09 +0000282<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000283<tr>
284 <th>OS</th>
285 <th>Arch</th>
286 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000287</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000288<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000289 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000290 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruth2929de42011-11-16 19:52:13 +0000291 <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 +0000292<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000293 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000294 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000295 <td>GCC</td>
296</tr>
297<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000298 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000299 <td>PowerPC</td>
300 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000301</tr>
John Criswell75162552005-05-09 16:49:59 +0000302
303<tr>
304 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
305 <td>Alpha</td>
306 <td>GCC</td>
307</tr>
308<tr>
309 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
310 <td>Itanium (IA-64)</td>
311 <td>GCC</td>
312</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000313<tr>
314 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
315 <td>Itanium (IA-64)</td>
316 <td>HP aCC</td>
317</tr>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000318<tr>
319 <td>Windows x64</td>
320 <td>x86-64</td>
321 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
322</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000323</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000324
Misha Brukmana892ead2005-02-09 21:01:26 +0000325<p><b>Notes:</b></p>
326
Misha Brukman6d8e1532005-02-09 22:38:47 +0000327<div class="doc_notes">
328<ol>
329<li><a name="pf_1">Code generation supported for Pentium processors and
330up</a></li>
331<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
332<li><a name="pf_3">No native code generation</a></li>
Nick Lewycky28ea4f62008-12-08 00:45:02 +0000333<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 +0000334<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner01bb8b02009-01-02 07:10:51 +0000335<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell75162552005-05-09 16:49:59 +0000336<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000337<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
338 generated by LLVM properly.</a></li>
Chris Lattner22b91d72008-11-09 17:19:14 +0000339<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 +0000340 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner22b91d72008-11-09 17:19:14 +0000341 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
342 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel050bc812008-03-18 23:13:26 +0000343 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000344<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
345 version of the perl package, and be sure it appears in your path
346 before any Windows-based versions such as Strawberry Perl and
347 ActivePerl, as these have Windows-specifics that will cause the
348 build to fail.</a></li>
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000349<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000350 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000351<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000352 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000353</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000354</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000355
Misha Brukman69def742004-11-19 21:53:22 +0000356<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 +0000357mode, depending on the system (it is so large because of all the debugging
358information and the fact that the libraries are statically linked into multiple
Chris Lattner06942902009-04-25 22:08:52 +0000359tools). If you do not need many of the tools and you are space-conscious, you
360can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
361requires considerably less space.</p>
Misha Brukman69def742004-11-19 21:53:22 +0000362
Misha Brukman00c73d22003-11-07 19:43:14 +0000363<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
364guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greif04367bf2007-07-06 22:07:22 +0000365able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000366generation should work as well, although the generated native code may not work
367on your platform.</p>
368
369<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 +0000370to work on another platform, you can download a copy of the source and <a
Duncan Sands8655b152008-02-14 17:53:22 +0000371href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000372
373</div>
374
375<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000376<h3>
377 <a name="software">Software</a>
378</h3>
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000379<div>
Reid Spencer748d82e2004-11-15 21:15:12 +0000380 <p>Compiling LLVM requires that you have several software packages
381 installed. The table below lists those required packages. The Package column
382 is the usual name for the software package that LLVM depends on. The Version
383 column provides "known to work" versions of the package. The Notes column
384 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000385 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000386 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000387
Reid Spencer748d82e2004-11-15 21:15:12 +0000388 <tr>
389 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
390 <td>3.79, 3.79.1</td>
391 <td>Makefile/build processor</td>
392 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000393
Reid Spencer748d82e2004-11-15 21:15:12 +0000394 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000395 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000396 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000397 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000398 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000399
Reid Spencer748d82e2004-11-15 21:15:12 +0000400 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000401 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattner2286cab2005-09-06 04:07:15 +0000402 <td>4.5</td>
403 <td>For building the CFE</td>
404 </tr>
405
406 <tr>
John Criswell9c29bfb2007-06-29 19:12:31 +0000407 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
408 <td>&ge;1.3</td>
409 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000410 </tr>
411
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +0000412 <!-- FIXME:
413 Do we support dg?
414 Are DejaGnu and expect obsolete?
415 Shall we mention Python? -->
416
Misha Brukman6d8e1532005-02-09 22:38:47 +0000417 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000418 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
419 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000420 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000421 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000422
Reid Spencer748d82e2004-11-15 21:15:12 +0000423 <tr>
424 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
425 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000426 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000427 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000428
Reid Spencer748d82e2004-11-15 21:15:12 +0000429 <tr>
430 <td><a href="http://expect.nist.gov/">expect</a></td>
431 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000432 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000433 </tr>
434
435 <tr>
436 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000437 <td>&ge;5.6.0</td>
Daniel Dunbar5b106562012-02-15 19:24:11 +0000438 <td>Utilities</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000439 </tr>
440
441 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000442 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
443 <td>1.4</td>
444 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000445 </tr>
446
447 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000448 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000449 <td>2.60</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000450 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
451 </tr>
452
453 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000454 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000455 <td>1.9.6</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000456 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
457 </tr>
458
459 <tr>
460 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000461 <td>1.5.22</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000462 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000463 </tr>
464
465 </table>
466
Misha Brukman6d8e1532005-02-09 22:38:47 +0000467 <p><b>Notes:</b></p>
468 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000469 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000470 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000471 need to build the other languages for LLVM's purposes.</a> See
472 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell9c29bfb2007-06-29 19:12:31 +0000473 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman6d8e1532005-02-09 22:38:47 +0000474 latest LLVM sources. If you're working from a release distribution, you
John Criswell9c29bfb2007-06-29 19:12:31 +0000475 don't need Subversion.</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000476 <li><a name="sf3">Only needed if you want to run the automated test
477 suite in the <tt>llvm/test</tt> directory.</a></li>
478 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser0560ce42010-05-19 07:00:17 +0000479 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
480 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer200d93b2004-12-09 17:55:37 +0000481 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000482 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000483 </div>
484
Reid Spencer748d82e2004-11-15 21:15:12 +0000485 <p>Additionally, your compilation host is expected to have the usual
486 plethora of Unix utilities. Specifically:</p>
487 <ul>
488 <li><b>ar</b> - archive library builder</li>
489 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
490 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
491 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000492 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000493 <li><b>cp</b> - copy files</li>
494 <li><b>date</b> - print the current date/time </li>
495 <li><b>echo</b> - print to standard output</li>
496 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000497 <li><b>find</b> - find files/dirs in a file system</li>
498 <li><b>grep</b> - regular expression search utility</li>
499 <li><b>gzip*</b> - gzip command for distribution generation</li>
500 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
501 <li><b>install</b> - install directories/files </li>
502 <li><b>mkdir</b> - create a directory</li>
503 <li><b>mv</b> - move (rename) files</li>
504 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000505 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000506 <li><b>sed</b> - stream editor for transforming output</li>
507 <li><b>sh</b> - Bourne shell for make build scripts</li>
508 <li><b>tar</b> - tape archive for distribution generation</li>
509 <li><b>test</b> - test things in file system</li>
510 <li><b>unzip*</b> - unzip command for distribution checking</li>
511 <li><b>zip*</b> - zip command for distribution generation</li>
512 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000513</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000514
Chris Lattner95e92582004-07-18 22:32:22 +0000515<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000516<h3>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000517 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000518</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000519
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000520<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000521
522<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
523bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenek0ba11792011-10-31 21:23:15 +0000524to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
525Other versions of GCC will probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000526here are known to not work. If you are using one of these versions, please try
527to upgrade your GCC to something more recent. If you run into a problem with a
528version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
529us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
530of GCC you are using.
531</p>
532
533<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
534problems in the STL that effectively prevent it from compiling LLVM.
535</p>
536
Chris Lattner82f0a092008-02-13 17:50:24 +0000537<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
538a bogus template error. This was fixed in later GCCs.</p>
John Criswell294ba022004-11-23 22:06:24 +0000539
Chris Lattner95e92582004-07-18 22:32:22 +0000540<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
541href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
542the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000543
Chris Lattner8e64f152005-02-13 22:20:49 +0000544<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 +0000545 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner8e64f152005-02-13 22:20:49 +0000546 to a newer version</a> if possible.</p>
547<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
548 possibly others) does not compile LLVM correctly (it appears that exception
549 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
550 to a newer version of GCC.</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000551<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000552 code generator, causing an infinite loop in the llvm-gcc build when built
553 with optimizations enabled (i.e. a release build).</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000554<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000555 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
556 correctly compiles LLVM at -O2. A work around is to build release LLVM
557 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000558<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 +0000559 miscompiles portions of LLVM</a>.</p>
Chris Lattner269f80c2007-11-01 04:20:16 +0000560<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
561 when building with optimizations enabled. It appears to work with
562 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
563 build.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000564<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
565 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000566<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
567 default with ENABLE_OPTIMIZED=1. To work around this, build with
568 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000569<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
570 compiling some files. At the time of this writing, GCC mainline (4.2)
571 did not share the problem.</p>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000572<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
573 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
574 code. LLVM will appear to mostly work but will be buggy, e.g. failing
575 portions of its testsuite.</p>
Reid Spencer72f92f02007-04-11 21:28:31 +0000576<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
577platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbarb7dfaf92008-10-11 18:40:33 +0000578<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
579to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
580about symbols remaining in the table on destruction.</p>
Nuno Lopesf82242d2008-12-10 16:11:10 +0000581<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 +0000582as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Mike Stumpfe095f32009-05-04 18:40:41 +0000583<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
584 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
585 with link errors when using this GCC version.</p>
Chris Lattner478e71d2009-09-10 16:25:02 +0000586<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 +0000587<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
588when optimizations are turned on. The symptom is an infinite loop in
Chris Lattner478e71d2009-09-10 16:25:02 +0000589FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewycky256f9602010-10-07 22:30:47 +0000590<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5911</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
592one symptom of the problem.
Reid Spencer7a119082006-11-04 00:33:42 +0000593<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
594long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
595defined in a discarded section. You can safely ignore these messages as they are
596erroneous and the linkage is correct. These messages disappear using ld
5972.17.</p>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000598
599<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
600href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
601causes huge link times (minutes instead of seconds) when building LLVM. We
602recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
603
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000604<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000605<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
606which causes intermittent failures when building LLVM with position independent
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000607code. The symptom is an error about cyclic dependencies. We recommend
608upgrading to a newer version of Gold.</p>
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000609
Misha Brukman00c73d22003-11-07 19:43:14 +0000610</div>
611
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000612</div>
Chris Lattner95e92582004-07-18 22:32:22 +0000613
Misha Brukman00c73d22003-11-07 19:43:14 +0000614<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000615<h2>
616 <a name="starting">Getting Started with LLVM</a>
617</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000618<!-- *********************************************************************** -->
619
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000620<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000621
622<p>The remainder of this guide is meant to get you up and running with
623LLVM and to give you some basic information about the LLVM environment.</p>
624
625<p>The later sections of this guide describe the <a
626href="#layout">general layout</a> of the the LLVM source tree, a <a
627href="#tutorial">simple example</a> using the LLVM tool chain, and <a
628href="#links">links</a> to find more information about LLVM or to get
629help via e-mail.</p>
Chris Lattner95e92582004-07-18 22:32:22 +0000630
Misha Brukman00c73d22003-11-07 19:43:14 +0000631<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000632<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000633 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000634</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000635
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000636<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000637
638<p>Throughout this manual, the following names are used to denote paths
639specific to the local system and working environment. <i>These are not
640environment variables you need to set but just strings used in the rest
641of this document below</i>. In any of the examples below, simply replace
642each of these names with the appropriate pathname on your local system.
643All these paths are absolute:</p>
644
Misha Brukman54111c42004-01-20 00:20:17 +0000645<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000646 <dt>SRC_ROOT
647 <dd>
648 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000649 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000650
Misha Brukman00c73d22003-11-07 19:43:14 +0000651 <dt>OBJ_ROOT
652 <dd>
653 This is the top level directory of the LLVM object tree (i.e. the
654 tree where object files and compiled programs will be placed. It
655 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000656 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000657
658 <dt>LLVMGCCDIR
659 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000660 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000661 <p>
662 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000663 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +0000664</dl>
665
666</div>
667
668<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000669<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000670 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000671</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000672
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000673<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000674
675<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000676In order to compile and use LLVM, you may need to set some environment
677variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000678
Misha Brukman54111c42004-01-20 00:20:17 +0000679<dl>
Gabor Greif04367bf2007-07-06 22:07:22 +0000680 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000681 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greif04367bf2007-07-06 22:07:22 +0000682 locations of your bitcode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000683 convenience since you can specify the paths using the -L options of the
Gabor Greif04367bf2007-07-06 22:07:22 +0000684 tools and the C/C++ front-end will automatically use the bitcode files
John Criswell8bfe6a72005-05-18 19:43:33 +0000685 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000686 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000687</dl>
688
689</div>
690
691<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000692<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000693 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000694</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000695
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000696<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000697
698<p>
699If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000700can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000701suite and the LLVM GCC front end compiled for your platform. There is an
702additional test suite that is optional. Each file is a TAR archive that is
703compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000704</p>
705
Misha Brukman3ce11032005-02-02 18:01:57 +0000706<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000707<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000708 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000709 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000710
Misha Brukman3ce11032005-02-02 18:01:57 +0000711 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000712 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000713
Misha Brukmanccd02952008-12-29 19:38:58 +0000714 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
715 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000716 directory for build instructions.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000717
Misha Brukmanccd02952008-12-29 19:38:58 +0000718 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
719 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000720
Misha Brukman00c73d22003-11-07 19:43:14 +0000721</dl>
722
723</div>
724
725<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000726<h3>
John Criswell9c29bfb2007-06-29 19:12:31 +0000727 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000728</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000729
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000730<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000731
John Criswell9c29bfb2007-06-29 19:12:31 +0000732<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000733the entire source code. All you need to do is check it out from Subversion as
Misha Brukman00c73d22003-11-07 19:43:14 +0000734follows:</p>
735
736<ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000737 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov98044e42007-06-29 20:56:49 +0000738 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
739 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell9c29bfb2007-06-29 19:12:31 +0000740 llvm</tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000741</ul>
742
John Criswell9c29bfb2007-06-29 19:12:31 +0000743
Misha Brukman00c73d22003-11-07 19:43:14 +0000744<p>This will create an '<tt>llvm</tt>' directory in the current
745directory and fully populate it with the LLVM source code, Makefiles,
746test directories, and local copies of documentation files.</p>
747
Misha Brukman54111c42004-01-20 00:20:17 +0000748<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikovd933fa92007-06-29 23:13:42 +0000749revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikovd724dc82007-06-30 00:00:57 +0000750'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman9474d012008-12-17 16:27:23 +0000751subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000752
John Criswelld000e1d2003-12-18 16:43:17 +0000753<ul>
Bill Wendlingc3b94fb2011-04-04 23:42:51 +0000754<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc44c2452010-10-06 23:50:30 +0000755<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner994526c2010-10-06 05:36:01 +0000756<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattnerf08803b2009-10-23 06:20:06 +0000757<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000758<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman9474d012008-12-17 16:27:23 +0000759<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattnerb37ef512008-06-09 06:02:09 +0000760<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattnerdd50f0f2008-02-12 02:42:55 +0000761<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner76385652007-09-28 22:50:54 +0000762<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattner1dcadec2007-05-22 06:06:22 +0000763<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner134693a2006-11-20 06:07:10 +0000764<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000765<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattner993b9802006-04-20 04:35:34 +0000766<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000767<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000768<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000769<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000770<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000771<li>Release 1.2: <b>RELEASE_12</b></li>
772<li>Release 1.1: <b>RELEASE_11</b></li>
773<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000774</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000775
Reid Spencer66db92e2004-12-08 16:51:31 +0000776<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 +0000777you get it from the Subversion repository:</p>
Bill Wendling77f74692007-07-16 08:44:39 +0000778
779<div class="doc_code">
Reid Spencer66db92e2004-12-08 16:51:31 +0000780<pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000781% cd llvm/projects
Andrew Trickbcf01162010-09-23 20:26:44 +0000782% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencer66db92e2004-12-08 16:51:31 +0000783</pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000784</div>
785
Reid Spencer66db92e2004-12-08 16:51:31 +0000786<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000787configured by the LLVM configure script as well as automatically updated when
John Criswell9c29bfb2007-06-29 19:12:31 +0000788you run <tt>svn update</tt>.</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000789
Chris Lattner82ad9f12007-03-06 06:27:34 +0000790<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 +0000791and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner82ad9f12007-03-06 06:27:34 +0000792instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000793
Misha Brukman00c73d22003-11-07 19:43:14 +0000794</div>
795
796<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000797<h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000798 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000799</h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000800
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000801<div>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000802
803<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
804 sync automatically with each Subversion commit and contain all necessary
805 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
806 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000807 read-only GIT clone of LLVM via:</p>
808
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000809<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000810git clone http://llvm.org/git/llvm.git
811</pre>
812
813<p>If you want to check out clang too, run:</p>
814
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000815<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000816git clone http://llvm.org/git/llvm.git
817cd llvm/tools
818git clone http://llvm.org/git/clang.git
819</pre>
820
NAKAMURA Takumi7a362f42011-08-12 07:48:01 +0000821<p>
822Since the upstream repository is in Subversion, you should use
823<tt>&quot;git pull --rebase&quot;</tt>
824instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
825history in your clone.
826To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
827on the master branch, run the following command:
828</p>
829
830<pre class="doc_code">
831git config branch.master.rebase true
832</pre>
833
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000834<h4>Sending patches with Git</h4>
835<div>
836<p>
837Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
838</p>
839
840<p>
841Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
842working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
843At first you may check sanity of whitespaces:
844</p>
845
846<pre class="doc_code">
847git diff --check master..mybranch
848</pre>
849
850<p>
851The easiest way to generate a patch is as below:
852</p>
853
854<pre class="doc_code">
855git diff master..mybranch &gt; /path/to/mybranch.diff
856</pre>
857
858<p>
859It is a little different from svn-generated diff. git-diff-generated diff has
860prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
861know it could be accepted with <tt>patch -p1 -N</tt>.
862</p>
863
864<p>
865But you may generate patchset with git-format-patch. It generates
866by-each-commit patchset. To generate patch files to attach to your article:
867</p>
868
869<pre class="doc_code">
870git format-patch --no-attach master..mybranch -o /path/to/your/patchset
871</pre>
872
873<p>
874If you would like to send patches directly, you may use git-send-email or
875git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
876</p>
877
878<pre class="doc_code">
879git format-patch --attach master..mybranch --stdout | git imap-send
880</pre>
881
882<p>
883Then, your .git/config should have [imap] sections.
884</p>
885
886<pre class="doc_code">
887[imap]
888 host = imaps://imap.gmail.com
889 user = <em>your.gmail.account</em>@gmail.com
890 pass = <em>himitsu!</em>
891 port = 993
892 sslverify = false
893; in English
894 folder = "[Gmail]/Drafts"
895; example for Japanese, "Modified UTF-7" encoded.
896 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumi0dd4f102011-11-06 06:51:58 +0000897; example for Traditional Chinese
898 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000899</pre>
900
901</div>
902
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000903<h4>For developers to work with git-svn</h4>
904<div>
905
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000906<p>To set up clone from which you can submit code using
907 <tt>git-svn</tt>, run:</p>
908
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000909<pre class="doc_code">
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000910git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000911cd llvm
912git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
913git config svn-remote.svn.fetch :refs/remotes/origin/master
914git svn rebase -l # -l avoids fetching ahead of the git mirror.
915
916# If you have clang too:
917cd tools
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000918git clone http://llvm.org/git/clang.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000919cd clang
920git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
921git config svn-remote.svn.fetch :refs/remotes/origin/master
922git svn rebase -l
923</pre>
924
925<p>To update this clone without generating git-svn tags that conflict
926with the upstream git repo, run:</p>
927
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000928<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000929git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
930git checkout master
931git svn rebase -l
932(cd tools/clang &&
933 git checkout master &&
934 git svn rebase -l)
935</pre>
936
937<p>This leaves your working directories on their master branches, so
938you'll need to <tt>checkout</tt> each working branch individually and
939<tt>rebase</tt> it on top of its parent branch. (Note: This script is
940intended for relative newbies to git. If you have more experience,
941you can likely improve on it.)</p>
942
943<p>The git-svn metadata can get out of sync after you mess around with
944branches and <code>dcommit</code>. When that happens, <code>git svn
945dcommit</code> stops working, complaining about files with uncommitted
946changes. The fix is to rebuild the metadata:</p>
947
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000948<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000949rm -rf .git/svn
950git svn rebase -l
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000951</pre>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000952
953</div>
954
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000955</div>
956
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000957<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000958<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000959 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000960</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000961
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000962<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000963
Jim Grosbach18df1d42009-12-17 17:18:11 +0000964<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
965GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trickbcf01162010-09-23 20:26:44 +0000966It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach18df1d42009-12-17 17:18:11 +0000967you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000968main LLVM repository.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000969
Jim Grosbach18df1d42009-12-17 17:18:11 +0000970<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000971like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000972
973<ol>
974 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukmanccd02952008-12-29 19:38:58 +0000975 <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 +0000976 -</tt></li>
977</ol>
978
Jim Grosbach18df1d42009-12-17 17:18:11 +0000979<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
980<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
981Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
982to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
983<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
984
985<p>If you now want to build LLVM from source, when you configure LLVM, it will
986automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trickbcf01162010-09-23 20:26:44 +0000987use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach18df1d42009-12-17 17:18:11 +0000988point after building the main LLVM repository: just reconfigure llvm and
Andrew Trickbcf01162010-09-23 20:26:44 +0000989test-suite will pick it up.
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000990</p>
991
Jim Grosbach18df1d42009-12-17 17:18:11 +0000992<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
993versions of the required w32api and mingw-runtime binaries. The last remaining step for
994Windows users is to simply uncompress the binary binutils package from
995<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
996front end installation steps are not quite the same as a typical manual MinGW installation,
997they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000998
Jim Grosbach18df1d42009-12-17 17:18:11 +0000999<p>To install binutils on Windows:</p>
1000
1001<ol>
1002 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
1003 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
1004 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
1005</ol>
1006
1007<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
1008example, the binary distribution may include an old version of a system header
1009file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
1010libraries not available on your system. In cases like these, you may want to try
1011<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
1012this is much easier now than it was in the past.</p>
1013
1014<p>We also do not currently support updating of the GCC front end by manually overlaying
1015newer versions of the w32api and mingw-runtime binary packages that may become available
1016from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
1017a self-contained convenience package that requires Windows users to simply download and
1018uncompress the GNU Binutils binary package from the MinGW project.</p>
1019
1020<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
1021binaries is not as easy as previously described, or you would like to suggest improvements,
1022please let us know how you would like to see things improved by dropping us a note on our
1023<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001024
1025</div>
1026
1027<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001028<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001029 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001030</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001031
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001032<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001033
John Criswell9c29bfb2007-06-29 19:12:31 +00001034 <p>Once checked out from the Subversion repository, the LLVM suite source
1035 code must be
Reid Spencer66db92e2004-12-08 16:51:31 +00001036configured via the <tt>configure</tt> script. This script sets variables in the
1037various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
1038<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
1039the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001040
1041<p>The following environment variables are used by the <tt>configure</tt>
1042script to configure the build system:</p>
1043
Chris Lattner9abd8af2006-09-07 04:19:09 +00001044<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +00001045 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001046 <tr>
1047 <td>CC</td>
1048 <td>Tells <tt>configure</tt> which C compiler to use. By default,
1049 <tt>configure</tt> will look for the first GCC C compiler in
1050 <tt>PATH</tt>. Use this variable to override
1051 <tt>configure</tt>'s default behavior.</td>
1052 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001053 <tr>
1054 <td>CXX</td>
1055 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
1056 <tt>configure</tt> will look for the first GCC C++ compiler in
1057 <tt>PATH</tt>. Use this variable to override
1058 <tt>configure</tt>'s default behavior.</td>
1059 </tr>
1060</table>
1061
1062<p>The following options can be used to set or enable LLVM specific options:</p>
1063
Misha Brukman54111c42004-01-20 00:20:17 +00001064<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +00001065 <dt><i>--with-llvmgccdir</i></dt>
1066 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
1067 The value of this option should specify the full pathname of the C/C++ Front
1068 End to be used. If this option is not provided, the PATH will be searched for
1069 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
1070 be inferred from the path found. If the option is not given, and no llvm-gcc
1071 can be found in the path then a warning will be produced by
1072 <tt>configure</tt> indicating this situation. LLVM may still be built with
1073 the <tt>tools-only</tt> target but attempting to build the runtime libraries
1074 will fail as these libraries require llvm-gcc and llvm-g++. See
1075 <a href="#installcf">Install the GCC Front End</a> for details on installing
1076 the C/C++ Front End. See
Duncan Sands8655b152008-02-14 17:53:22 +00001077 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencerfef93b72004-12-26 05:47:26 +00001078 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001079 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +00001080 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +00001081 found. Use this if you have multiple tcl installations on your machine and you
1082 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
1083 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +00001084 option, the LLVM configure script will search for the tcl 8.4 and 8.3
1085 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001086 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001087 </dd>
1088 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001089 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001090 Enables optimized compilation (debugging symbols are removed
1091 and GCC optimization flags are enabled). Note that this is the default
1092 setting if you are using the LLVM distribution. The default behavior
1093 of an Subversion checkout is to use an unoptimized build (also known as a
1094 debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +00001095 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001096 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +00001097 <dt><i>--enable-debug-runtime</i></dt>
1098 <dd>
1099 Enables debug symbols in the runtime libraries. The default is to strip
1100 debug symbols from the runtime libraries.
1101 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001102 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001103 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +00001104 Compile the Just In Time (JIT) compiler functionality. This is not
1105 available
Misha Brukman00c73d22003-11-07 19:43:14 +00001106 on all platforms. The default is dependent on platform, so it is best
1107 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001108 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001109 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +00001110 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1111 <dd>Controls which targets will be built and linked into llc. The default
1112 value for <tt>target_options</tt> is "all" which builds and links all
1113 available targets. The value "host-only" can be specified to build only a
1114 native compiler (no cross-compiler targets available). The "native" target is
1115 selected as the target of the build host. You can also specify a comma
1116 separated list of target names that you want available in llc. The target
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001117 names use all lower case. The current set of targets is: <br>
Jia Liu060047f2012-02-10 04:58:24 +00001118 <tt>arm, cbe, cpp, hexagon, mblaze, mips, mipsel, msp430, powerpc, ptx, sparc, spu, x86, x86_64, xcore</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001119 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001120 <dt><i>--enable-doxygen</i></dt>
1121 <dd>Look for the doxygen program and enable construction of doxygen based
1122 documentation from the source code. This is disabled by default because
1123 generating the documentation can take a long time and producess 100s of
1124 megabytes of output.</dd>
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +00001125 <dt><i>--with-udis86</i></dt>
1126 <dd>LLVM can use external disassembler library for various purposes (now it's
1127 used only for examining code produced by JIT). This option will enable usage
1128 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1129 bits) disassembler library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001130</dl>
1131
1132<p>To configure LLVM, follow these steps:</p>
1133
1134<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001135 <li><p>Change directory into the object root directory:</p>
John Criswell0f6d7c02003-10-27 18:18:16 +00001136
Bill Wendling77f74692007-07-16 08:44:39 +00001137 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1138
1139 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1140 tree:</p>
1141
1142 <div class="doc_code">
1143 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1144 </div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001145</ol>
John Criswell85ed3612003-06-12 19:34:44 +00001146
Misha Brukman00c73d22003-11-07 19:43:14 +00001147</div>
John Criswell85ed3612003-06-12 19:34:44 +00001148
Misha Brukman00c73d22003-11-07 19:43:14 +00001149<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001150<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001151 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001152</h3>
John Criswell85ed3612003-06-12 19:34:44 +00001153
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001154<div>
John Criswell0b459202003-07-08 20:35:59 +00001155
Misha Brukman00c73d22003-11-07 19:43:14 +00001156<p>Once you have configured LLVM, you can build it. There are three types of
1157builds:</p>
John Criswell0b459202003-07-08 20:35:59 +00001158
Misha Brukman54111c42004-01-20 00:20:17 +00001159<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001160 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +00001161 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001162 These builds are the default when one is using an Subversion checkout and
1163 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1164 used during configuration). The build system will compile the tools and
1165 libraries with debugging information. To get a Debug Build using the
1166 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1167 to <tt>configure</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001168 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001169
1170 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +00001171 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001172 These builds are enabled with the <tt>--enable-optimized</tt> option to
1173 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1174 <tt>gmake</tt> command line. For these builds, the build system will
1175 compile the tools and libraries with GCC optimizations enabled and strip
1176 debugging information from the libraries and executables it generates.
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001177 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001178 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001179
1180 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +00001181 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001182 These builds are for use with profiling. They compile profiling
1183 information into the code for use with programs like <tt>gprof</tt>.
1184 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1185 on the <tt>gmake</tt> command line.
1186</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001187
Misha Brukman00c73d22003-11-07 19:43:14 +00001188<p>Once you have LLVM configured, you can build it by entering the
1189<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001190
Bill Wendling77f74692007-07-16 08:44:39 +00001191<div class="doc_code"><pre>% gmake</pre></div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001192
Chris Lattner95e92582004-07-18 22:32:22 +00001193<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +00001194are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +00001195
1196<p>
1197If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +00001198the parallel build options provided by GNU Make. For example, you could use the
1199command:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001200
Bill Wendling77f74692007-07-16 08:44:39 +00001201<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellce760f62003-07-03 16:01:38 +00001202
Misha Brukman00c73d22003-11-07 19:43:14 +00001203<p>There are several special targets which are useful when working with the LLVM
1204source code:</p>
John Criswellce760f62003-07-03 16:01:38 +00001205
Misha Brukman54111c42004-01-20 00:20:17 +00001206<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001207 <dt><tt>gmake clean</tt>
1208 <dd>
1209 Removes all files generated by the build. This includes object files,
1210 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001211 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001212
Reid Spencer66db92e2004-12-08 16:51:31 +00001213 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001214 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +00001215 Removes everything that <tt>gmake clean</tt> does, but also removes files
1216 generated by <tt>configure</tt>. It attempts to return the source tree to the
1217 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001218 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001219
Misha Brukmane51c3562004-08-23 20:25:33 +00001220 <dt><tt>gmake install</tt>
1221 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +00001222 Installs LLVM header files, libraries, tools, and documentation in a
1223 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +00001224 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1225 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001226 <br><br>
1227
Reid Spencer66db92e2004-12-08 16:51:31 +00001228 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001229 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +00001230 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greif04367bf2007-07-06 22:07:22 +00001231 install bitcode libraries into the GCC front end's bitcode library
1232 directory. If you need to update your bitcode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +00001233 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001234 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001235</dl>
John Criswellce760f62003-07-03 16:01:38 +00001236
Reid Spencer66db92e2004-12-08 16:51:31 +00001237<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1238details on these <tt>make</tt> targets and descriptions of other targets
1239available.</p>
1240
Misha Brukman00c73d22003-11-07 19:43:14 +00001241<p>It is also possible to override default values from <tt>configure</tt> by
1242declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +00001243
Misha Brukman54111c42004-01-20 00:20:17 +00001244<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001245 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1246 <dd>
1247 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001248 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001249
Reid Spencer004ba032006-04-09 23:45:38 +00001250 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +00001251 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +00001252 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001253 <br><br>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001254
1255 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1256 <dd>
1257 Perform a Debug build.
1258 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +00001259
Misha Brukman00c73d22003-11-07 19:43:14 +00001260 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1261 <dd>
1262 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001263 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001264
Misha Brukman00c73d22003-11-07 19:43:14 +00001265 <dt><tt>gmake VERBOSE=1</tt>
1266 <dd>
1267 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001268 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001269
1270 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1271 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +00001272 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001273 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001274</dl>
John Criswellce760f62003-07-03 16:01:38 +00001275
Misha Brukman00c73d22003-11-07 19:43:14 +00001276<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1277it and any subdirectories that it contains. Entering any directory inside the
1278LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1279that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +00001280
Misha Brukman00c73d22003-11-07 19:43:14 +00001281</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001282
Misha Brukman00c73d22003-11-07 19:43:14 +00001283<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001284<h3>
Reid Spencerd30a9712006-07-27 06:41:31 +00001285 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001286</h3>
Reid Spencer17850ef2006-07-27 05:43:30 +00001287
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001288<div>
Jim Grosbach5bea8222009-04-17 17:25:16 +00001289 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1290 executables and libraries to be hosted on a platform different from the
1291 platform where they are build (a Canadian Cross build). To configure a
1292 cross-compile, supply the configure script with <tt>--build</tt> and
1293 <tt>--host</tt> options that are different. The values of these options must
1294 be legal target triples that your GCC compiler supports.</p>
1295
1296 <p>The result of such a build is executables that are not runnable on
1297 on the build host (--build option) but can be executed on the compile host
Reid Spencerd30a9712006-07-27 06:41:31 +00001298 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001299</div>
1300
1301<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001302<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001303 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001304</h3>
John Criswell20d2d3e2003-10-10 14:26:14 +00001305
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001306<div>
John Criswellce760f62003-07-03 16:01:38 +00001307
Misha Brukman00c73d22003-11-07 19:43:14 +00001308<p>The LLVM build system is capable of sharing a single LLVM source tree among
1309several LLVM builds. Hence, it is possible to build LLVM for several different
1310platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001311
Misha Brukman00c73d22003-11-07 19:43:14 +00001312<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001313
Misha Brukman00c73d22003-11-07 19:43:14 +00001314<ul>
1315 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001316
Bill Wendling77f74692007-07-16 08:44:39 +00001317 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellce760f62003-07-03 16:01:38 +00001318
Misha Brukman00c73d22003-11-07 19:43:14 +00001319 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1320 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001321
Bill Wendling77f74692007-07-16 08:44:39 +00001322 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001323</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001324
Misha Brukman00c73d22003-11-07 19:43:14 +00001325<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1326named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001327
Misha Brukman54111c42004-01-20 00:20:17 +00001328<dl>
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001329 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman00c73d22003-11-07 19:43:14 +00001330 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001331 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001332 <dt>Tools
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001333 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001334 <dt>Libraries
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001335 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001336 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001337 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001338
Misha Brukman00c73d22003-11-07 19:43:14 +00001339 <dt>Release Builds
1340 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001341 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001342 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001343 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001344 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001345 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001346 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001347 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001348
Misha Brukman00c73d22003-11-07 19:43:14 +00001349 <dt>Profile Builds
1350 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001351 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001352 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001353 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001354 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001355 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001356 </dl>
1357</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001358
Misha Brukman00c73d22003-11-07 19:43:14 +00001359</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001360
Chris Lattnera553f622004-03-25 20:38:40 +00001361<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001362<h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001363 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001364</h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001365
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001366<div>
Chris Lattnera553f622004-03-25 20:38:40 +00001367
1368<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001369If you're running on a Linux system that supports the "<a
Bill Wendling22e37c32007-07-16 08:46:40 +00001370href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001371module, and you have root access on the system, you can set your system up to
Bill Wendling22e37c32007-07-16 08:46:40 +00001372execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattnera553f622004-03-25 20:38:40 +00001373first command may not be required if you are already using the module):</p>
1374
Misha Brukman9106eca2005-02-03 22:25:23 +00001375<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001376<pre>
Bill Wendling77f74692007-07-16 08:44:39 +00001377$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckye6b5a522009-11-04 06:15:28 +00001378$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendling77f74692007-07-16 08:44:39 +00001379$ chmod u+x hello.bc (if needed)
1380$ ./hello.bc
Chris Lattnera553f622004-03-25 20:38:40 +00001381</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001382</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001383
1384<p>
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001385This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +00001386can also use this command instead of the 'echo' command above:
Chris Lattnera553f622004-03-25 20:38:40 +00001387</p>
1388
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001389<div class="doc_code">
1390<pre>
1391$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1392</pre>
1393</div>
1394
Chris Lattnera553f622004-03-25 20:38:40 +00001395</div>
1396
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001397</div>
1398
Misha Brukman00c73d22003-11-07 19:43:14 +00001399<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001400<h2>
1401 <a name="layout">Program Layout</a>
1402</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001403<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001404
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001405<div>
John Criswell85ed3612003-06-12 19:34:44 +00001406
Misha Brukman00c73d22003-11-07 19:43:14 +00001407<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001408href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001409href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001410The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001411
Misha Brukman00c73d22003-11-07 19:43:14 +00001412<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001413<h3>
1414 <a name="examples"><tt>llvm/examples</tt></a>
1415</h3>
1416
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001417<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001418 <p>This directory contains some simple examples of how to use the LLVM IR and
1419 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001420</div>
John Criswell85ed3612003-06-12 19:34:44 +00001421
Misha Brukman00c73d22003-11-07 19:43:14 +00001422<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001423<h3>
1424 <a name="include"><tt>llvm/include</tt></a>
1425</h3>
1426
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001427<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001428
1429<p>This directory contains public header files exported from the LLVM
1430library. The three main subdirectories of this directory are:</p>
1431
Reid Spencer77d90192004-09-05 20:50:22 +00001432<dl>
1433 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1434 <dd>This directory contains all of the LLVM specific header files. This
1435 directory also has subdirectories for different portions of LLVM:
1436 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1437 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001438
Reid Spencer77d90192004-09-05 20:50:22 +00001439 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1440 <dd>This directory contains generic support libraries that are provided with
1441 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1442 and a Command Line option processing library store their header files here.
1443 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001444
Reid Spencer77d90192004-09-05 20:50:22 +00001445 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1446 <dd>This directory contains header files configured by the <tt>configure</tt>
1447 script. They wrap "standard" UNIX and C header files. Source code can
1448 include these header files which automatically take care of the conditional
1449 #includes that the <tt>configure</tt> script generates.</dd>
1450</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001451</div>
1452
1453<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001454<h3>
1455 <a name="lib"><tt>llvm/lib</tt></a>
1456</h3>
1457
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001458<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001459
1460<p>This directory contains most of the source files of the LLVM system. In LLVM,
1461almost all code exists in libraries, making it very easy to share code among the
1462different <a href="#tools">tools</a>.</p>
1463
Misha Brukman54111c42004-01-20 00:20:17 +00001464<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001465 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1466 <dd> This directory holds the core LLVM source files that implement core
1467 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001468
Reid Spencer77d90192004-09-05 20:50:22 +00001469 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1470 <dd>This directory holds the source code for the LLVM assembly language parser
1471 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001472
Gabor Greif04367bf2007-07-06 22:07:22 +00001473 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1474 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001475
Reid Spencer77d90192004-09-05 20:50:22 +00001476 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001477 different program analyses, such as Dominator Information, Call Graphs,
1478 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001479 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001480
Reid Spencer77d90192004-09-05 20:50:22 +00001481 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1482 <dd> This directory contains the source code for the LLVM to LLVM program
1483 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1484 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1485 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001486
Reid Spencer77d90192004-09-05 20:50:22 +00001487 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1488 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001489 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1490 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001491 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001492
Reid Spencer77d90192004-09-05 20:50:22 +00001493 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1494 <dd> This directory contains the major parts of the code generator: Instruction
1495 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001496
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +00001497 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1498 <dd>(FIXME: T.B.D.)</dd>
1499
1500 <!--FIXME: obsoleted -->
Reid Spencer77d90192004-09-05 20:50:22 +00001501 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1502 <dd> This directory contains the source level debugger library that makes
1503 it possible to instrument LLVM programs so that a debugger could identify
1504 source code locations at which the program is executing.</dd>
1505
1506 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001507 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer77d90192004-09-05 20:50:22 +00001508 at runtime in both interpreted and JIT compiled fashions.</dd>
1509
1510 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar2c607b62011-10-11 20:02:52 +00001511 <dd> This directory contains the source code that corresponds to the header
1512 files located in <tt>llvm/include/ADT/</tt>
1513 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001514</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001515
Misha Brukman00c73d22003-11-07 19:43:14 +00001516</div>
John Criswell85ed3612003-06-12 19:34:44 +00001517
Misha Brukman00c73d22003-11-07 19:43:14 +00001518<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001519<h3>
1520 <a name="projects"><tt>llvm/projects</tt></a>
1521</h3>
1522
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001523<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001524 <p>This directory contains projects that are not strictly part of LLVM but are
1525 shipped with LLVM. This is also the directory where you should create your own
1526 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner4630e4d2008-08-11 06:13:31 +00001527 to set up your own project.</p>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001528</div>
1529
1530<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001531<h3>
1532 <a name="runtime"><tt>llvm/runtime</tt></a>
1533</h3>
1534
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001535<div>
John Criswell85ed3612003-06-12 19:34:44 +00001536
Gabor Greif04367bf2007-07-06 22:07:22 +00001537<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman00c73d22003-11-07 19:43:14 +00001538used when linking programs with the GCC front end. Most of these libraries are
1539skeleton versions of real libraries; for example, libc is a stripped down
1540version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001541
Misha Brukman00c73d22003-11-07 19:43:14 +00001542<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1543end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001544
Misha Brukman00c73d22003-11-07 19:43:14 +00001545</div>
John Criswell85ed3612003-06-12 19:34:44 +00001546
Misha Brukman00c73d22003-11-07 19:43:14 +00001547<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001548<h3>
1549 <a name="test"><tt>llvm/test</tt></a>
1550</h3>
1551
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001552<div>
Reid Spencer77d90192004-09-05 20:50:22 +00001553 <p>This directory contains feature and regression tests and other basic sanity
1554 checks on the LLVM infrastructure. These are intended to run quickly and cover
1555 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001556</div>
John Criswell85ed3612003-06-12 19:34:44 +00001557
Misha Brukman00c73d22003-11-07 19:43:14 +00001558<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001559<h3>
1560 <a name="test-suite"><tt>test-suite</tt></a>
1561</h3>
1562
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001563<div>
John Criswell9c29bfb2007-06-29 19:12:31 +00001564 <p>This is not a directory in the normal llvm module; it is a separate
1565 Subversion
1566 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1567 This
John Criswell3d8ba512004-12-08 17:53:54 +00001568 module contains a comprehensive correctness, performance, and benchmarking
1569 test
John Criswell9c29bfb2007-06-29 19:12:31 +00001570 suite for LLVM. It is a separate Subversion module because not every LLVM
1571 user is
John Criswell838bce52005-05-09 16:39:27 +00001572 interested in downloading or building such a comprehensive test suite. For
1573 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001574 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001575</div>
John Criswell85ed3612003-06-12 19:34:44 +00001576
Reid Spencer77d90192004-09-05 20:50:22 +00001577<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001578<h3>
1579 <a name="tools"><tt>llvm/tools</tt></a>
1580</h3>
1581
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001582<div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001583
Misha Brukman00c73d22003-11-07 19:43:14 +00001584<p>The <b>tools</b> directory contains the executables built out of the
1585libraries above, which form the main part of the user interface. You can
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001586always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001587following is a brief introduction to the most important tools. More detailed
1588information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001589
Misha Brukman54111c42004-01-20 00:20:17 +00001590<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001591
Reid Spencer77d90192004-09-05 20:50:22 +00001592 <dt><tt><b>bugpoint</b></tt></dt>
1593 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001594 optimization passes or code generation backends by narrowing down the
1595 given test case to the minimum number of passes and/or instructions that
1596 still cause a problem, whether it is a crash or miscompilation. See <a
1597 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001598 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001599
Reid Spencer77d90192004-09-05 20:50:22 +00001600 <dt><tt><b>llvm-ar</b></tt></dt>
1601 <dd>The archiver produces an archive containing
Gabor Greif04367bf2007-07-06 22:07:22 +00001602 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001603 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001604
Reid Spencer77d90192004-09-05 20:50:22 +00001605 <dt><tt><b>llvm-as</b></tt></dt>
1606 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001607 bitcode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001608
Reid Spencer77d90192004-09-05 20:50:22 +00001609 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001610 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer77d90192004-09-05 20:50:22 +00001611 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001612
Reid Spencer079e9452004-12-08 18:00:30 +00001613 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001614 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Eric Christopher78d08352011-09-20 00:42:28 +00001615 It performs standard link time optimizations and allows optimization
1616 modules to be loaded and run so that language specific optimizations can
1617 be applied at link time.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001618
Reid Spencer77d90192004-09-05 20:50:22 +00001619 <dt><tt><b>llvm-link</b></tt></dt>
1620 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1621 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001622
Reid Spencer77d90192004-09-05 20:50:22 +00001623 <dt><tt><b>lli</b></tt></dt>
1624 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky64270d52007-12-03 01:58:01 +00001625 can directly execute LLVM bitcode (although very slowly...). For architectures
1626 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1627 will function as a Just-In-Time compiler (if the functionality was compiled
1628 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001629
Reid Spencer77d90192004-09-05 20:50:22 +00001630 <dt><tt><b>llc</b></tt></dt>
1631 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greif04367bf2007-07-06 22:07:22 +00001632 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001633 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001634
Reid Spencerd4694f92004-12-22 06:29:07 +00001635 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001636 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1637 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001638 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencer434262a2007-02-09 15:59:08 +00001639 usual machine code output. It works just like any other GCC compiler,
1640 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1641 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell9c29bfb2007-06-29 19:12:31 +00001642 separate Subversion module.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001643
Reid Spencer77d90192004-09-05 20:50:22 +00001644 <dt><tt><b>opt</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001645 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer84f82f72006-08-28 00:34:19 +00001646 transformations (which are specified on the command line), and then outputs
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001647 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001648 get a list of the program transformations available in LLVM.<br>
Reid Spencer84f82f72006-08-28 00:34:19 +00001649 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greif04367bf2007-07-06 22:07:22 +00001650 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer84f82f72006-08-28 00:34:19 +00001651 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001652</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001653</div>
John Criswell85ed3612003-06-12 19:34:44 +00001654
Misha Brukman00c73d22003-11-07 19:43:14 +00001655<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001656<h3>
1657 <a name="utils"><tt>llvm/utils</tt></a>
1658</h3>
1659
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001660<div>
John Criswell85ed3612003-06-12 19:34:44 +00001661
Misha Brukman00c73d22003-11-07 19:43:14 +00001662<p>This directory contains utilities for working with LLVM source code, and some
1663of the utilities are actually required as part of the build process because they
1664are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001665
Misha Brukman54111c42004-01-20 00:20:17 +00001666<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001667 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001668 that finds differences between code that LLC generates and code that LLI
1669 generates. This is a useful tool if you are debugging one of them,
1670 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001671 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001672
Misha Brukman54111c42004-01-20 00:20:17 +00001673 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001674 syntax-highlighting files which will work with Emacs and XEmacs editors,
1675 providing syntax highlighting support for LLVM assembly files and TableGen
1676 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001677 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001678
Misha Brukman54111c42004-01-20 00:20:17 +00001679 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001680 and outputs all non-generated source files, which is useful if one wishes
1681 to do a lot of development across directories and does not want to
1682 individually find each file. One way to use it is to run, for example:
1683 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001684 tree.<br><br>
1685
Reid Spencer77d90192004-09-05 20:50:22 +00001686 <dt><tt><b>llvmgrep</b></tt></dt>
1687 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1688 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1689 line. This is a very efficient way of searching the source base for a
1690 particular regular expression.</dd>
1691
Misha Brukman54111c42004-01-20 00:20:17 +00001692 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001693 files in the current directory and then compiles and links the tool that
1694 is the first argument. For example, assuming you are in the directory
1695 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1696 simply running <tt>makellvm llc</tt> will make a build of the current
1697 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001698 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001699
Misha Brukman54111c42004-01-20 00:20:17 +00001700 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001701 the tool used to generate register descriptions, instruction set
1702 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001703 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001704
Misha Brukman54111c42004-01-20 00:20:17 +00001705 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001706 syntax-highlighting files which will work with the VIM editor, providing
1707 syntax highlighting support for LLVM assembly files and TableGen
1708 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001709 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001710
Misha Brukman00c73d22003-11-07 19:43:14 +00001711</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001712
Misha Brukman00c73d22003-11-07 19:43:14 +00001713</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001714
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001715</div>
1716
Misha Brukman00c73d22003-11-07 19:43:14 +00001717<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001718<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001719 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001720</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001721<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001722
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001723<div>
Chad Rosier372b8222012-02-26 21:31:25 +00001724<p>This section gives an example of using LLVM with the Clang front end.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001725
1726<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001727<h3>
Chad Rosier372b8222012-02-26 21:31:25 +00001728 <a name="tutorial4">Example with clang</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001729</h3>
Chris Lattner5907d402006-08-14 20:45:25 +00001730
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001731<div>
Chris Lattner5907d402006-08-14 20:45:25 +00001732
1733<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001734 <li><p>First, create a simple C file, name it 'hello.c':</p>
1735
1736<div class="doc_code">
1737<pre>
1738#include &lt;stdio.h&gt;
1739
1740int main() {
1741 printf("hello world\n");
1742 return 0;
1743}
1744</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001745
1746 <li><p>Next, compile the C file into a native executable:</p>
1747
Chad Rosier372b8222012-02-26 21:31:25 +00001748 <div class="doc_code"><pre>% clang hello.c -o hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001749
Chad Rosier372b8222012-02-26 21:31:25 +00001750 <p>Note that clang works just like GCC by default. The standard -S and
Chris Lattner5907d402006-08-14 20:45:25 +00001751 -c arguments work as usual (producing a native .s or .o file,
Bill Wendling77f74692007-07-16 08:44:39 +00001752 respectively).</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001753
Gabor Greif04367bf2007-07-06 22:07:22 +00001754 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendling77f74692007-07-16 08:44:39 +00001755
1756 <div class="doc_code">
Chad Rosier372b8222012-02-26 21:31:25 +00001757 <pre>% clang -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001758
1759 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1760 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1761 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Chad Rosier372b8222012-02-26 21:31:25 +00001762 the bitcode file.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001763
1764 <li><p>Run the program in both forms. To run the program, use:</p>
1765
Bill Wendling77f74692007-07-16 08:44:39 +00001766 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001767
1768 <p>and</p>
1769
Bill Wendling77f74692007-07-16 08:44:39 +00001770 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001771
1772 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001773 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001774
1775 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1776 code:</p>
1777
Bill Wendling77f74692007-07-16 08:44:39 +00001778<div class="doc_code">
1779<pre>llvm-dis &lt; hello.bc | less</pre>
1780</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001781
1782 <li><p>Compile the program to native assembly using the LLC code
1783 generator:</p>
1784
Bill Wendling77f74692007-07-16 08:44:39 +00001785 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001786
1787 <li><p>Assemble the native assembly language file into a program:</p>
1788
Bill Wendling77f74692007-07-16 08:44:39 +00001789<div class="doc_code">
1790<pre>
1791<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1792
1793<b>Others:</b> % gcc hello.s -o hello.native
1794</pre>
1795</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001796
1797 <li><p>Execute the native code program:</p>
1798
Bill Wendling77f74692007-07-16 08:44:39 +00001799 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001800
Chad Rosier372b8222012-02-26 21:31:25 +00001801 <p>Note that using clang to compile directly to native code (i.e. when
Chris Lattner5907d402006-08-14 20:45:25 +00001802 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001803 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001804
1805</ol>
1806
1807</div>
1808
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001809</div>
John Criswell85ed3612003-06-12 19:34:44 +00001810
Misha Brukman00c73d22003-11-07 19:43:14 +00001811<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001812<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001813 <a name="problems">Common Problems</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001814</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001815<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001816
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001817<div>
John Criswellce760f62003-07-03 16:01:38 +00001818
Misha Brukman00c73d22003-11-07 19:43:14 +00001819<p>If you are having problems building or using LLVM, or if you have any other
1820general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1821Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001822
Misha Brukman00c73d22003-11-07 19:43:14 +00001823</div>
John Criswell85ed3612003-06-12 19:34:44 +00001824
Misha Brukman00c73d22003-11-07 19:43:14 +00001825<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001826<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001827 <a name="links">Links</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001828</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001829<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001830
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001831<div>
John Criswell85ed3612003-06-12 19:34:44 +00001832
Bill Wendling2d4c2152008-07-22 01:10:25 +00001833<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman00c73d22003-11-07 19:43:14 +00001834some simple things... there are many more interesting and complicated things
1835that you can do that aren't documented here (but we'll gladly accept a patch
1836if you want to write something up!). For more information about LLVM, check
1837out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001838
Misha Brukman00c73d22003-11-07 19:43:14 +00001839<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001840 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1841 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1842 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001843 that Uses LLVM</a></li>
1844</ul>
1845
1846</div>
1847
1848<!-- *********************************************************************** -->
1849
1850<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001851<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001852 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001853 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001854 <a href="http://validator.w3.org/check/referer"><img
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001855 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001856
Misha Brukman142207b2003-11-22 01:30:01 +00001857 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001858 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001859 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001860 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001861</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001862</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001863</html>