blob: 9bbb1d5c3ab87d7f8aed621b43bb2c4f18a89d2a [file] [log] [blame]
Misha Brukman560e9892003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shib65a78e2002-07-17 23:05:56 +00003<html>
Misha Brukman560e9892003-11-07 19:43:14 +00004<head>
Reid Spencer38fcf302004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman560e9892003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell72989a52003-06-12 19:34:44 +000010
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000011<h1>
Misha Brukman560e9892003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000013</h1>
John Criswell72989a52003-06-12 19:34:44 +000014
Misha Brukman560e9892003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattnerc0bda0d2003-02-14 04:22:13 +000019 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000023 </ol></li>
John Criswell3ef61af2003-06-30 21:59:07 +000024
Misha Brukman560e9892003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell71139f22003-07-08 20:35:59 +000026 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000032 <li><a href="#installcf">Install the GCC Front End</a></li>
33 <li><a href="#config">Local LLVM Configuration</a></li>
34 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
35 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
36 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
37 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000038 </ol></li>
John Criswell71139f22003-07-08 20:35:59 +000039
Misha Brukman560e9892003-11-07 19:43:14 +000040 <li><a href="#layout">Program layout</a>
41 <ol>
Chris Lattner059a8df2007-11-01 04:20:16 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
43 <li><a href="#include"><tt>llvm/include</tt></a></li>
44 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
45 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
46 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
47 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trick68aa18e42010-09-23 20:26:44 +000048 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner059a8df2007-11-01 04:20:16 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
50 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman560e9892003-11-07 19:43:14 +000051 </ol></li>
John Criswellf531f312003-10-27 18:18:16 +000052
Misha Brukman560e9892003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000054 <ol>
Chad Rosier233f1472012-02-26 21:31:25 +000055 <li><a href="#tutorial4">Example with Clang</a></li>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +000056 </ol>
Misha Brukman560e9892003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner020e1fc2004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +000065 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner020e1fc2004-05-23 21:07:27 +000066 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
67 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
68 </p>
69</div>
Misha Brukman560e9892003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +000073<h2>
74 <a name="overview">Overview</a>
75</h2>
Misha Brukman560e9892003-11-07 19:43:14 +000076<!-- *********************************************************************** -->
77
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +000078<div>
Misha Brukman560e9892003-11-07 19:43:14 +000079
80<p>Welcome to LLVM! In order to get started, you first need to know some
81basic information.</p>
82
Andrew Trick68aa18e42010-09-23 20:26:44 +000083<p>First, LLVM comes in three pieces. The first piece is the LLVM
84suite. This contains all of the tools, libraries, and header files
Jim Grosbach65e24652012-01-25 22:00:23 +000085needed to use LLVM. It contains an assembler, disassembler, bitcode
86analyzer and bitcode optimizer. It also contains basic regression tests that
Chad Rosier233f1472012-02-26 21:31:25 +000087can be used to test the LLVM tools and the Clang front end.</p>
Misha Brukman560e9892003-11-07 19:43:14 +000088
Chad Rosier233f1472012-02-26 21:31:25 +000089<p>The second piece is the Clang front end. This component compiles C, C++,
90Objective C, and Objective C++ code into LLVM bitcode. Once compiled into LLVM
91bitcode, a program can be manipulated with the LLVM tools from the LLVM suite.
92</p>
Misha Brukman560e9892003-11-07 19:43:14 +000093
John Criswell6ab273c2004-12-08 17:53:54 +000094<p>
Andrew Trick68aa18e42010-09-23 20:26:44 +000095There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell6ab273c2004-12-08 17:53:54 +000096with a testing harness that can be used to further test LLVM's functionality
97and performance.
98</p>
99
Misha Brukman560e9892003-11-07 19:43:14 +0000100</div>
101
102<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000103<h2>
104 <a name="quickstart">Getting Started Quickly (A Summary)</a>
105</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000106<!-- *********************************************************************** -->
107
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000108<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000109
Chad Rosier6e220d52012-02-23 21:23:24 +0000110<p>The LLVM Getting Started documentation is <b>wildly</b> out of date and is
Chad Rosier563f6202012-02-23 23:21:22 +0000111in dire need of an update. Most notably, Clang has replaced the GCC front end
Chad Rosier6e220d52012-02-23 21:23:24 +0000112entirely and building with the LLVM GCC front end is no longer supported.
113The Clang <a href="http://clang.llvm.org/get_started.html">Getting Started</a>
114page might be a better place to start.</p>
115
Misha Brukman560e9892003-11-07 19:43:14 +0000116<p>Here's the short story for getting up and running quickly with LLVM:</p>
117
118<ol>
Reid Spencer3fbf26a2004-11-08 00:29:22 +0000119 <li>Read the documentation.</li>
120 <li>Read the documentation.</li>
121 <li>Remember that you were warned twice about reading the documentation.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000122 <li>Install the llvm-gcc-4.2 front end if you intend to compile C or C++
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000123 (see <a href="#installcf">Install the GCC Front End</a> for details):
Misha Brukman560e9892003-11-07 19:43:14 +0000124 <ol>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000125 <li><tt>cd <i>where-you-want-the-C-front-end-to-live</i></tt></li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000126 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf -</tt></li>
127 <li><tt><i>install-binutils-binary-from-MinGW</i></tt> (Windows only)</li>
128 <li>Note: If the binary extension is "<tt>.bz</tt>" use <tt>bunzip2</tt> instead of <tt>gunzip</tt>.</li>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000129 <li>Note: On Windows, use <a href="http://www.7-zip.org/">7-Zip</a> or a similar archiving tool.</li>
Jim Grosbach67584fe2009-12-17 17:18:11 +0000130 <li>Add <tt>llvm-gcc</tt>'s "<tt>bin</tt>" directory to your <tt>PATH</tt> environment variable.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000131 </ol></li>
132
Misha Brukman20b8a6562005-02-03 22:25:23 +0000133 <li>Get the LLVM Source Code
Misha Brukman560e9892003-11-07 19:43:14 +0000134 <ul>
John Criswell58594852007-06-29 19:12:31 +0000135 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
Misha Brukman560e9892003-11-07 19:43:14 +0000136 <ol>
137 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
John Criswell64f13ab2004-03-12 20:31:37 +0000138 <li><tt>gunzip --stdout llvm-<i>version</i>.tar.gz | tar -xvf -</tt>
Misha Brukman560e9892003-11-07 19:43:14 +0000139 </ol></li>
140
Misha Brukman560e9892003-11-07 19:43:14 +0000141 </ul></li>
142
Misha Brukman20b8a6562005-02-03 22:25:23 +0000143 <li><b>[Optional]</b> Get the Test Suite Source Code
John Criswelldfe6a862004-12-10 15:51:16 +0000144 <ul>
John Criswell58594852007-06-29 19:12:31 +0000145 <li>With the distributed files (or use <a href="#checkout">SVN</a>):
John Criswelldfe6a862004-12-10 15:51:16 +0000146 <ol>
147 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
148 <li><tt>cd llvm/projects</tt>
149 <li><tt>gunzip --stdout llvm-test-<i>version</i>.tar.gz | tar -xvf -</tt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000150 <li><tt>mv llvm-test-<i>version</i> test-suite</tt>
John Criswelldfe6a862004-12-10 15:51:16 +0000151 </ol></li>
152
John Criswelldfe6a862004-12-10 15:51:16 +0000153 </ul></li>
154
155
Misha Brukman560e9892003-11-07 19:43:14 +0000156 <li>Configure the LLVM Build Environment
157 <ol>
Misha Brukman20b8a6562005-02-03 22:25:23 +0000158 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
159 <li><tt><i>/path/to/llvm/</i>configure [options]</tt><br>
160 Some common options:
161
Misha Brukman560e9892003-11-07 19:43:14 +0000162 <ul>
Reid Spencer788b0fd2004-12-22 06:29:07 +0000163 <li><tt>--prefix=<i>directory</i></tt>
164 <p>Specify for <i>directory</i> the full pathname of where you
Misha Brukman20b8a6562005-02-03 22:25:23 +0000165 want the LLVM tools and libraries to be installed (default
166 <tt>/usr/local</tt>).</p></li>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000167 <li><tt>--with-llvmgccdir=<i>directory</i></tt>
168 <p>Optionally, specify for <i>directory</i> the full pathname of the
John Criswellcfdeb5c2005-05-09 16:39:27 +0000169 C/C++ front end installation to use with this LLVM configuration. If
Duncan Sands10961cd2009-04-18 12:40:19 +0000170 not specified, the PATH will be searched. This is only needed if you
Andrew Trick68aa18e42010-09-23 20:26:44 +0000171 want to run test-suite or do some special kinds of LLVM builds.</p></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000172 <li><tt>--enable-spec2000=<i>directory</i></tt>
173 <p>Enable the SPEC2000 benchmarks for testing. The SPEC2000
174 benchmarks should be available in
175 <tt><i>directory</i></tt>.</p></li>
176 </ul>
177 </ol></li>
178
179 <li>Build the LLVM Suite:
180 <ol>
Chris Lattnere0050f02004-07-18 22:32:22 +0000181 <li><tt>gmake -k |&amp; tee gnumake.out
182 &nbsp;&nbsp;&nbsp;# this is csh or tcsh syntax</tt></li>
Chris Lattner13ce9182007-01-04 07:06:05 +0000183 <li>If you get an "internal compiler error (ICE)" or test failures, see
184 <a href="#brokengcc">below</a>.</li>
Misha Brukman560e9892003-11-07 19:43:14 +0000185 </ol>
186
187</ol>
188
Chris Lattner53e5e2a2004-06-21 22:52:48 +0000189<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman560e9892003-11-07 19:43:14 +0000190detailed information on configuring and compiling LLVM. See <a
191href="#environment">Setting Up Your Environment</a> for tips that simplify
192working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
193Layout</a> to learn about the layout of the source code tree.</p>
194
195</div>
196
197<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000198<h2>
199 <a name="requirements">Requirements</a>
200</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000201<!-- *********************************************************************** -->
202
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000203<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000204
205<p>Before you begin to use the LLVM system, review the requirements given below.
206This may save you some trouble by knowing ahead of time what hardware and
207software you will need.</p>
208
Misha Brukman560e9892003-11-07 19:43:14 +0000209<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000210<h3>
211 <a name="hardware">Hardware</a>
212</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000213
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000214<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000215
216<p>LLVM is known to work on the following platforms:</p>
217
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000218<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukmanb0681672004-11-15 05:19:53 +0000219<tr>
220 <th>OS</th>
221 <th>Arch</th>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000222 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000223</tr>
224<tr>
Chris Lattner6bad1372009-07-22 04:21:40 +0000225 <td>AuroraUX</td>
226 <td>x86<sup><a href="#pf_1">1</a></sup></td>
227 <td>GCC</td>
Chris Lattner3a56ae82009-07-21 22:47:03 +0000228</tr>
229<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000230 <td>Linux</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000231 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000232 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000233</tr>
234<tr>
Edward O'Callaghanab8a04c2009-08-04 05:24:28 +0000235 <td>Linux</td>
236 <td>amd64</td>
237 <td>GCC</td>
238</tr>
239<tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000240 <td>Solaris</td>
241 <td>V9 (Ultrasparc)</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000242 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000243</tr>
244<tr>
245 <td>FreeBSD</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000246 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000247 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000248</tr>
249<tr>
Bill Wendling5d32b702010-12-15 01:35:55 +0000250 <td>FreeBSD</td>
251 <td>amd64</td>
252 <td>GCC</td>
253</tr>
254<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000255 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000256 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000257 <td>GCC</td>
Misha Brukmanb0681672004-11-15 05:19:53 +0000258</tr>
259<tr>
Scott Michel4799ea72008-03-18 23:13:26 +0000260 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000261 <td>x86</td>
262 <td>GCC</td>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000263</tr>
264<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000265 <td>Cygwin/Win32</td>
Anton Korobeynikovd0a0bc32009-12-09 17:26:02 +0000266 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
267 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000268 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000269</tr>
Misha Brukman5ac308f2004-12-23 07:14:56 +0000270<tr>
Chris Lattner093ffb02005-02-09 20:43:48 +0000271 <td>MinGW/Win32</td>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000272 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000273 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
274 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000275 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner093ffb02005-02-09 20:43:48 +0000276</tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000277</table>
278
279<p>LLVM has partial support for the following platforms:</p>
280
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000281<table summary="LLVM partial platform support">
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000282<tr>
283 <th>OS</th>
284 <th>Arch</th>
285 <th>Compilers</th>
Misha Brukmanb0681672004-11-15 05:19:53 +0000286</tr>
Misha Brukmandca72382004-11-15 21:05:08 +0000287<tr>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000288 <td>Windows</td>
Chris Lattnerac648f52005-02-09 21:15:51 +0000289 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruthd1eafe12011-11-16 19:52:13 +0000290 <td>Visual Studio 2008 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000291<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000292 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukmandca72382004-11-15 21:05:08 +0000293 <td>PowerPC</td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000294 <td>GCC</td>
295</tr>
296<tr>
Chris Lattnerac648f52005-02-09 21:15:51 +0000297 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000298 <td>PowerPC</td>
299 <td>GCC</td>
Misha Brukmandca72382004-11-15 21:05:08 +0000300</tr>
John Criswell05990f32005-05-09 16:49:59 +0000301
302<tr>
303 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
304 <td>Alpha</td>
305 <td>GCC</td>
306</tr>
307<tr>
308 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
309 <td>Itanium (IA-64)</td>
310 <td>GCC</td>
311</tr>
Duraid Madina332b16a2005-05-10 06:57:53 +0000312<tr>
313 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
314 <td>Itanium (IA-64)</td>
315 <td>HP aCC</td>
316</tr>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000317<tr>
318 <td>Windows x64</td>
319 <td>x86-64</td>
320 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
321</tr>
Misha Brukmanb0681672004-11-15 05:19:53 +0000322</table>
Misha Brukman560e9892003-11-07 19:43:14 +0000323
Misha Brukman77723092005-02-09 21:01:26 +0000324<p><b>Notes:</b></p>
325
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000326<div class="doc_notes">
327<ol>
328<li><a name="pf_1">Code generation supported for Pentium processors and
329up</a></li>
330<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
331<li><a name="pf_3">No native code generation</a></li>
Nick Lewyckyd745ade2008-12-08 00:45:02 +0000332<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000333<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattnerb7481cf2009-01-02 07:10:51 +0000334<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell05990f32005-05-09 16:49:59 +0000335<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov9e8baa52010-02-11 21:51:51 +0000336<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
337 generated by LLVM properly.</a></li>
Chris Lattner26c74442008-11-09 17:19:14 +0000338<li><a name="pf_9">XCode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel4799ea72008-03-18 23:13:26 +0000339 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner26c74442008-11-09 17:19:14 +0000340 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
341 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel4799ea72008-03-18 23:13:26 +0000342 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikovd4f00612009-08-06 12:54:58 +0000343<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
344 version of the perl package, and be sure it appears in your path
345 before any Windows-based versions such as Strawberry Perl and
346 ActivePerl, as these have Windows-specifics that will cause the
347 build to fail.</a></li>
NAKAMURA Takumi05c00022011-03-28 06:27:06 +0000348<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000349 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi10b96cb2011-03-28 06:27:12 +0000350<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000351 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukman77723092005-02-09 21:01:26 +0000352</ol>
Misha Brukman77723092005-02-09 21:01:26 +0000353</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000354
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000355<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswelle1a81202005-05-18 19:43:33 +0000356mode, depending on the system (it is so large because of all the debugging
357information and the fact that the libraries are statically linked into multiple
Chris Lattner0cb89772009-04-25 22:08:52 +0000358tools). If you do not need many of the tools and you are space-conscious, you
359can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
360requires considerably less space.</p>
Misha Brukman1ed0fa52004-11-19 21:53:22 +0000361
Misha Brukman560e9892003-11-07 19:43:14 +0000362<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
363guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greifa54634a2007-07-06 22:07:22 +0000364able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman560e9892003-11-07 19:43:14 +0000365generation should work as well, although the generated native code may not work
366on your platform.</p>
367
368<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman876d5f12004-08-09 19:57:01 +0000369to work on another platform, you can download a copy of the source and <a
Duncan Sands551d3e62008-02-14 17:53:22 +0000370href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000371
372</div>
373
374<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000375<h3>
376 <a name="software">Software</a>
377</h3>
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000378<div>
Reid Spencer38fcf302004-11-15 21:15:12 +0000379 <p>Compiling LLVM requires that you have several software packages
380 installed. The table below lists those required packages. The Package column
381 is the usual name for the software package that LLVM depends on. The Version
382 column provides "known to work" versions of the package. The Notes column
383 describes how LLVM uses the package and provides other details.</p>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000384 <table summary="Packages required to compile LLVM">
Reid Spencer38fcf302004-11-15 21:15:12 +0000385 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000386
Reid Spencer38fcf302004-11-15 21:15:12 +0000387 <tr>
388 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
389 <td>3.79, 3.79.1</td>
390 <td>Makefile/build processor</td>
391 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000392
Reid Spencer38fcf302004-11-15 21:15:12 +0000393 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000394 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000395 <td>3.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000396 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000397 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000398
Reid Spencer38fcf302004-11-15 21:15:12 +0000399 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000400 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattnerf1705fd2005-09-06 04:07:15 +0000401 <td>4.5</td>
402 <td>For building the CFE</td>
403 </tr>
404
405 <tr>
John Criswell58594852007-06-29 19:12:31 +0000406 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
407 <td>&ge;1.3</td>
408 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000409 </tr>
410
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +0000411 <!-- FIXME:
412 Do we support dg?
413 Are DejaGnu and expect obsolete?
414 Shall we mention Python? -->
415
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000416 <tr>
Reid Spencer38fcf302004-11-15 21:15:12 +0000417 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
418 <td>1.4.2</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000419 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000420 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000421
Reid Spencer38fcf302004-11-15 21:15:12 +0000422 <tr>
423 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
424 <td>8.3, 8.4</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000425 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000426 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +0000427
Reid Spencer38fcf302004-11-15 21:15:12 +0000428 <tr>
429 <td><a href="http://expect.nist.gov/">expect</a></td>
430 <td>5.38.0</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000431 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000432 </tr>
433
434 <tr>
435 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer098fce42004-12-09 17:55:37 +0000436 <td>&ge;5.6.0</td>
Daniel Dunbar06b68122012-02-15 19:24:11 +0000437 <td>Utilities</td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000438 </tr>
439
440 <tr>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000441 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
442 <td>1.4</td>
443 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000444 </tr>
445
446 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000447 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000448 <td>2.60</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000449 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
450 </tr>
451
452 <tr>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000453 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000454 <td>1.9.6</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000455 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
456 </tr>
457
458 <tr>
459 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewyckyf32f6982009-09-27 04:56:27 +0000460 <td>1.5.22</td>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000461 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer38fcf302004-11-15 21:15:12 +0000462 </tr>
463
464 </table>
465
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000466 <p><b>Notes:</b></p>
467 <div class="doc_notes">
Reid Spencer38fcf302004-11-15 21:15:12 +0000468 <ol>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000469 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000470 need to build the other languages for LLVM's purposes.</a> See
471 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell58594852007-06-29 19:12:31 +0000472 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000473 latest LLVM sources. If you're working from a release distribution, you
John Criswell58594852007-06-29 19:12:31 +0000474 don't need Subversion.</a></li>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000475 <li><a name="sf3">Only needed if you want to run the automated test
476 suite in the <tt>llvm/test</tt> directory.</a></li>
477 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser4518c862010-05-19 07:00:17 +0000478 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
479 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer098fce42004-12-09 17:55:37 +0000480 from that package.</a></li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000481 </ol>
Misha Brukman0c4b8b62005-02-09 22:38:47 +0000482 </div>
483
Reid Spencer38fcf302004-11-15 21:15:12 +0000484 <p>Additionally, your compilation host is expected to have the usual
485 plethora of Unix utilities. Specifically:</p>
486 <ul>
487 <li><b>ar</b> - archive library builder</li>
488 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
489 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
490 <li><b>chmod</b> - change permissions on a file</li>
John Criswell33e0f062004-12-08 16:55:27 +0000491 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000492 <li><b>cp</b> - copy files</li>
493 <li><b>date</b> - print the current date/time </li>
494 <li><b>echo</b> - print to standard output</li>
495 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000496 <li><b>find</b> - find files/dirs in a file system</li>
497 <li><b>grep</b> - regular expression search utility</li>
498 <li><b>gzip*</b> - gzip command for distribution generation</li>
499 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
500 <li><b>install</b> - install directories/files </li>
501 <li><b>mkdir</b> - create a directory</li>
502 <li><b>mv</b> - move (rename) files</li>
503 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman29d3d462004-11-20 01:27:40 +0000504 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer38fcf302004-11-15 21:15:12 +0000505 <li><b>sed</b> - stream editor for transforming output</li>
506 <li><b>sh</b> - Bourne shell for make build scripts</li>
507 <li><b>tar</b> - tape archive for distribution generation</li>
508 <li><b>test</b> - test things in file system</li>
509 <li><b>unzip*</b> - unzip command for distribution checking</li>
510 <li><b>zip*</b> - zip command for distribution generation</li>
511 </ul>
Chris Lattnere0050f02004-07-18 22:32:22 +0000512</div>
Misha Brukman560e9892003-11-07 19:43:14 +0000513
Chris Lattnere0050f02004-07-18 22:32:22 +0000514<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000515<h3>
Chris Lattner55514822007-06-19 05:52:36 +0000516 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000517</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000518
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000519<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000520
521<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
522bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenekaff36402011-10-31 21:23:15 +0000523to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
524Other versions of GCC will probably work as well. GCC versions listed
Chris Lattnere0050f02004-07-18 22:32:22 +0000525here are known to not work. If you are using one of these versions, please try
526to upgrade your GCC to something more recent. If you run into a problem with a
527version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
528us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
529of GCC you are using.
530</p>
531
532<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
533problems in the STL that effectively prevent it from compiling LLVM.
534</p>
535
Chris Lattner419df4e2008-02-13 17:50:24 +0000536<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
537a bogus template error. This was fixed in later GCCs.</p>
John Criswellfd769452004-11-23 22:06:24 +0000538
Chris Lattnere0050f02004-07-18 22:32:22 +0000539<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
540href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
541the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattnere254e2f2005-02-12 20:11:13 +0000542
Chris Lattner58247622005-02-13 22:20:49 +0000543<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands551d3e62008-02-14 17:53:22 +0000544 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner58247622005-02-13 22:20:49 +0000545 to a newer version</a> if possible.</p>
546<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
547 possibly others) does not compile LLVM correctly (it appears that exception
548 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
549 to a newer version of GCC.</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000550<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000551 code generator, causing an infinite loop in the llvm-gcc build when built
552 with optimizations enabled (i.e. a release build).</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000553<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner3d82dcf2007-05-10 06:42:21 +0000554 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
555 correctly compiles LLVM at -O2. A work around is to build release LLVM
556 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendlinga5d30d52007-07-16 08:52:56 +0000557<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner489ad332007-04-01 20:14:46 +0000558 miscompiles portions of LLVM</a>.</p>
Chris Lattner059a8df2007-11-01 04:20:16 +0000559<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
560 when building with optimizations enabled. It appears to work with
561 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
562 build.</p>
Chris Lattner7caf6f62005-05-15 22:26:45 +0000563<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
564 miscompile LLVM.</p>
Chris Lattnerc9ede192006-06-16 19:53:39 +0000565<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
566 default with ENABLE_OPTIMIZED=1. To work around this, build with
567 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattneraa64b942006-09-07 17:34:27 +0000568<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
569 compiling some files. At the time of this writing, GCC mainline (4.2)
570 did not share the problem.</p>
Chris Lattner13ce9182007-01-04 07:06:05 +0000571<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
572 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
573 code. LLVM will appear to mostly work but will be buggy, e.g. failing
574 portions of its testsuite.</p>
Reid Spencera28d6622007-04-11 21:28:31 +0000575<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
576platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbar2a575452008-10-11 18:40:33 +0000577<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
578to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
579about symbols remaining in the table on destruction.</p>
Nuno Lopes94993852008-12-10 16:11:10 +0000580<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes65e877e2008-12-10 16:01:22 +0000581as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Anton Korobeynikovdad58712009-05-04 10:24:46 +0000582<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
583 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
584 with link errors when using this GCC version.</p>
Chris Lattnereba6c722009-09-10 16:25:02 +0000585<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewyckyd562ab12009-07-17 06:32:10 +0000586<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
587when optimizations are turned on. The symptom is an infinite loop in
Chris Lattnereba6c722009-09-10 16:25:02 +0000588FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewyckyabe8c132010-10-07 22:30:47 +0000589<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
5901</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
591one symptom of the problem.
Reid Spencer6291ddc2006-11-04 00:33:42 +0000592<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
593long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
594defined in a discarded section. You can safely ignore these messages as they are
595erroneous and the linkage is correct. These messages disappear using ld
5962.17.</p>
Chris Lattner55514822007-06-19 05:52:36 +0000597
598<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
599href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
600causes huge link times (minutes instead of seconds) when building LLVM. We
601recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
602
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000603<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewycky2db07612009-02-25 06:29:47 +0000604<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
605which causes intermittent failures when building LLVM with position independent
Nick Lewycky79a6fe92009-03-03 05:41:16 +0000606code. The symptom is an error about cyclic dependencies. We recommend
607upgrading to a newer version of Gold.</p>
Nick Lewycky2db07612009-02-25 06:29:47 +0000608
Misha Brukman560e9892003-11-07 19:43:14 +0000609</div>
610
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000611</div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000612
Misha Brukman560e9892003-11-07 19:43:14 +0000613<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000614<h2>
615 <a name="starting">Getting Started with LLVM</a>
616</h2>
Misha Brukman560e9892003-11-07 19:43:14 +0000617<!-- *********************************************************************** -->
618
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000619<div>
Chris Lattnere0050f02004-07-18 22:32:22 +0000620
621<p>The remainder of this guide is meant to get you up and running with
622LLVM and to give you some basic information about the LLVM environment.</p>
623
624<p>The later sections of this guide describe the <a
625href="#layout">general layout</a> of the the LLVM source tree, a <a
626href="#tutorial">simple example</a> using the LLVM tool chain, and <a
627href="#links">links</a> to find more information about LLVM or to get
628help via e-mail.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +0000629
Misha Brukman560e9892003-11-07 19:43:14 +0000630<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000631<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000632 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000633</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000634
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000635<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000636
637<p>Throughout this manual, the following names are used to denote paths
638specific to the local system and working environment. <i>These are not
639environment variables you need to set but just strings used in the rest
640of this document below</i>. In any of the examples below, simply replace
641each of these names with the appropriate pathname on your local system.
642All these paths are absolute:</p>
643
Misha Brukmand3de5c62004-01-20 00:20:17 +0000644<dl>
Misha Brukman560e9892003-11-07 19:43:14 +0000645 <dt>SRC_ROOT
646 <dd>
647 This is the top level directory of the LLVM source tree.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000648 <br><br>
John Criswellf531f312003-10-27 18:18:16 +0000649
Misha Brukman560e9892003-11-07 19:43:14 +0000650 <dt>OBJ_ROOT
651 <dd>
652 This is the top level directory of the LLVM object tree (i.e. the
653 tree where object files and compiled programs will be placed. It
654 can be the same as SRC_ROOT).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +0000655 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +0000656
657 <dt>LLVMGCCDIR
658 <dd>
Reid Spencer6bfa7a42004-12-26 05:47:26 +0000659 This is where the LLVM GCC Front End is installed.
Misha Brukman560e9892003-11-07 19:43:14 +0000660 <p>
661 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000662 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman560e9892003-11-07 19:43:14 +0000663</dl>
664
665</div>
666
667<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000668<h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000669 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000670</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000671
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000672<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000673
674<p>
Misha Brukmancd673252005-02-03 18:28:08 +0000675In order to compile and use LLVM, you may need to set some environment
676variables.
Misha Brukman560e9892003-11-07 19:43:14 +0000677
Misha Brukmand3de5c62004-01-20 00:20:17 +0000678<dl>
Gabor Greifa54634a2007-07-06 22:07:22 +0000679 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukmancd673252005-02-03 18:28:08 +0000680 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greifa54634a2007-07-06 22:07:22 +0000681 locations of your bitcode libraries. It is provided only as a
Misha Brukmancd673252005-02-03 18:28:08 +0000682 convenience since you can specify the paths using the -L options of the
Gabor Greifa54634a2007-07-06 22:07:22 +0000683 tools and the C/C++ front-end will automatically use the bitcode files
John Criswelle1a81202005-05-18 19:43:33 +0000684 installed in its
Misha Brukmancd673252005-02-03 18:28:08 +0000685 <tt>lib</tt> directory.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000686</dl>
687
688</div>
689
690<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000691<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000692 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000693</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000694
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000695<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000696
697<p>
698If you have the LLVM distribution, you will need to unpack it before you
John Criswell86a3a482003-12-18 16:43:17 +0000699can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswelldfe6a862004-12-10 15:51:16 +0000700suite and the LLVM GCC front end compiled for your platform. There is an
701additional test suite that is optional. Each file is a TAR archive that is
702compressed with the gzip program.
Misha Brukman560e9892003-11-07 19:43:14 +0000703</p>
704
Misha Brukmand4528ea2005-02-02 18:01:57 +0000705<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukmand3de5c62004-01-20 00:20:17 +0000706<dl>
Misha Brukmand4528ea2005-02-02 18:01:57 +0000707 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukman21a63702008-12-11 18:23:24 +0000708 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +0000709
Misha Brukmand4528ea2005-02-02 18:01:57 +0000710 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trick68aa18e42010-09-23 20:26:44 +0000711 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukmanc3184442004-11-23 19:26:24 +0000712
Misha Brukman4050d152008-12-29 19:38:58 +0000713 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
714 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukman21a63702008-12-11 18:23:24 +0000715 directory for build instructions.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000716
Misha Brukman4050d152008-12-29 19:38:58 +0000717 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
718 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner499abb52006-04-20 05:08:23 +0000719
Misha Brukman560e9892003-11-07 19:43:14 +0000720</dl>
721
722</div>
723
724<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000725<h3>
John Criswell58594852007-06-29 19:12:31 +0000726 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000727</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000728
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000729<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000730
John Criswell58594852007-06-29 19:12:31 +0000731<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattner1c1595f2009-04-25 22:24:49 +0000732the entire source code. All you need to do is check it out from Subversion as
Misha Brukman560e9892003-11-07 19:43:14 +0000733follows:</p>
734
735<ul>
John Criswell58594852007-06-29 19:12:31 +0000736 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov4c04a93332007-06-29 20:56:49 +0000737 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
738 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell58594852007-06-29 19:12:31 +0000739 llvm</tt></li>
Misha Brukman560e9892003-11-07 19:43:14 +0000740</ul>
741
John Criswell58594852007-06-29 19:12:31 +0000742
Misha Brukman560e9892003-11-07 19:43:14 +0000743<p>This will create an '<tt>llvm</tt>' directory in the current
744directory and fully populate it with the LLVM source code, Makefiles,
745test directories, and local copies of documentation files.</p>
746
Misha Brukmand3de5c62004-01-20 00:20:17 +0000747<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikoveaa836b2007-06-29 23:13:42 +0000748revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikov09ca62d2007-06-30 00:00:57 +0000749'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman52757bf2008-12-17 16:27:23 +0000750subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000751
John Criswell86a3a482003-12-18 16:43:17 +0000752<ul>
Bill Wendlingdb624242011-04-04 23:42:51 +0000753<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc4735872010-10-06 23:50:30 +0000754<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner3d7ec7b2010-10-06 05:36:01 +0000755<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattner9d3ba88b2009-10-23 06:20:06 +0000756<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattner1c1595f2009-04-25 22:24:49 +0000757<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman52757bf2008-12-17 16:27:23 +0000758<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattner610e89d2008-06-09 06:02:09 +0000759<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattner779593c2008-02-12 02:42:55 +0000760<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner586eb8e2007-09-28 22:50:54 +0000761<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattnere94a09e2007-05-22 06:06:22 +0000762<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner84252ca2006-11-20 06:07:10 +0000763<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerda2d1e22006-11-20 06:04:46 +0000764<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattnerfb762912006-04-20 04:35:34 +0000765<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswell3bdbd302005-11-08 21:11:33 +0000766<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell05990f32005-05-09 16:49:59 +0000767<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000768<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell1e87b972004-08-16 14:51:33 +0000769<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanc1aac032004-05-12 19:25:59 +0000770<li>Release 1.2: <b>RELEASE_12</b></li>
771<li>Release 1.1: <b>RELEASE_11</b></li>
772<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswell86a3a482003-12-18 16:43:17 +0000773</ul>
John Criswell86a3a482003-12-18 16:43:17 +0000774
Reid Spencerdfcf7902004-12-08 16:51:31 +0000775<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell58594852007-06-29 19:12:31 +0000776you get it from the Subversion repository:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000777
778<div class="doc_code">
Reid Spencerdfcf7902004-12-08 16:51:31 +0000779<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000780% cd llvm/projects
Andrew Trick68aa18e42010-09-23 20:26:44 +0000781% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencerdfcf7902004-12-08 16:51:31 +0000782</pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +0000783</div>
784
Reid Spencerdfcf7902004-12-08 16:51:31 +0000785<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswell33e0f062004-12-08 16:55:27 +0000786configured by the LLVM configure script as well as automatically updated when
John Criswell58594852007-06-29 19:12:31 +0000787you run <tt>svn update</tt>.</p>
Reid Spencerdfcf7902004-12-08 16:51:31 +0000788
Chris Lattner40872ad2007-03-06 06:27:34 +0000789<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands551d3e62008-02-14 17:53:22 +0000790and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner40872ad2007-03-06 06:27:34 +0000791instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner3337c822004-06-28 17:14:01 +0000792
Misha Brukman560e9892003-11-07 19:43:14 +0000793</div>
794
795<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000796<h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000797 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000798</h3>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000799
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000800<div>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000801
802<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
803 sync automatically with each Subversion commit and contain all necessary
804 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
805 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +0000806 read-only GIT clone of LLVM via:</p>
807
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000808<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000809git clone http://llvm.org/git/llvm.git
810</pre>
811
812<p>If you want to check out clang too, run:</p>
813
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000814<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000815git clone http://llvm.org/git/llvm.git
816cd llvm/tools
817git clone http://llvm.org/git/clang.git
818</pre>
819
NAKAMURA Takumid92a5fe2011-08-12 07:48:01 +0000820<p>
821Since the upstream repository is in Subversion, you should use
822<tt>&quot;git pull --rebase&quot;</tt>
823instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
824history in your clone.
825To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
826on the master branch, run the following command:
827</p>
828
829<pre class="doc_code">
830git config branch.master.rebase true
831</pre>
832
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000833<h4>Sending patches with Git</h4>
834<div>
835<p>
836Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
837</p>
838
839<p>
840Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
841working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
842At first you may check sanity of whitespaces:
843</p>
844
845<pre class="doc_code">
846git diff --check master..mybranch
847</pre>
848
849<p>
850The easiest way to generate a patch is as below:
851</p>
852
853<pre class="doc_code">
854git diff master..mybranch &gt; /path/to/mybranch.diff
855</pre>
856
857<p>
858It is a little different from svn-generated diff. git-diff-generated diff has
859prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
860know it could be accepted with <tt>patch -p1 -N</tt>.
861</p>
862
863<p>
864But you may generate patchset with git-format-patch. It generates
865by-each-commit patchset. To generate patch files to attach to your article:
866</p>
867
868<pre class="doc_code">
869git format-patch --no-attach master..mybranch -o /path/to/your/patchset
870</pre>
871
872<p>
873If you would like to send patches directly, you may use git-send-email or
874git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
875</p>
876
877<pre class="doc_code">
878git format-patch --attach master..mybranch --stdout | git imap-send
879</pre>
880
881<p>
882Then, your .git/config should have [imap] sections.
883</p>
884
885<pre class="doc_code">
886[imap]
887 host = imaps://imap.gmail.com
888 user = <em>your.gmail.account</em>@gmail.com
889 pass = <em>himitsu!</em>
890 port = 993
891 sslverify = false
892; in English
893 folder = "[Gmail]/Drafts"
894; example for Japanese, "Modified UTF-7" encoded.
895 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumia61f0cc2011-11-06 06:51:58 +0000896; example for Traditional Chinese
897 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi5dd41322011-08-12 07:48:06 +0000898</pre>
899
900</div>
901
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000902<h4>For developers to work with git-svn</h4>
903<div>
904
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000905<p>To set up clone from which you can submit code using
906 <tt>git-svn</tt>, run:</p>
907
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000908<pre class="doc_code">
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000909git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000910cd llvm
911git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
912git config svn-remote.svn.fetch :refs/remotes/origin/master
913git svn rebase -l # -l avoids fetching ahead of the git mirror.
914
915# If you have clang too:
916cd tools
NAKAMURA Takumi5d2a7322011-07-20 22:58:28 +0000917git clone http://llvm.org/git/clang.git
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000918cd clang
919git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
920git config svn-remote.svn.fetch :refs/remotes/origin/master
921git svn rebase -l
922</pre>
923
924<p>To update this clone without generating git-svn tags that conflict
925with the upstream git repo, run:</p>
926
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000927<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000928git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
929git checkout master
930git svn rebase -l
931(cd tools/clang &&
932 git checkout master &&
933 git svn rebase -l)
934</pre>
935
936<p>This leaves your working directories on their master branches, so
937you'll need to <tt>checkout</tt> each working branch individually and
938<tt>rebase</tt> it on top of its parent branch. (Note: This script is
939intended for relative newbies to git. If you have more experience,
940you can likely improve on it.)</p>
941
942<p>The git-svn metadata can get out of sync after you mess around with
943branches and <code>dcommit</code>. When that happens, <code>git svn
944dcommit</code> stops working, complaining about files with uncommitted
945changes. The fix is to rebuild the metadata:</p>
946
NAKAMURA Takumi72c4af52011-07-20 23:37:51 +0000947<pre class="doc_code">
Jeffrey Yasskin532114e2011-07-19 00:20:54 +0000948rm -rf .git/svn
949git svn rebase -l
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000950</pre>
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000951
952</div>
953
NAKAMURA Takumid9b1c6e2011-08-12 07:47:55 +0000954</div>
955
Anton Korobeynikov3e956af2011-02-01 20:08:28 +0000956<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000957<h3>
Misha Brukmand3de5c62004-01-20 00:20:17 +0000958 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +0000959</h3>
Misha Brukman560e9892003-11-07 19:43:14 +0000960
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +0000961<div>
Misha Brukman560e9892003-11-07 19:43:14 +0000962
Jim Grosbach67584fe2009-12-17 17:18:11 +0000963<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
964GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trick68aa18e42010-09-23 20:26:44 +0000965It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach67584fe2009-12-17 17:18:11 +0000966you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattner24b71352007-02-14 07:33:00 +0000967main LLVM repository.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000968
Jim Grosbach67584fe2009-12-17 17:18:11 +0000969<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +0000970like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000971
972<ol>
973 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukman4050d152008-12-29 19:38:58 +0000974 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman560e9892003-11-07 19:43:14 +0000975 -</tt></li>
976</ol>
977
Jim Grosbach67584fe2009-12-17 17:18:11 +0000978<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
979<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
980Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
981to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
982<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
983
984<p>If you now want to build LLVM from source, when you configure LLVM, it will
985automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trick68aa18e42010-09-23 20:26:44 +0000986use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach67584fe2009-12-17 17:18:11 +0000987point after building the main LLVM repository: just reconfigure llvm and
Andrew Trick68aa18e42010-09-23 20:26:44 +0000988test-suite will pick it up.
Chris Lattner24b71352007-02-14 07:33:00 +0000989</p>
990
Jim Grosbach67584fe2009-12-17 17:18:11 +0000991<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
992versions of the required w32api and mingw-runtime binaries. The last remaining step for
993Windows users is to simply uncompress the binary binutils package from
994<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
995front end installation steps are not quite the same as a typical manual MinGW installation,
996they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman560e9892003-11-07 19:43:14 +0000997
Jim Grosbach67584fe2009-12-17 17:18:11 +0000998<p>To install binutils on Windows:</p>
999
1000<ol>
1001 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
1002 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
1003 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
1004</ol>
1005
1006<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
1007example, the binary distribution may include an old version of a system header
1008file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
1009libraries not available on your system. In cases like these, you may want to try
1010<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
1011this is much easier now than it was in the past.</p>
1012
1013<p>We also do not currently support updating of the GCC front end by manually overlaying
1014newer versions of the w32api and mingw-runtime binary packages that may become available
1015from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
1016a self-contained convenience package that requires Windows users to simply download and
1017uncompress the GNU Binutils binary package from the MinGW project.</p>
1018
1019<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
1020binaries is not as easy as previously described, or you would like to suggest improvements,
1021please let us know how you would like to see things improved by dropping us a note on our
1022<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001023
1024</div>
1025
1026<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001027<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001028 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001029</h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001030
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001031<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001032
John Criswell58594852007-06-29 19:12:31 +00001033 <p>Once checked out from the Subversion repository, the LLVM suite source
1034 code must be
Reid Spencerdfcf7902004-12-08 16:51:31 +00001035configured via the <tt>configure</tt> script. This script sets variables in the
1036various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
1037<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
1038the Makefiles needed to begin building LLVM.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001039
1040<p>The following environment variables are used by the <tt>configure</tt>
1041script to configure the build system:</p>
1042
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001043<table summary="LLVM configure script environment variables">
Reid Spencerc3c4c4f2004-11-01 08:19:36 +00001044 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman560e9892003-11-07 19:43:14 +00001045 <tr>
1046 <td>CC</td>
1047 <td>Tells <tt>configure</tt> which C compiler to use. By default,
1048 <tt>configure</tt> will look for the first GCC C compiler in
1049 <tt>PATH</tt>. Use this variable to override
1050 <tt>configure</tt>'s default behavior.</td>
1051 </tr>
Misha Brukman560e9892003-11-07 19:43:14 +00001052 <tr>
1053 <td>CXX</td>
1054 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
1055 <tt>configure</tt> will look for the first GCC C++ compiler in
1056 <tt>PATH</tt>. Use this variable to override
1057 <tt>configure</tt>'s default behavior.</td>
1058 </tr>
1059</table>
1060
1061<p>The following options can be used to set or enable LLVM specific options:</p>
1062
Misha Brukmand3de5c62004-01-20 00:20:17 +00001063<dl>
Reid Spencer6bfa7a42004-12-26 05:47:26 +00001064 <dt><i>--with-llvmgccdir</i></dt>
1065 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
1066 The value of this option should specify the full pathname of the C/C++ Front
1067 End to be used. If this option is not provided, the PATH will be searched for
1068 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
1069 be inferred from the path found. If the option is not given, and no llvm-gcc
1070 can be found in the path then a warning will be produced by
1071 <tt>configure</tt> indicating this situation. LLVM may still be built with
1072 the <tt>tools-only</tt> target but attempting to build the runtime libraries
1073 will fail as these libraries require llvm-gcc and llvm-g++. See
1074 <a href="#installcf">Install the GCC Front End</a> for details on installing
1075 the C/C++ Front End. See
Duncan Sands551d3e62008-02-14 17:53:22 +00001076 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencer6bfa7a42004-12-26 05:47:26 +00001077 for details on building the C/C++ Front End.</dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001078 <dt><i>--with-tclinclude</i></dt>
John Criswelle1a81202005-05-18 19:43:33 +00001079 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencerdfcf7902004-12-08 16:51:31 +00001080 found. Use this if you have multiple tcl installations on your machine and you
1081 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
1082 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswelle1a81202005-05-18 19:43:33 +00001083 option, the LLVM configure script will search for the tcl 8.4 and 8.3
1084 releases.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001085 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001086 </dd>
1087 <dt><i>--enable-optimized</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +00001088 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001089 Enables optimized compilation (debugging symbols are removed
1090 and GCC optimization flags are enabled). Note that this is the default
1091 setting if you are using the LLVM distribution. The default behavior
1092 of an Subversion checkout is to use an unoptimized build (also known as a
1093 debug build).
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001094 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001095 </dd>
Reid Spencer294adbb2005-12-21 03:46:45 +00001096 <dt><i>--enable-debug-runtime</i></dt>
1097 <dd>
1098 Enables debug symbols in the runtime libraries. The default is to strip
1099 debug symbols from the runtime libraries.
1100 </dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001101 <dt><i>--enable-jit</i></dt>
Misha Brukman560e9892003-11-07 19:43:14 +00001102 <dd>
John Criswell86a3a482003-12-18 16:43:17 +00001103 Compile the Just In Time (JIT) compiler functionality. This is not
1104 available
Misha Brukman560e9892003-11-07 19:43:14 +00001105 on all platforms. The default is dependent on platform, so it is best
1106 to explicitly enable it if you want it.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001107 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001108 </dd>
Reid Spencer1e195bd2005-04-22 17:58:03 +00001109 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1110 <dd>Controls which targets will be built and linked into llc. The default
1111 value for <tt>target_options</tt> is "all" which builds and links all
1112 available targets. The value "host-only" can be specified to build only a
1113 native compiler (no cross-compiler targets available). The "native" target is
1114 selected as the target of the build host. You can also specify a comma
1115 separated list of target names that you want available in llc. The target
Misha Brukman21a63702008-12-11 18:23:24 +00001116 names use all lower case. The current set of targets is: <br>
Jia Liu5b6562f2012-02-10 04:58:24 +00001117 <tt>arm, cbe, cpp, hexagon, mblaze, mips, mipsel, msp430, powerpc, ptx, sparc, spu, x86, x86_64, xcore</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001118 <br><br></dd>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001119 <dt><i>--enable-doxygen</i></dt>
1120 <dd>Look for the doxygen program and enable construction of doxygen based
1121 documentation from the source code. This is disabled by default because
1122 generating the documentation can take a long time and producess 100s of
1123 megabytes of output.</dd>
Anton Korobeynikovc7f9f3d2007-01-23 12:35:46 +00001124 <dt><i>--with-udis86</i></dt>
1125 <dd>LLVM can use external disassembler library for various purposes (now it's
1126 used only for examining code produced by JIT). This option will enable usage
1127 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1128 bits) disassembler library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001129</dl>
1130
1131<p>To configure LLVM, follow these steps:</p>
1132
1133<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001134 <li><p>Change directory into the object root directory:</p>
John Criswellf531f312003-10-27 18:18:16 +00001135
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001136 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1137
1138 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1139 tree:</p>
1140
1141 <div class="doc_code">
1142 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1143 </div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001144</ol>
John Criswell72989a52003-06-12 19:34:44 +00001145
Misha Brukman560e9892003-11-07 19:43:14 +00001146</div>
John Criswell72989a52003-06-12 19:34:44 +00001147
Misha Brukman560e9892003-11-07 19:43:14 +00001148<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001149<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001150 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001151</h3>
John Criswell72989a52003-06-12 19:34:44 +00001152
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001153<div>
John Criswell71139f22003-07-08 20:35:59 +00001154
Misha Brukman560e9892003-11-07 19:43:14 +00001155<p>Once you have configured LLVM, you can build it. There are three types of
1156builds:</p>
John Criswell71139f22003-07-08 20:35:59 +00001157
Misha Brukmand3de5c62004-01-20 00:20:17 +00001158<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001159 <dt>Debug Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001160 <dd>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001161 These builds are the default when one is using an Subversion checkout and
1162 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1163 used during configuration). The build system will compile the tools and
1164 libraries with debugging information. To get a Debug Build using the
1165 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1166 to <tt>configure</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001167 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001168
1169 <dt>Release (Optimized) Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001170 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001171 These builds are enabled with the <tt>--enable-optimized</tt> option to
1172 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1173 <tt>gmake</tt> command line. For these builds, the build system will
1174 compile the tools and libraries with GCC optimizations enabled and strip
1175 debugging information from the libraries and executables it generates.
Chris Lattner1c1595f2009-04-25 22:24:49 +00001176 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001177 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001178
1179 <dt>Profile Builds
John Criswellc5eb4602003-07-03 16:01:38 +00001180 <dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001181 These builds are for use with profiling. They compile profiling
1182 information into the code for use with programs like <tt>gprof</tt>.
1183 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1184 on the <tt>gmake</tt> command line.
1185</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001186
Misha Brukman560e9892003-11-07 19:43:14 +00001187<p>Once you have LLVM configured, you can build it by entering the
1188<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001189
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001190<div class="doc_code"><pre>% gmake</pre></div>
John Criswell38cc2b52003-10-10 14:26:14 +00001191
Chris Lattnere0050f02004-07-18 22:32:22 +00001192<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell6ab273c2004-12-08 17:53:54 +00001193are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattnere0050f02004-07-18 22:32:22 +00001194
1195<p>
1196If you have multiple processors in your machine, you may wish to use some of
Misha Brukman560e9892003-11-07 19:43:14 +00001197the parallel build options provided by GNU Make. For example, you could use the
1198command:</p>
John Criswell72989a52003-06-12 19:34:44 +00001199
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001200<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellc5eb4602003-07-03 16:01:38 +00001201
Misha Brukman560e9892003-11-07 19:43:14 +00001202<p>There are several special targets which are useful when working with the LLVM
1203source code:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001204
Misha Brukmand3de5c62004-01-20 00:20:17 +00001205<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001206 <dt><tt>gmake clean</tt>
1207 <dd>
1208 Removes all files generated by the build. This includes object files,
1209 generated C/C++ files, libraries, and executables.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001210 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001211
Reid Spencerdfcf7902004-12-08 16:51:31 +00001212 <dt><tt>gmake dist-clean</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001213 <dd>
Misha Brukman5d413912004-08-21 23:40:49 +00001214 Removes everything that <tt>gmake clean</tt> does, but also removes files
1215 generated by <tt>configure</tt>. It attempts to return the source tree to the
1216 original state in which it was shipped.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001217 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001218
Misha Brukman62a2c1f2004-08-23 20:25:33 +00001219 <dt><tt>gmake install</tt>
1220 <dd>
John Criswell6ab273c2004-12-08 17:53:54 +00001221 Installs LLVM header files, libraries, tools, and documentation in a
1222 hierarchy
Reid Spencerdfcf7902004-12-08 16:51:31 +00001223 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1224 defaults to <tt>/usr/local</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001225 <br><br>
1226
Reid Spencerdfcf7902004-12-08 16:51:31 +00001227 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001228 <dd>
Reid Spencer45dc1392004-11-11 07:30:27 +00001229 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greifa54634a2007-07-06 22:07:22 +00001230 install bitcode libraries into the GCC front end's bitcode library
1231 directory. If you need to update your bitcode libraries,
Misha Brukman5d413912004-08-21 23:40:49 +00001232 this is the target to use once you've built them.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001233 <br><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001234</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001235
Reid Spencerdfcf7902004-12-08 16:51:31 +00001236<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1237details on these <tt>make</tt> targets and descriptions of other targets
1238available.</p>
1239
Misha Brukman560e9892003-11-07 19:43:14 +00001240<p>It is also possible to override default values from <tt>configure</tt> by
1241declaring variables on the command line. The following are some examples:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001242
Misha Brukmand3de5c62004-01-20 00:20:17 +00001243<dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001244 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1245 <dd>
1246 Perform a Release (Optimized) build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001247 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001248
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001249 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001250 <dd>
Reid Spencer3dc3ea72006-04-09 23:45:38 +00001251 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001252 <br><br>
Chris Lattner1c1595f2009-04-25 22:24:49 +00001253
1254 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1255 <dd>
1256 Perform a Debug build.
1257 <br><br>
Chris Lattner0f546dd2006-03-21 01:10:57 +00001258
Misha Brukman560e9892003-11-07 19:43:14 +00001259 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1260 <dd>
1261 Perform a Profiling build.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001262 <br><br>
John Criswellc5eb4602003-07-03 16:01:38 +00001263
Misha Brukman560e9892003-11-07 19:43:14 +00001264 <dt><tt>gmake VERBOSE=1</tt>
1265 <dd>
1266 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001267 <br><br>
Reid Spencerdfcf7902004-12-08 16:51:31 +00001268
1269 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1270 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell6ab273c2004-12-08 17:53:54 +00001271 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001272 <br><br></dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001273</dl>
John Criswellc5eb4602003-07-03 16:01:38 +00001274
Misha Brukman560e9892003-11-07 19:43:14 +00001275<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1276it and any subdirectories that it contains. Entering any directory inside the
1277LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1278that directory that is out of date.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001279
Misha Brukman560e9892003-11-07 19:43:14 +00001280</div>
John Criswell38cc2b52003-10-10 14:26:14 +00001281
Misha Brukman560e9892003-11-07 19:43:14 +00001282<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001283<h3>
Reid Spencer734b74f2006-07-27 06:41:31 +00001284 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001285</h3>
Reid Spencerd966b242006-07-27 05:43:30 +00001286
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001287<div>
Jim Grosbach7da1b902009-04-17 17:25:16 +00001288 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1289 executables and libraries to be hosted on a platform different from the
1290 platform where they are build (a Canadian Cross build). To configure a
1291 cross-compile, supply the configure script with <tt>--build</tt> and
1292 <tt>--host</tt> options that are different. The values of these options must
1293 be legal target triples that your GCC compiler supports.</p>
1294
1295 <p>The result of such a build is executables that are not runnable on
1296 on the build host (--build option) but can be executed on the compile host
Reid Spencer734b74f2006-07-27 06:41:31 +00001297 (--host option).</p>
Reid Spencerd966b242006-07-27 05:43:30 +00001298</div>
1299
1300<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001301<h3>
Misha Brukman560e9892003-11-07 19:43:14 +00001302 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001303</h3>
John Criswell38cc2b52003-10-10 14:26:14 +00001304
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001305<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001306
Misha Brukman560e9892003-11-07 19:43:14 +00001307<p>The LLVM build system is capable of sharing a single LLVM source tree among
1308several LLVM builds. Hence, it is possible to build LLVM for several different
1309platforms or configurations using the same source tree.</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001310
Misha Brukman560e9892003-11-07 19:43:14 +00001311<p>This is accomplished in the typical autoconf manner:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001312
Misha Brukman560e9892003-11-07 19:43:14 +00001313<ul>
1314 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001315
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001316 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellc5eb4602003-07-03 16:01:38 +00001317
Misha Brukman560e9892003-11-07 19:43:14 +00001318 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1319 directory:</p>
John Criswellc5eb4602003-07-03 16:01:38 +00001320
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001321 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman560e9892003-11-07 19:43:14 +00001322</ul>
John Criswell72989a52003-06-12 19:34:44 +00001323
Misha Brukman560e9892003-11-07 19:43:14 +00001324<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1325named after the build type:</p>
John Criswell72989a52003-06-12 19:34:44 +00001326
Misha Brukmand3de5c62004-01-20 00:20:17 +00001327<dl>
Duncan Sands1567f0f2010-07-08 08:27:18 +00001328 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman560e9892003-11-07 19:43:14 +00001329 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001330 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001331 <dt>Tools
Duncan Sands1567f0f2010-07-08 08:27:18 +00001332 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001333 <dt>Libraries
Duncan Sands1567f0f2010-07-08 08:27:18 +00001334 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001335 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001336 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001337
Misha Brukman560e9892003-11-07 19:43:14 +00001338 <dt>Release Builds
1339 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001340 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001341 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001342 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001343 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001344 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001345 </dl>
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001346 <br><br>
John Criswell72989a52003-06-12 19:34:44 +00001347
Misha Brukman560e9892003-11-07 19:43:14 +00001348 <dt>Profile Builds
1349 <dd>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001350 <dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001351 <dt>Tools
Reid Spencerdfcf7902004-12-08 16:51:31 +00001352 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001353 <dt>Libraries
Reid Spencerdfcf7902004-12-08 16:51:31 +00001354 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman560e9892003-11-07 19:43:14 +00001355 </dl>
1356</dl>
John Criswell72989a52003-06-12 19:34:44 +00001357
Misha Brukman560e9892003-11-07 19:43:14 +00001358</div>
Chris Lattner1c1ef112002-07-24 19:51:14 +00001359
Chris Lattner998c0672004-03-25 20:38:40 +00001360<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001361<h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001362 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001363</h3>
Chris Lattner998c0672004-03-25 20:38:40 +00001364
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001365<div>
Chris Lattner998c0672004-03-25 20:38:40 +00001366
1367<p>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001368If you're running on a Linux system that supports the "<a
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001369href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattner998c0672004-03-25 20:38:40 +00001370module, and you have root access on the system, you can set your system up to
Bill Wendlingaf5b63f2007-07-16 08:46:40 +00001371execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattner998c0672004-03-25 20:38:40 +00001372first command may not be required if you are already using the module):</p>
1373
Misha Brukman20b8a6562005-02-03 22:25:23 +00001374<div class="doc_code">
Chris Lattner998c0672004-03-25 20:38:40 +00001375<pre>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001376$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckyb8c923b2009-11-04 06:15:28 +00001377$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001378$ chmod u+x hello.bc (if needed)
1379$ ./hello.bc
Chris Lattner998c0672004-03-25 20:38:40 +00001380</pre>
Misha Brukman20b8a6562005-02-03 22:25:23 +00001381</div>
Chris Lattner998c0672004-03-25 20:38:40 +00001382
1383<p>
Chris Lattnerb5c11742010-02-17 18:33:13 +00001384This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi6bd36d52011-04-09 09:51:57 +00001385can also use this command instead of the 'echo' command above:
Chris Lattner998c0672004-03-25 20:38:40 +00001386</p>
1387
Chris Lattnerb5c11742010-02-17 18:33:13 +00001388<div class="doc_code">
1389<pre>
1390$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1391</pre>
1392</div>
1393
Chris Lattner998c0672004-03-25 20:38:40 +00001394</div>
1395
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001396</div>
1397
Misha Brukman560e9892003-11-07 19:43:14 +00001398<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001399<h2>
1400 <a name="layout">Program Layout</a>
1401</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001402<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001403
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001404<div>
John Criswell72989a52003-06-12 19:34:44 +00001405
Misha Brukman560e9892003-11-07 19:43:14 +00001406<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001407href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencerca058542006-03-14 05:39:39 +00001408href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman560e9892003-11-07 19:43:14 +00001409The following is a brief introduction to code layout:</p>
John Criswell72989a52003-06-12 19:34:44 +00001410
Misha Brukman560e9892003-11-07 19:43:14 +00001411<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001412<h3>
1413 <a name="examples"><tt>llvm/examples</tt></a>
1414</h3>
1415
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001416<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001417 <p>This directory contains some simple examples of how to use the LLVM IR and
1418 JIT.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001419</div>
John Criswell72989a52003-06-12 19:34:44 +00001420
Misha Brukman560e9892003-11-07 19:43:14 +00001421<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001422<h3>
1423 <a name="include"><tt>llvm/include</tt></a>
1424</h3>
1425
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001426<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001427
1428<p>This directory contains public header files exported from the LLVM
1429library. The three main subdirectories of this directory are:</p>
1430
Reid Spencer075de232004-09-05 20:50:22 +00001431<dl>
1432 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1433 <dd>This directory contains all of the LLVM specific header files. This
1434 directory also has subdirectories for different portions of LLVM:
1435 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1436 etc...</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001437
Reid Spencer075de232004-09-05 20:50:22 +00001438 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1439 <dd>This directory contains generic support libraries that are provided with
1440 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1441 and a Command Line option processing library store their header files here.
1442 </dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001443
Reid Spencer075de232004-09-05 20:50:22 +00001444 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1445 <dd>This directory contains header files configured by the <tt>configure</tt>
1446 script. They wrap "standard" UNIX and C header files. Source code can
1447 include these header files which automatically take care of the conditional
1448 #includes that the <tt>configure</tt> script generates.</dd>
1449</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001450</div>
1451
1452<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001453<h3>
1454 <a name="lib"><tt>llvm/lib</tt></a>
1455</h3>
1456
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001457<div>
Misha Brukman560e9892003-11-07 19:43:14 +00001458
1459<p>This directory contains most of the source files of the LLVM system. In LLVM,
1460almost all code exists in libraries, making it very easy to share code among the
1461different <a href="#tools">tools</a>.</p>
1462
Misha Brukmand3de5c62004-01-20 00:20:17 +00001463<dl>
Reid Spencer075de232004-09-05 20:50:22 +00001464 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1465 <dd> This directory holds the core LLVM source files that implement core
1466 classes like Instruction and BasicBlock.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001467
Reid Spencer075de232004-09-05 20:50:22 +00001468 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1469 <dd>This directory holds the source code for the LLVM assembly language parser
1470 library.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001471
Gabor Greifa54634a2007-07-06 22:07:22 +00001472 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1473 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001474
Reid Spencer075de232004-09-05 20:50:22 +00001475 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman560e9892003-11-07 19:43:14 +00001476 different program analyses, such as Dominator Information, Call Graphs,
1477 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer075de232004-09-05 20:50:22 +00001478 etc.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001479
Reid Spencer075de232004-09-05 20:50:22 +00001480 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1481 <dd> This directory contains the source code for the LLVM to LLVM program
1482 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1483 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1484 Elimination, and many others.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001485
Reid Spencer075de232004-09-05 20:50:22 +00001486 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1487 <dd> This directory contains files that describe various target architectures
Chris Lattner7991e852006-04-20 17:42:23 +00001488 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1489 directory holds the X86 machine description while
John Criswelle1a81202005-05-18 19:43:33 +00001490 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001491
Reid Spencer075de232004-09-05 20:50:22 +00001492 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1493 <dd> This directory contains the major parts of the code generator: Instruction
1494 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001495
NAKAMURA Takumif8e44c32011-04-05 08:24:15 +00001496 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1497 <dd>(FIXME: T.B.D.)</dd>
1498
1499 <!--FIXME: obsoleted -->
Reid Spencer075de232004-09-05 20:50:22 +00001500 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1501 <dd> This directory contains the source level debugger library that makes
1502 it possible to instrument LLVM programs so that a debugger could identify
1503 source code locations at which the program is executing.</dd>
1504
1505 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001506 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer075de232004-09-05 20:50:22 +00001507 at runtime in both interpreted and JIT compiled fashions.</dd>
1508
1509 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar037fc932011-10-11 20:02:52 +00001510 <dd> This directory contains the source code that corresponds to the header
1511 files located in <tt>llvm/include/ADT/</tt>
1512 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001513</dl>
John Criswell3ef61af2003-06-30 21:59:07 +00001514
Misha Brukman560e9892003-11-07 19:43:14 +00001515</div>
John Criswell72989a52003-06-12 19:34:44 +00001516
Misha Brukman560e9892003-11-07 19:43:14 +00001517<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001518<h3>
1519 <a name="projects"><tt>llvm/projects</tt></a>
1520</h3>
1521
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001522<div>
Reid Spencer5be4f042004-12-08 16:18:26 +00001523 <p>This directory contains projects that are not strictly part of LLVM but are
1524 shipped with LLVM. This is also the directory where you should create your own
1525 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner7b7b6782008-08-11 06:13:31 +00001526 to set up your own project.</p>
Reid Spencer5be4f042004-12-08 16:18:26 +00001527</div>
1528
1529<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001530<h3>
1531 <a name="runtime"><tt>llvm/runtime</tt></a>
1532</h3>
1533
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001534<div>
John Criswell72989a52003-06-12 19:34:44 +00001535
Gabor Greifa54634a2007-07-06 22:07:22 +00001536<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman560e9892003-11-07 19:43:14 +00001537used when linking programs with the GCC front end. Most of these libraries are
1538skeleton versions of real libraries; for example, libc is a stripped down
1539version of glibc.</p>
John Criswell72989a52003-06-12 19:34:44 +00001540
Misha Brukman560e9892003-11-07 19:43:14 +00001541<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1542end to compile.</p>
John Criswell72989a52003-06-12 19:34:44 +00001543
Misha Brukman560e9892003-11-07 19:43:14 +00001544</div>
John Criswell72989a52003-06-12 19:34:44 +00001545
Misha Brukman560e9892003-11-07 19:43:14 +00001546<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001547<h3>
1548 <a name="test"><tt>llvm/test</tt></a>
1549</h3>
1550
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001551<div>
Reid Spencer075de232004-09-05 20:50:22 +00001552 <p>This directory contains feature and regression tests and other basic sanity
1553 checks on the LLVM infrastructure. These are intended to run quickly and cover
1554 a lot of territory without being exhaustive.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001555</div>
John Criswell72989a52003-06-12 19:34:44 +00001556
Misha Brukman560e9892003-11-07 19:43:14 +00001557<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001558<h3>
1559 <a name="test-suite"><tt>test-suite</tt></a>
1560</h3>
1561
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001562<div>
John Criswell58594852007-06-29 19:12:31 +00001563 <p>This is not a directory in the normal llvm module; it is a separate
1564 Subversion
1565 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1566 This
John Criswell6ab273c2004-12-08 17:53:54 +00001567 module contains a comprehensive correctness, performance, and benchmarking
1568 test
John Criswell58594852007-06-29 19:12:31 +00001569 suite for LLVM. It is a separate Subversion module because not every LLVM
1570 user is
John Criswellcfdeb5c2005-05-09 16:39:27 +00001571 interested in downloading or building such a comprehensive test suite. For
1572 further details on this test suite, please see the
Reid Spencer075de232004-09-05 20:50:22 +00001573 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman560e9892003-11-07 19:43:14 +00001574</div>
John Criswell72989a52003-06-12 19:34:44 +00001575
Reid Spencer075de232004-09-05 20:50:22 +00001576<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001577<h3>
1578 <a name="tools"><tt>llvm/tools</tt></a>
1579</h3>
1580
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001581<div>
John Criswell38cc2b52003-10-10 14:26:14 +00001582
Misha Brukman560e9892003-11-07 19:43:14 +00001583<p>The <b>tools</b> directory contains the executables built out of the
1584libraries above, which form the main part of the user interface. You can
Duncan Sands142b9ed2010-02-18 14:08:13 +00001585always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmanb4bd8de2004-11-15 23:20:51 +00001586following is a brief introduction to the most important tools. More detailed
1587information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell38cc2b52003-10-10 14:26:14 +00001588
Misha Brukmand3de5c62004-01-20 00:20:17 +00001589<dl>
John Criswell72989a52003-06-12 19:34:44 +00001590
Reid Spencer075de232004-09-05 20:50:22 +00001591 <dt><tt><b>bugpoint</b></tt></dt>
1592 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman560e9892003-11-07 19:43:14 +00001593 optimization passes or code generation backends by narrowing down the
1594 given test case to the minimum number of passes and/or instructions that
1595 still cause a problem, whether it is a crash or miscompilation. See <a
1596 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer075de232004-09-05 20:50:22 +00001597 on using <tt>bugpoint</tt>.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001598
Reid Spencer075de232004-09-05 20:50:22 +00001599 <dt><tt><b>llvm-ar</b></tt></dt>
1600 <dd>The archiver produces an archive containing
Gabor Greifa54634a2007-07-06 22:07:22 +00001601 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer075de232004-09-05 20:50:22 +00001602 lookup.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001603
Reid Spencer075de232004-09-05 20:50:22 +00001604 <dt><tt><b>llvm-as</b></tt></dt>
1605 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001606 bitcode.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001607
Reid Spencer075de232004-09-05 20:50:22 +00001608 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001609 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer075de232004-09-05 20:50:22 +00001610 LLVM assembly.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001611
Reid Spencer92815e52004-12-08 18:00:30 +00001612 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001613 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Eric Christophercafab2e2011-09-20 00:42:28 +00001614 It performs standard link time optimizations and allows optimization
1615 modules to be loaded and run so that language specific optimizations can
1616 be applied at link time.</dd>
Reid Spencer92815e52004-12-08 18:00:30 +00001617
Reid Spencer075de232004-09-05 20:50:22 +00001618 <dt><tt><b>llvm-link</b></tt></dt>
1619 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1620 a single program.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001621
Reid Spencer075de232004-09-05 20:50:22 +00001622 <dt><tt><b>lli</b></tt></dt>
1623 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky97467822007-12-03 01:58:01 +00001624 can directly execute LLVM bitcode (although very slowly...). For architectures
1625 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1626 will function as a Just-In-Time compiler (if the functionality was compiled
1627 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001628
Reid Spencer075de232004-09-05 20:50:22 +00001629 <dt><tt><b>llc</b></tt></dt>
1630 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greifa54634a2007-07-06 22:07:22 +00001631 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer075de232004-09-05 20:50:22 +00001632 the -march=c option).</dd>
Misha Brukman994d7e82003-10-06 19:23:34 +00001633
Reid Spencer788b0fd2004-12-22 06:29:07 +00001634 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencera7974cc2007-02-09 15:59:08 +00001635 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1636 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greifa54634a2007-07-06 22:07:22 +00001637 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencera7974cc2007-02-09 15:59:08 +00001638 usual machine code output. It works just like any other GCC compiler,
1639 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1640 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell58594852007-06-29 19:12:31 +00001641 separate Subversion module.</dd>
John Criswell72989a52003-06-12 19:34:44 +00001642
Reid Spencer075de232004-09-05 20:50:22 +00001643 <dt><tt><b>opt</b></tt></dt>
Gabor Greifa54634a2007-07-06 22:07:22 +00001644 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer80f843d2006-08-28 00:34:19 +00001645 transformations (which are specified on the command line), and then outputs
Duncan Sands142b9ed2010-02-18 14:08:13 +00001646 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukman21a63702008-12-11 18:23:24 +00001647 get a list of the program transformations available in LLVM.<br>
Reid Spencer80f843d2006-08-28 00:34:19 +00001648 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greifa54634a2007-07-06 22:07:22 +00001649 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer80f843d2006-08-28 00:34:19 +00001650 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman560e9892003-11-07 19:43:14 +00001651</dl>
Misha Brukman560e9892003-11-07 19:43:14 +00001652</div>
John Criswell72989a52003-06-12 19:34:44 +00001653
Misha Brukman560e9892003-11-07 19:43:14 +00001654<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001655<h3>
1656 <a name="utils"><tt>llvm/utils</tt></a>
1657</h3>
1658
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001659<div>
John Criswell72989a52003-06-12 19:34:44 +00001660
Misha Brukman560e9892003-11-07 19:43:14 +00001661<p>This directory contains utilities for working with LLVM source code, and some
1662of the utilities are actually required as part of the build process because they
1663are code generators for parts of LLVM infrastructure.</p>
John Criswell72989a52003-06-12 19:34:44 +00001664
Misha Brukmand3de5c62004-01-20 00:20:17 +00001665<dl>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001666 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman560e9892003-11-07 19:43:14 +00001667 that finds differences between code that LLC generates and code that LLI
1668 generates. This is a useful tool if you are debugging one of them,
1669 assuming that the other generates correct output. For the full user
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001670 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001671
Misha Brukmand3de5c62004-01-20 00:20:17 +00001672 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001673 syntax-highlighting files which will work with Emacs and XEmacs editors,
1674 providing syntax highlighting support for LLVM assembly files and TableGen
1675 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001676 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001677
Misha Brukmand3de5c62004-01-20 00:20:17 +00001678 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman560e9892003-11-07 19:43:14 +00001679 and outputs all non-generated source files, which is useful if one wishes
1680 to do a lot of development across directories and does not want to
1681 individually find each file. One way to use it is to run, for example:
1682 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001683 tree.<br><br>
1684
Reid Spencer075de232004-09-05 20:50:22 +00001685 <dt><tt><b>llvmgrep</b></tt></dt>
1686 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1687 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1688 line. This is a very efficient way of searching the source base for a
1689 particular regular expression.</dd>
1690
Misha Brukmand3de5c62004-01-20 00:20:17 +00001691 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman560e9892003-11-07 19:43:14 +00001692 files in the current directory and then compiles and links the tool that
1693 is the first argument. For example, assuming you are in the directory
1694 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1695 simply running <tt>makellvm llc</tt> will make a build of the current
1696 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001697 causing a re-linking of LLC.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001698
Misha Brukmand3de5c62004-01-20 00:20:17 +00001699 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001700 the tool used to generate register descriptions, instruction set
1701 descriptions, and even assemblers from common TableGen description
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001702 files.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001703
Misha Brukmand3de5c62004-01-20 00:20:17 +00001704 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman560e9892003-11-07 19:43:14 +00001705 syntax-highlighting files which will work with the VIM editor, providing
1706 syntax highlighting support for LLVM assembly files and TableGen
1707 description files. For information on how to use the syntax files, consult
Chris Lattner4d7ce8a2006-09-07 04:19:09 +00001708 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001709
Misha Brukman560e9892003-11-07 19:43:14 +00001710</dl>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001711
Misha Brukman560e9892003-11-07 19:43:14 +00001712</div>
Misha Brukmanefe54be2003-08-11 18:45:46 +00001713
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001714</div>
1715
Misha Brukman560e9892003-11-07 19:43:14 +00001716<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001717<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001718 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001719</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001720<!-- *********************************************************************** -->
Misha Brukmanefe54be2003-08-11 18:45:46 +00001721
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001722<div>
Chad Rosier233f1472012-02-26 21:31:25 +00001723<p>This section gives an example of using LLVM with the Clang front end.</p>
Chris Lattner5b560d92006-08-14 20:45:25 +00001724
1725<!-- ======================================================================= -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001726<h3>
Chad Rosier233f1472012-02-26 21:31:25 +00001727 <a name="tutorial4">Example with clang</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001728</h3>
Chris Lattner5b560d92006-08-14 20:45:25 +00001729
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001730<div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001731
1732<ol>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001733 <li><p>First, create a simple C file, name it 'hello.c':</p>
1734
1735<div class="doc_code">
1736<pre>
1737#include &lt;stdio.h&gt;
1738
1739int main() {
1740 printf("hello world\n");
1741 return 0;
1742}
1743</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001744
1745 <li><p>Next, compile the C file into a native executable:</p>
1746
Chad Rosier233f1472012-02-26 21:31:25 +00001747 <div class="doc_code"><pre>% clang hello.c -o hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001748
Chad Rosier233f1472012-02-26 21:31:25 +00001749 <p>Note that clang works just like GCC by default. The standard -S and
Chris Lattner5b560d92006-08-14 20:45:25 +00001750 -c arguments work as usual (producing a native .s or .o file,
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001751 respectively).</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001752
Gabor Greifa54634a2007-07-06 22:07:22 +00001753 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001754
1755 <div class="doc_code">
Chad Rosier233f1472012-02-26 21:31:25 +00001756 <pre>% clang -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001757
1758 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1759 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1760 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Chad Rosier233f1472012-02-26 21:31:25 +00001761 the bitcode file.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001762
1763 <li><p>Run the program in both forms. To run the program, use:</p>
1764
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001765 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001766
1767 <p>and</p>
1768
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001769 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001770
1771 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattnerc7443af2006-08-14 20:51:35 +00001772 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001773
1774 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1775 code:</p>
1776
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001777<div class="doc_code">
1778<pre>llvm-dis &lt; hello.bc | less</pre>
1779</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001780
1781 <li><p>Compile the program to native assembly using the LLC code
1782 generator:</p>
1783
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001784 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001785
1786 <li><p>Assemble the native assembly language file into a program:</p>
1787
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001788<div class="doc_code">
1789<pre>
1790<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1791
1792<b>Others:</b> % gcc hello.s -o hello.native
1793</pre>
1794</div></li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001795
1796 <li><p>Execute the native code program:</p>
1797
Bill Wendlingbcb3b412007-07-16 08:44:39 +00001798 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5b560d92006-08-14 20:45:25 +00001799
Chad Rosier233f1472012-02-26 21:31:25 +00001800 <p>Note that using clang to compile directly to native code (i.e. when
Chris Lattner5b560d92006-08-14 20:45:25 +00001801 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattnerc7443af2006-08-14 20:51:35 +00001802 </li>
Chris Lattner5b560d92006-08-14 20:45:25 +00001803
1804</ol>
1805
1806</div>
1807
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001808</div>
John Criswell72989a52003-06-12 19:34:44 +00001809
Misha Brukman560e9892003-11-07 19:43:14 +00001810<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001811<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001812 <a name="problems">Common Problems</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001813</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001814<!-- *********************************************************************** -->
John Criswellc5eb4602003-07-03 16:01:38 +00001815
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001816<div>
John Criswellc5eb4602003-07-03 16:01:38 +00001817
Misha Brukman560e9892003-11-07 19:43:14 +00001818<p>If you are having problems building or using LLVM, or if you have any other
1819general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1820Asked Questions</a> page.</p>
John Criswell72989a52003-06-12 19:34:44 +00001821
Misha Brukman560e9892003-11-07 19:43:14 +00001822</div>
John Criswell72989a52003-06-12 19:34:44 +00001823
Misha Brukman560e9892003-11-07 19:43:14 +00001824<!-- *********************************************************************** -->
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001825<h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001826 <a name="links">Links</a>
NAKAMURA Takumifc8d9302011-04-18 23:59:50 +00001827</h2>
Misha Brukman560e9892003-11-07 19:43:14 +00001828<!-- *********************************************************************** -->
John Criswell72989a52003-06-12 19:34:44 +00001829
NAKAMURA Takumiaa3d6242011-04-23 00:30:22 +00001830<div>
John Criswell72989a52003-06-12 19:34:44 +00001831
Bill Wendlingcb13d702008-07-22 01:10:25 +00001832<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman560e9892003-11-07 19:43:14 +00001833some simple things... there are many more interesting and complicated things
1834that you can do that aren't documented here (but we'll gladly accept a patch
1835if you want to write something up!). For more information about LLVM, check
1836out:</p>
John Criswell72989a52003-06-12 19:34:44 +00001837
Misha Brukman560e9892003-11-07 19:43:14 +00001838<ul>
Reid Spencerca058542006-03-14 05:39:39 +00001839 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1840 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1841 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman560e9892003-11-07 19:43:14 +00001842 that Uses LLVM</a></li>
1843</ul>
1844
1845</div>
1846
1847<!-- *********************************************************************** -->
1848
1849<hr>
Misha Brukman74d4df82003-11-22 01:30:01 +00001850<address>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001851 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001852 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001853 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +00001854 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmand3de5c62004-01-20 00:20:17 +00001855
Misha Brukman74d4df82003-11-22 01:30:01 +00001856 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer075de232004-09-05 20:50:22 +00001857 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001858 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman560e9892003-11-07 19:43:14 +00001859 Last modified: $Date$
Misha Brukman74d4df82003-11-22 01:30:01 +00001860</address>
Misha Brukman560e9892003-11-07 19:43:14 +00001861</body>
Guochun Shib65a78e2002-07-17 23:05:56 +00001862</html>