blob: c4fd3a1459aa491bc68f673708cd4e88563d9e84 [file] [log] [blame]
Misha Brukman00c73d22003-11-07 19:43:14 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
Guochun Shif4688a82002-07-17 23:05:56 +00003<html>
Misha Brukman00c73d22003-11-07 19:43:14 +00004<head>
Reid Spencer748d82e2004-11-15 21:15:12 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman00c73d22003-11-07 19:43:14 +00006 <title>Getting Started with LLVM System</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
John Criswell85ed3612003-06-12 19:34:44 +000010
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000011<h1>
Misha Brukman00c73d22003-11-07 19:43:14 +000012 Getting Started with the LLVM System
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000013</h1>
John Criswell85ed3612003-06-12 19:34:44 +000014
Misha Brukman00c73d22003-11-07 19:43:14 +000015<ul>
16 <li><a href="#overview">Overview</a>
17 <li><a href="#quickstart">Getting Started Quickly (A Summary)</a>
18 <li><a href="#requirements">Requirements</a>
Chris Lattner96768ea2003-02-14 04:22:13 +000019 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000020 <li><a href="#hardware">Hardware</a></li>
21 <li><a href="#software">Software</a></li>
22 <li><a href="#brokengcc">Broken versions of GCC and other tools</a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000023 </ol></li>
John Criswell7a73b802003-06-30 21:59:07 +000024
Misha Brukman00c73d22003-11-07 19:43:14 +000025 <li><a href="#starting">Getting Started with LLVM</a>
John Criswell0b459202003-07-08 20:35:59 +000026 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000027 <li><a href="#terminology">Terminology and Notation</a></li>
28 <li><a href="#environment">Setting Up Your Environment</a></li>
29 <li><a href="#unpack">Unpacking the LLVM Archives</a></li>
30 <li><a href="#checkout">Checkout LLVM from Subversion</a></li>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +000031 <li><a href="#git_mirror">LLVM GIT mirror</a></li>
Chris Lattner269f80c2007-11-01 04:20:16 +000032 <li><a href="#installcf">Install the GCC Front End</a></li>
33 <li><a href="#config">Local LLVM Configuration</a></li>
34 <li><a href="#compile">Compiling the LLVM Suite Source Code</a></li>
35 <li><a href="#cross-compile">Cross-Compiling LLVM</a></li>
36 <li><a href="#objfiles">The Location of LLVM Object Files</a></li>
37 <li><a href="#optionalconfig">Optional Configuration Items</a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000038 </ol></li>
John Criswell0b459202003-07-08 20:35:59 +000039
Misha Brukman00c73d22003-11-07 19:43:14 +000040 <li><a href="#layout">Program layout</a>
41 <ol>
Chris Lattner269f80c2007-11-01 04:20:16 +000042 <li><a href="#examples"><tt>llvm/examples</tt></a></li>
43 <li><a href="#include"><tt>llvm/include</tt></a></li>
44 <li><a href="#lib"><tt>llvm/lib</tt></a></li>
45 <li><a href="#projects"><tt>llvm/projects</tt></a></li>
46 <li><a href="#runtime"><tt>llvm/runtime</tt></a></li>
47 <li><a href="#test"><tt>llvm/test</tt></a></li>
Andrew Trickbcf01162010-09-23 20:26:44 +000048 <li><a href="#test-suite"><tt>test-suite</tt></a></li>
Chris Lattner269f80c2007-11-01 04:20:16 +000049 <li><a href="#tools"><tt>llvm/tools</tt></a></li>
50 <li><a href="#utils"><tt>llvm/utils</tt></a></li>
Misha Brukman00c73d22003-11-07 19:43:14 +000051 </ol></li>
John Criswell0f6d7c02003-10-27 18:18:16 +000052
Misha Brukman00c73d22003-11-07 19:43:14 +000053 <li><a href="#tutorial">An Example Using the LLVM Tool Chain</a>
Chris Lattner9abd8af2006-09-07 04:19:09 +000054 <ol>
Chad Rosier372b8222012-02-26 21:31:25 +000055 <li><a href="#tutorial4">Example with Clang</a></li>
Chris Lattner9abd8af2006-09-07 04:19:09 +000056 </ol>
Misha Brukman00c73d22003-11-07 19:43:14 +000057 <li><a href="#problems">Common Problems</a>
58 <li><a href="#links">Links</a>
59</ul>
60
Chris Lattner7911ce22004-05-23 21:07:27 +000061<div class="doc_author">
62 <p>Written by:
63 <a href="mailto:criswell@uiuc.edu">John Criswell</a>,
64 <a href="mailto:sabre@nondot.org">Chris Lattner</a>,
NAKAMURA Takumib9a33632011-04-09 02:13:37 +000065 <a href="http://misha.brukman.net/">Misha Brukman</a>,
Chris Lattner7911ce22004-05-23 21:07:27 +000066 <a href="http://www.cs.uiuc.edu/~vadve">Vikram Adve</a>, and
67 <a href="mailto:gshi1@uiuc.edu">Guochun Shi</a>.
68 </p>
69</div>
Misha Brukman00c73d22003-11-07 19:43:14 +000070
71
72<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +000073<h2>
74 <a name="overview">Overview</a>
75</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +000076<!-- *********************************************************************** -->
77
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +000078<div>
Misha Brukman00c73d22003-11-07 19:43:14 +000079
80<p>Welcome to LLVM! In order to get started, you first need to know some
81basic information.</p>
82
Andrew Trickbcf01162010-09-23 20:26:44 +000083<p>First, LLVM comes in three pieces. The first piece is the LLVM
84suite. This contains all of the tools, libraries, and header files
Jim Grosbachc48d4dc2012-01-25 22:00:23 +000085needed to use LLVM. It contains an assembler, disassembler, bitcode
86analyzer and bitcode optimizer. It also contains basic regression tests that
Chad Rosier372b8222012-02-26 21:31:25 +000087can be used to test the LLVM tools and the Clang front end.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000088
Chad Rosier483454f2012-02-26 21:34:02 +000089<p>The second piece is the <a href="http://clang.llvm.org/">Clang</a> front end.
90This component compiles C, C++, Objective C, and Objective C++ code into LLVM
91bitcode. Once compiled into LLVM bitcode, a program can be manipulated with the
92LLVM tools from the LLVM suite.
Chad Rosier372b8222012-02-26 21:31:25 +000093</p>
Misha Brukman00c73d22003-11-07 19:43:14 +000094
John Criswell3d8ba512004-12-08 17:53:54 +000095<p>
Andrew Trickbcf01162010-09-23 20:26:44 +000096There is a third, optional piece called Test Suite. It is a suite of programs
John Criswell3d8ba512004-12-08 17:53:54 +000097with a testing harness that can be used to further test LLVM's functionality
98and performance.
99</p>
100
Misha Brukman00c73d22003-11-07 19:43:14 +0000101</div>
102
103<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000104<h2>
105 <a name="quickstart">Getting Started Quickly (A Summary)</a>
106</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000107<!-- *********************************************************************** -->
108
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000109<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000110
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000111<p>The LLVM Getting Started documentation may be out of date. So, the Clang
112<a href="http://clang.llvm.org/get_started.html">Getting Started</a> page might
113also be a good place to start.</p>
Chad Rosier8ce6b7d2012-02-23 21:23:24 +0000114
Misha Brukman00c73d22003-11-07 19:43:14 +0000115<p>Here's the short story for getting up and running quickly with LLVM:</p>
116
117<ol>
Reid Spencer9f547912004-11-08 00:29:22 +0000118 <li>Read the documentation.</li>
119 <li>Read the documentation.</li>
120 <li>Remember that you were warned twice about reading the documentation.</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000121
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000122 <li>Checkout LLVM:
Misha Brukman00c73d22003-11-07 19:43:14 +0000123 <ul>
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000124 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
125 <li><tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
126 </ul>
127 </li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000128
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000129 <li>Checkout Clang:
John Criswell9e2485c2004-12-10 15:51:16 +0000130 <ul>
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000131 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
132 <li><tt>cd llvm/tools</tt>
133 <li><tt>svn co http://llvm.org/svn/llvm-project/cfe/trunk clang</tt></li>
134 </ul>
135 </li>
John Criswell9e2485c2004-12-10 15:51:16 +0000136
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000137 <li>Checkout Compiler-RT:
138 <ul>
139 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
140 <li><tt>cd llvm/projects</tt>
141 <li><tt>svn co http://llvm.org/svn/llvm-project/compiler-rt/trunk
142 compiler-rt</tt></li>
143 </ul>
144 </li>
John Criswell9e2485c2004-12-10 15:51:16 +0000145
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000146 <li>Get the Test Suite Source Code <b>[Optional]</b>
147 <ul>
148 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt>
149 <li><tt>cd llvm/projects</tt>
150 <li><tt>svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite</tt></li>
151 </ul>
152 </li>
John Criswell9e2485c2004-12-10 15:51:16 +0000153
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000154 <li>Configure and build LLVM and Clang:
155 <ul>
Misha Brukman9106eca2005-02-03 22:25:23 +0000156 <li><tt>cd <i>where-you-want-to-build-llvm</i></tt></li>
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000157 <li><tt>mkdir build</tt> (for building without polluting the source dir)</li>
158 <li><tt>cd build</tt></li>
159 <li><tt>../llvm/configure [options]</tt></li>
Misha Brukman9106eca2005-02-03 22:25:23 +0000160 Some common options:
161
Misha Brukman00c73d22003-11-07 19:43:14 +0000162 <ul>
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000163 <li><tt>--prefix=<i>directory</i></tt> -
164 Specify for <i>directory</i> the full pathname of where you
Misha Brukman9106eca2005-02-03 22:25:23 +0000165 want the LLVM tools and libraries to be installed (default
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000166 <tt>/usr/local</tt>).</li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000167 </ul>
Misha Brukman00c73d22003-11-07 19:43:14 +0000168
Chad Rosier1cdc9fb2012-02-26 22:12:59 +0000169 <ul>
170 <li><tt>--enable-optimized</tt> -
171 Compile with optimizations enabled (default is NO).</li>
172 </ul>
173
174 <ul>
175 <li><tt>--enable-assertions</tt> -
176 Compile with assertion checks enabled (default is YES).</li>
177 </ul>
178
179 <li><tt>make [-j]</tt> - The -j specifies the number of jobs (commands) to
180 run simultaneously. This builds both LLVM and Clang for Debug+Asserts mode.
181 The --enabled-optimized configure option is used to specify a Release build.</li>
182 <li><tt>make check-all</tt> -
183 This run the regression tests to ensure everything is in working order.</li>
184 <li><tt>make update</tt> -
185 This command is used to update all the svn repositories at once, rather then
186 having to <tt>cd</tt> into the individual repositories and running
187 <tt>svn update</tt>.</li>
188 <li>It is also possible to use CMake instead of the makefiles. With CMake
189 it is also possible to generate project files for several IDEs: Eclipse
190 CDT4, CodeBlocks, Qt-Creator (use the CodeBlocks generator), KDevelop3.</li>
191 <li>If you get an "internal compiler error (ICE)" or test failures, see
192 <a href="#brokengcc">below</a>.</li>
193
194 </ul>
195 </li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000196 </ol>
197
198</ol>
199
Chris Lattnerfcd37252004-06-21 22:52:48 +0000200<p>Consult the <a href="#starting">Getting Started with LLVM</a> section for
Misha Brukman00c73d22003-11-07 19:43:14 +0000201detailed information on configuring and compiling LLVM. See <a
202href="#environment">Setting Up Your Environment</a> for tips that simplify
203working with the GCC front end and LLVM tools. Go to <a href="#layout">Program
204Layout</a> to learn about the layout of the source code tree.</p>
205
206</div>
207
208<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000209<h2>
210 <a name="requirements">Requirements</a>
211</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000212<!-- *********************************************************************** -->
213
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000214<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000215
216<p>Before you begin to use the LLVM system, review the requirements given below.
217This may save you some trouble by knowing ahead of time what hardware and
218software you will need.</p>
219
Misha Brukman00c73d22003-11-07 19:43:14 +0000220<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000221<h3>
222 <a name="hardware">Hardware</a>
223</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000224
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000225<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000226
227<p>LLVM is known to work on the following platforms:</p>
228
Chris Lattner9abd8af2006-09-07 04:19:09 +0000229<table cellpadding="3" summary="Known LLVM platforms">
Misha Brukman14ab5372004-11-15 05:19:53 +0000230<tr>
231 <th>OS</th>
232 <th>Arch</th>
Misha Brukman69def742004-11-19 21:53:22 +0000233 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000234</tr>
235<tr>
Chris Lattnerd8afc462009-07-22 04:21:40 +0000236 <td>AuroraUX</td>
237 <td>x86<sup><a href="#pf_1">1</a></sup></td>
238 <td>GCC</td>
Chris Lattner3e7b5ca2009-07-21 22:47:03 +0000239</tr>
240<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000241 <td>Linux</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000242 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000243 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000244</tr>
245<tr>
Edward O'Callaghan37442b72009-08-04 05:24:28 +0000246 <td>Linux</td>
247 <td>amd64</td>
248 <td>GCC</td>
249</tr>
250<tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000251 <td>Solaris</td>
252 <td>V9 (Ultrasparc)</td>
Misha Brukman69def742004-11-19 21:53:22 +0000253 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000254</tr>
255<tr>
256 <td>FreeBSD</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000257 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000258 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000259</tr>
260<tr>
Bill Wendlingf7226992010-12-15 01:35:55 +0000261 <td>FreeBSD</td>
262 <td>amd64</td>
263 <td>GCC</td>
264</tr>
265<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000266 <td>MacOS X<sup><a href="#pf_2">2</a></sup></td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000267 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000268 <td>GCC</td>
Misha Brukman14ab5372004-11-15 05:19:53 +0000269</tr>
270<tr>
Scott Michel050bc812008-03-18 23:13:26 +0000271 <td>MacOS X<sup><a href="#pf_2">2</a>,<a href="#pf_9">9</a></sup></td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000272 <td>x86</td>
273 <td>GCC</td>
Tanya Lattner993b9802006-04-20 04:35:34 +0000274</tr>
275<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000276 <td>Cygwin/Win32</td>
Anton Korobeynikov16f16922009-12-09 17:26:02 +0000277 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_8">8</a>,
278 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000279 <td>GCC 3.4.X, binutils 2.20</td>
Misha Brukman69def742004-11-19 21:53:22 +0000280</tr>
Misha Brukmanc155a0a2004-12-23 07:14:56 +0000281<tr>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000282 <td>MinGW/Win32</td>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000283 <td>x86<sup><a href="#pf_1">1</a>,<a href="#pf_6">6</a>,
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000284 <a href="#pf_8">8</a>, <a href="#pf_10">10</a>,
285 <a href="#pf_11">11</a></sup></td>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000286 <td>GCC 3.4.X, binutils 2.20</td>
Chris Lattner8ccb87f2005-02-09 20:43:48 +0000287</tr>
Misha Brukman69def742004-11-19 21:53:22 +0000288</table>
289
290<p>LLVM has partial support for the following platforms:</p>
291
Chris Lattner9abd8af2006-09-07 04:19:09 +0000292<table summary="LLVM partial platform support">
Misha Brukman69def742004-11-19 21:53:22 +0000293<tr>
294 <th>OS</th>
295 <th>Arch</th>
296 <th>Compilers</th>
Misha Brukman14ab5372004-11-15 05:19:53 +0000297</tr>
Misha Brukman00117692004-11-15 21:05:08 +0000298<tr>
Misha Brukman69def742004-11-19 21:53:22 +0000299 <td>Windows</td>
Chris Lattner7db3f522005-02-09 21:15:51 +0000300 <td>x86<sup><a href="#pf_1">1</a></sup></td>
Chandler Carruth2929de42011-11-16 19:52:13 +0000301 <td>Visual Studio 2008 or higher<sup><a href="#pf_4">4</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000302<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000303 <td>AIX<sup><a href="#pf_3">3</a>,<a href="#pf_4">4</a></sup></td>
Misha Brukman00117692004-11-15 21:05:08 +0000304 <td>PowerPC</td>
Misha Brukman69def742004-11-19 21:53:22 +0000305 <td>GCC</td>
306</tr>
307<tr>
Chris Lattner7db3f522005-02-09 21:15:51 +0000308 <td>Linux<sup><a href="#pf_3">3</a>,<a href="#pf_5">5</a></sup></td>
Misha Brukman69def742004-11-19 21:53:22 +0000309 <td>PowerPC</td>
310 <td>GCC</td>
Misha Brukman00117692004-11-15 21:05:08 +0000311</tr>
John Criswell75162552005-05-09 16:49:59 +0000312
313<tr>
314 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
315 <td>Alpha</td>
316 <td>GCC</td>
317</tr>
318<tr>
319 <td>Linux<sup><a href="#pf_7">7</a></sup></td>
320 <td>Itanium (IA-64)</td>
321 <td>GCC</td>
322</tr>
Duraid Madinae8714af2005-05-10 06:57:53 +0000323<tr>
324 <td>HP-UX<sup><a href="#pf_7">7</a></sup></td>
325 <td>Itanium (IA-64)</td>
326 <td>HP aCC</td>
327</tr>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000328<tr>
329 <td>Windows x64</td>
330 <td>x86-64</td>
331 <td>mingw-w64's GCC-4.5.x<sup><a href="#pf_12">12</a></sup></td>
332</tr>
Misha Brukman14ab5372004-11-15 05:19:53 +0000333</table>
Misha Brukman00c73d22003-11-07 19:43:14 +0000334
Misha Brukmana892ead2005-02-09 21:01:26 +0000335<p><b>Notes:</b></p>
336
Misha Brukman6d8e1532005-02-09 22:38:47 +0000337<div class="doc_notes">
338<ol>
339<li><a name="pf_1">Code generation supported for Pentium processors and
340up</a></li>
341<li><a name="pf_2">Code generation supported for 32-bit ABI only</a></li>
342<li><a name="pf_3">No native code generation</a></li>
Nick Lewycky28ea4f62008-12-08 00:45:02 +0000343<li><a name="pf_4">Build is not complete: one or more tools do not link or function</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000344<li><a name="pf_5">The GCC-based C/C++ frontend does not build</a></li>
Chris Lattner01bb8b02009-01-02 07:10:51 +0000345<li><a name="pf_6">The port is done using the MSYS shell.</a></li>
John Criswell75162552005-05-09 16:49:59 +0000346<li><a name="pf_7">Native code generation exists but is not complete.</a></li>
Anton Korobeynikov780679b2010-02-11 21:51:51 +0000347<li><a name="pf_8">Binutils 2.20 or later is required to build the assembler
348 generated by LLVM properly.</a></li>
Chris Lattner22b91d72008-11-09 17:19:14 +0000349<li><a name="pf_9">XCode 2.5 and gcc 4.0.1</a> (Apple Build 5370) will trip
Scott Michel050bc812008-03-18 23:13:26 +0000350 internal LLVM assert messages when compiled for Release at optimization
Chris Lattner22b91d72008-11-09 17:19:14 +0000351 levels greater than 0 (i.e., <i>"-O1"</i> and higher).
352 Add <i>OPTIMIZE_OPTION="-O0"</i> to the build command line
Scott Michel050bc812008-03-18 23:13:26 +0000353 if compiling for LLVM Release or bootstrapping the LLVM toolchain.</li>
Anton Korobeynikov2bc8ef12009-08-06 12:54:58 +0000354<li><a name="pf_10">For MSYS/MinGW on Windows, be sure to install the MSYS
355 version of the perl package, and be sure it appears in your path
356 before any Windows-based versions such as Strawberry Perl and
357 ActivePerl, as these have Windows-specifics that will cause the
358 build to fail.</a></li>
NAKAMURA Takumi3c496552011-03-28 06:27:06 +0000359<li><a name="pf_11">To use LLVM modules on Win32-based system,
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000360 you may configure LLVM with <i>&quot;--enable-shared&quot;</i>.</a></li>
NAKAMURA Takumi282fdd32011-03-28 06:27:12 +0000361<li><a name="pf_12">To compile SPU backend, you need to add
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000362 <tt>&quot;LDFLAGS=-Wl,--stack,16777216&quot;</tt> to configure.</a></li>
Misha Brukmana892ead2005-02-09 21:01:26 +0000363</ol>
Misha Brukmana892ead2005-02-09 21:01:26 +0000364</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000365
Misha Brukman69def742004-11-19 21:53:22 +0000366<p>Note that you will need about 1-3 GB of space for a full LLVM build in Debug
John Criswell8bfe6a72005-05-18 19:43:33 +0000367mode, depending on the system (it is so large because of all the debugging
368information and the fact that the libraries are statically linked into multiple
Chris Lattner06942902009-04-25 22:08:52 +0000369tools). If you do not need many of the tools and you are space-conscious, you
370can pass <tt>ONLY_TOOLS="tools you need"</tt> to make. The Release build
371requires considerably less space.</p>
Misha Brukman69def742004-11-19 21:53:22 +0000372
Misha Brukman00c73d22003-11-07 19:43:14 +0000373<p>The LLVM suite <i>may</i> compile on other platforms, but it is not
374guaranteed to do so. If compilation is successful, the LLVM utilities should be
Gabor Greif04367bf2007-07-06 22:07:22 +0000375able to assemble, disassemble, analyze, and optimize LLVM bitcode. Code
Misha Brukman00c73d22003-11-07 19:43:14 +0000376generation should work as well, although the generated native code may not work
377on your platform.</p>
378
379<p>The GCC front end is not very portable at the moment. If you want to get it
Misha Brukman22e9e332004-08-09 19:57:01 +0000380to work on another platform, you can download a copy of the source and <a
Duncan Sands8655b152008-02-14 17:53:22 +0000381href="GCCFEBuildInstrs.html">try to compile it</a> on your platform.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000382
383</div>
384
385<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000386<h3>
387 <a name="software">Software</a>
388</h3>
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000389<div>
Reid Spencer748d82e2004-11-15 21:15:12 +0000390 <p>Compiling LLVM requires that you have several software packages
391 installed. The table below lists those required packages. The Package column
392 is the usual name for the software package that LLVM depends on. The Version
393 column provides "known to work" versions of the package. The Notes column
394 describes how LLVM uses the package and provides other details.</p>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000395 <table summary="Packages required to compile LLVM">
Reid Spencer748d82e2004-11-15 21:15:12 +0000396 <tr><th>Package</th><th>Version</th><th>Notes</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000397
Reid Spencer748d82e2004-11-15 21:15:12 +0000398 <tr>
399 <td><a href="http://savannah.gnu.org/projects/make">GNU Make</a></td>
400 <td>3.79, 3.79.1</td>
401 <td>Makefile/build processor</td>
402 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000403
Reid Spencer748d82e2004-11-15 21:15:12 +0000404 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000405 <td><a href="http://gcc.gnu.org/">GCC</a></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000406 <td>3.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000407 <td>C/C++ compiler<sup><a href="#sf1">1</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000408 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000409
Reid Spencer748d82e2004-11-15 21:15:12 +0000410 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000411 <td><a href="http://www.gnu.org/software/texinfo/">TeXinfo</a></td>
Chris Lattner2286cab2005-09-06 04:07:15 +0000412 <td>4.5</td>
413 <td>For building the CFE</td>
414 </tr>
415
416 <tr>
John Criswell9c29bfb2007-06-29 19:12:31 +0000417 <td><a href="http://subversion.tigris.org/project_packages.html">SVN</a></td>
418 <td>&ge;1.3</td>
419 <td>Subversion access to LLVM<sup><a href="#sf2">2</a></sup></td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000420 </tr>
421
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +0000422 <!-- FIXME:
423 Do we support dg?
424 Are DejaGnu and expect obsolete?
425 Shall we mention Python? -->
426
Misha Brukman6d8e1532005-02-09 22:38:47 +0000427 <tr>
Reid Spencer748d82e2004-11-15 21:15:12 +0000428 <td><a href="http://savannah.gnu.org/projects/dejagnu">DejaGnu</a></td>
429 <td>1.4.2</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000430 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000431 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000432
Reid Spencer748d82e2004-11-15 21:15:12 +0000433 <tr>
434 <td><a href="http://www.tcl.tk/software/tcltk/">tcl</a></td>
435 <td>8.3, 8.4</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000436 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000437 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +0000438
Reid Spencer748d82e2004-11-15 21:15:12 +0000439 <tr>
440 <td><a href="http://expect.nist.gov/">expect</a></td>
441 <td>5.38.0</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000442 <td>Automated test suite<sup><a href="#sf3">3</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000443 </tr>
444
445 <tr>
446 <td><a href="http://www.perl.com/download.csp">perl</a></td>
Reid Spencer200d93b2004-12-09 17:55:37 +0000447 <td>&ge;5.6.0</td>
Daniel Dunbar5b106562012-02-15 19:24:11 +0000448 <td>Utilities</td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000449 </tr>
450
451 <tr>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000452 <td><a href="http://savannah.gnu.org/projects/m4">GNU M4</a>
453 <td>1.4</td>
454 <td>Macro processor for configuration<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000455 </tr>
456
457 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000458 <td><a href="http://www.gnu.org/software/autoconf/">GNU Autoconf</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000459 <td>2.60</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000460 <td>Configuration script builder<sup><a href="#sf4">4</a></sup></td>
461 </tr>
462
463 <tr>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000464 <td><a href="http://www.gnu.org/software/automake/">GNU Automake</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000465 <td>1.9.6</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000466 <td>aclocal macro generator<sup><a href="#sf4">4</a></sup></td>
467 </tr>
468
469 <tr>
470 <td><a href="http://savannah.gnu.org/projects/libtool">libtool</a></td>
Nick Lewycky2a0ed092009-09-27 04:56:27 +0000471 <td>1.5.22</td>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000472 <td>Shared library manager<sup><a href="#sf4">4</a></sup></td>
Reid Spencer748d82e2004-11-15 21:15:12 +0000473 </tr>
474
475 </table>
476
Misha Brukman6d8e1532005-02-09 22:38:47 +0000477 <p><b>Notes:</b></p>
478 <div class="doc_notes">
Reid Spencer748d82e2004-11-15 21:15:12 +0000479 <ol>
Chris Lattner9abd8af2006-09-07 04:19:09 +0000480 <li><a name="sf1">Only the C and C++ languages are needed so there's no
Misha Brukman6d8e1532005-02-09 22:38:47 +0000481 need to build the other languages for LLVM's purposes.</a> See
482 <a href="#brokengcc">below</a> for specific version info.</li>
John Criswell9c29bfb2007-06-29 19:12:31 +0000483 <li><a name="sf2">You only need Subversion if you intend to build from the
Misha Brukman6d8e1532005-02-09 22:38:47 +0000484 latest LLVM sources. If you're working from a release distribution, you
John Criswell9c29bfb2007-06-29 19:12:31 +0000485 don't need Subversion.</a></li>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000486 <li><a name="sf3">Only needed if you want to run the automated test
487 suite in the <tt>llvm/test</tt> directory.</a></li>
488 <li><a name="sf4">If you want to make changes to the configure scripts,
Tobias Grosser0560ce42010-05-19 07:00:17 +0000489 you will need GNU autoconf (2.60), and consequently, GNU M4 (version 1.4
490 or higher). You will also need automake (1.9.6). We only use aclocal
Reid Spencer200d93b2004-12-09 17:55:37 +0000491 from that package.</a></li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000492 </ol>
Misha Brukman6d8e1532005-02-09 22:38:47 +0000493 </div>
494
Reid Spencer748d82e2004-11-15 21:15:12 +0000495 <p>Additionally, your compilation host is expected to have the usual
496 plethora of Unix utilities. Specifically:</p>
497 <ul>
498 <li><b>ar</b> - archive library builder</li>
499 <li><b>bzip2*</b> - bzip2 command for distribution generation</li>
500 <li><b>bunzip2*</b> - bunzip2 command for distribution checking</li>
501 <li><b>chmod</b> - change permissions on a file</li>
John Criswellc4ef3f22004-12-08 16:55:27 +0000502 <li><b>cat</b> - output concatenation utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000503 <li><b>cp</b> - copy files</li>
504 <li><b>date</b> - print the current date/time </li>
505 <li><b>echo</b> - print to standard output</li>
506 <li><b>egrep</b> - extended regular expression search utility</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000507 <li><b>find</b> - find files/dirs in a file system</li>
508 <li><b>grep</b> - regular expression search utility</li>
509 <li><b>gzip*</b> - gzip command for distribution generation</li>
510 <li><b>gunzip*</b> - gunzip command for distribution checking</li>
511 <li><b>install</b> - install directories/files </li>
512 <li><b>mkdir</b> - create a directory</li>
513 <li><b>mv</b> - move (rename) files</li>
514 <li><b>ranlib</b> - symbol table builder for archive libraries</li>
Misha Brukman616bd052004-11-20 01:27:40 +0000515 <li><b>rm</b> - remove (delete) files and directories</li>
Reid Spencer748d82e2004-11-15 21:15:12 +0000516 <li><b>sed</b> - stream editor for transforming output</li>
517 <li><b>sh</b> - Bourne shell for make build scripts</li>
518 <li><b>tar</b> - tape archive for distribution generation</li>
519 <li><b>test</b> - test things in file system</li>
520 <li><b>unzip*</b> - unzip command for distribution checking</li>
521 <li><b>zip*</b> - zip command for distribution generation</li>
522 </ul>
Chris Lattner95e92582004-07-18 22:32:22 +0000523</div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000524
Chris Lattner95e92582004-07-18 22:32:22 +0000525<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000526<h3>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000527 <a name="brokengcc">Broken versions of GCC and other tools</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000528</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000529
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000530<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000531
532<p>LLVM is very demanding of the host C++ compiler, and as such tends to expose
533bugs in the compiler. In particular, several versions of GCC crash when trying
Ted Kremenek0ba11792011-10-31 21:23:15 +0000534to compile LLVM. We routinely use GCC 4.2 (and higher) or Clang.
535Other versions of GCC will probably work as well. GCC versions listed
Chris Lattner95e92582004-07-18 22:32:22 +0000536here are known to not work. If you are using one of these versions, please try
537to upgrade your GCC to something more recent. If you run into a problem with a
538version of GCC not listed here, please <a href="mailto:llvmdev@cs.uiuc.edu">let
539us know</a>. Please use the "<tt>gcc -v</tt>" command to find out which version
540of GCC you are using.
541</p>
542
543<p><b>GCC versions prior to 3.0</b>: GCC 2.96.x and before had several
544problems in the STL that effectively prevent it from compiling LLVM.
545</p>
546
Chris Lattner82f0a092008-02-13 17:50:24 +0000547<p><b>GCC 3.2.2 and 3.2.3</b>: These versions of GCC fails to compile LLVM with
548a bogus template error. This was fixed in later GCCs.</p>
John Criswell294ba022004-11-23 22:06:24 +0000549
Chris Lattner95e92582004-07-18 22:32:22 +0000550<p><b>GCC 3.3.2</b>: This version of GCC suffered from a <a
551href="http://gcc.gnu.org/PR13392">serious bug</a> which causes it to crash in
552the "<tt>convert_from_eh_region_ranges_1</tt>" GCC function.</p>
Chris Lattner25e7b162005-02-12 20:11:13 +0000553
Chris Lattner8e64f152005-02-13 22:20:49 +0000554<p><b>Cygwin GCC 3.3.3</b>: The version of GCC 3.3.3 commonly shipped with
Duncan Sands8655b152008-02-14 17:53:22 +0000555 Cygwin does not work. Please <a href="GCCFEBuildInstrs.html#cygwin">upgrade
Chris Lattner8e64f152005-02-13 22:20:49 +0000556 to a newer version</a> if possible.</p>
557<p><b>SuSE GCC 3.3.3</b>: The version of GCC 3.3.3 shipped with SuSE 9.1 (and
558 possibly others) does not compile LLVM correctly (it appears that exception
559 handling is broken in some cases). Please download the FSF 3.3.3 or upgrade
560 to a newer version of GCC.</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000561<p><b>GCC 3.4.0 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000562 code generator, causing an infinite loop in the llvm-gcc build when built
563 with optimizations enabled (i.e. a release build).</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000564<p><b>GCC 3.4.2 on linux/x86 (32-bit)</b>: GCC miscompiles portions of the
Chris Lattner36117ac2007-05-10 06:42:21 +0000565 code generator at -O3, as with 3.4.0. However gcc 3.4.2 (unlike 3.4.0)
566 correctly compiles LLVM at -O2. A work around is to build release LLVM
567 builds with "make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2 ..."</p>
Bill Wendling18bf0d02007-07-16 08:52:56 +0000568<p><b>GCC 3.4.x on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1056">
Chris Lattner77c2af62007-04-01 20:14:46 +0000569 miscompiles portions of LLVM</a>.</p>
Chris Lattner269f80c2007-11-01 04:20:16 +0000570<p><b>GCC 3.4.4 (CodeSourcery ARM 2005q3-2)</b>: this compiler miscompiles LLVM
571 when building with optimizations enabled. It appears to work with
572 "<tt>make ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O1</tt>" or build a debug
573 build.</p>
Chris Lattnerf2b5e6e2005-05-15 22:26:45 +0000574<p><b>IA-64 GCC 4.0.0</b>: The IA-64 version of GCC 4.0.0 is known to
575 miscompile LLVM.</p>
Chris Lattnerdd197912006-06-16 19:53:39 +0000576<p><b>Apple Xcode 2.3</b>: GCC crashes when compiling LLVM at -O3 (which is the
577 default with ENABLE_OPTIMIZED=1. To work around this, build with
578 "ENABLE_OPTIMIZED=1 OPTIMIZE_OPTION=-O2".</p>
Chris Lattnerc40eb5e2006-09-07 17:34:27 +0000579<p><b>GCC 4.1.1</b>: GCC fails to build LLVM with template concept check errors
580 compiling some files. At the time of this writing, GCC mainline (4.2)
581 did not share the problem.</p>
Chris Lattner78ce3b82007-01-04 07:06:05 +0000582<p><b>GCC 4.1.1 on X86-64/amd64</b>: GCC <a href="http://llvm.org/PR1063">
583 miscompiles portions of LLVM</a> when compiling llvm itself into 64-bit
584 code. LLVM will appear to mostly work but will be buggy, e.g. failing
585 portions of its testsuite.</p>
Reid Spencer72f92f02007-04-11 21:28:31 +0000586<p><b>GCC 4.1.2 on OpenSUSE</b>: Seg faults during libstdc++ build and on x86_64
587platforms compiling md5.c gets a mangled constant.</p>
Daniel Dunbarb7dfaf92008-10-11 18:40:33 +0000588<p><b>GCC 4.1.2 (20061115 (prerelease) (Debian 4.1.1-21)) on Debian</b>: Appears
589to miscompile parts of LLVM 2.4. One symptom is ValueSymbolTable complaining
590about symbols remaining in the table on destruction.</p>
Nuno Lopesf82242d2008-12-10 16:11:10 +0000591<p><b>GCC 4.1.2 20071124 (Red Hat 4.1.2-42)</b>: Suffers from the same symptoms
Nuno Lopes58dc0b52008-12-10 16:01:22 +0000592as the previous one. It appears to work with ENABLE_OPTIMIZED=0 (the default).</p>
Mike Stumpfe095f32009-05-04 18:40:41 +0000593<p><b>Cygwin GCC 4.3.2 20080827 (beta) 2</b>:
594 Users <a href="http://llvm.org/PR4145">reported</a> various problems related
595 with link errors when using this GCC version.</p>
Chris Lattner478e71d2009-09-10 16:25:02 +0000596<p><b>Debian GCC 4.3.2 on X86</b>: Crashes building some files in LLVM 2.6.</p>
Nick Lewycky3bf2d032009-07-17 06:32:10 +0000597<p><b>GCC 4.3.3 (Debian 4.3.3-10) on ARM</b>: Miscompiles parts of LLVM 2.6
598when optimizations are turned on. The symptom is an infinite loop in
Chris Lattner478e71d2009-09-10 16:25:02 +0000599FoldingSetImpl::RemoveNode while running the code generator.</p>
Nick Lewycky256f9602010-10-07 22:30:47 +0000600<p><b>GCC 4.3.5 and GCC 4.4.5 on ARM</b>: These can miscompile <tt>value >>
6011</tt> even at -O0. A test failure in <tt>test/Assembler/alignstack.ll</tt> is
602one symptom of the problem.
Reid Spencer7a119082006-11-04 00:33:42 +0000603<p><b>GNU ld 2.16.X</b>. Some 2.16.X versions of the ld linker will produce very
604long warning messages complaining that some ".gnu.linkonce.t.*" symbol was
605defined in a discarded section. You can safely ignore these messages as they are
606erroneous and the linkage is correct. These messages disappear using ld
6072.17.</p>
Chris Lattnerdefb9fb2007-06-19 05:52:36 +0000608
609<p><b>GNU binutils 2.17</b>: Binutils 2.17 contains <a
610href="http://sourceware.org/bugzilla/show_bug.cgi?id=3111">a bug</a> which
611causes huge link times (minutes instead of seconds) when building LLVM. We
612recommend upgrading to a newer version (2.17.50.0.4 or later).</p>
613
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000614<p><b>GNU Binutils 2.19.1 Gold</b>: This version of Gold contained
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000615<a href="http://sourceware.org/bugzilla/show_bug.cgi?id=9836">a bug</a>
616which causes intermittent failures when building LLVM with position independent
Nick Lewyckybb2b5212009-03-03 05:41:16 +0000617code. The symptom is an error about cyclic dependencies. We recommend
618upgrading to a newer version of Gold.</p>
Nick Lewyckyd9f66e62009-02-25 06:29:47 +0000619
Misha Brukman00c73d22003-11-07 19:43:14 +0000620</div>
621
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000622</div>
Chris Lattner95e92582004-07-18 22:32:22 +0000623
Misha Brukman00c73d22003-11-07 19:43:14 +0000624<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000625<h2>
626 <a name="starting">Getting Started with LLVM</a>
627</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +0000628<!-- *********************************************************************** -->
629
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000630<div>
Chris Lattner95e92582004-07-18 22:32:22 +0000631
632<p>The remainder of this guide is meant to get you up and running with
633LLVM and to give you some basic information about the LLVM environment.</p>
634
635<p>The later sections of this guide describe the <a
636href="#layout">general layout</a> of the the LLVM source tree, a <a
637href="#tutorial">simple example</a> using the LLVM tool chain, and <a
638href="#links">links</a> to find more information about LLVM or to get
639help via e-mail.</p>
Chris Lattner95e92582004-07-18 22:32:22 +0000640
Misha Brukman00c73d22003-11-07 19:43:14 +0000641<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000642<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000643 <a name="terminology">Terminology and Notation</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000644</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000645
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000646<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000647
648<p>Throughout this manual, the following names are used to denote paths
649specific to the local system and working environment. <i>These are not
650environment variables you need to set but just strings used in the rest
651of this document below</i>. In any of the examples below, simply replace
652each of these names with the appropriate pathname on your local system.
653All these paths are absolute:</p>
654
Misha Brukman54111c42004-01-20 00:20:17 +0000655<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +0000656 <dt>SRC_ROOT
657 <dd>
658 This is the top level directory of the LLVM source tree.
Chris Lattner9abd8af2006-09-07 04:19:09 +0000659 <br><br>
John Criswell0f6d7c02003-10-27 18:18:16 +0000660
Misha Brukman00c73d22003-11-07 19:43:14 +0000661 <dt>OBJ_ROOT
662 <dd>
663 This is the top level directory of the LLVM object tree (i.e. the
664 tree where object files and compiled programs will be placed. It
665 can be the same as SRC_ROOT).
Chris Lattner9abd8af2006-09-07 04:19:09 +0000666 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +0000667
668 <dt>LLVMGCCDIR
669 <dd>
Reid Spencerfef93b72004-12-26 05:47:26 +0000670 This is where the LLVM GCC Front End is installed.
Misha Brukman00c73d22003-11-07 19:43:14 +0000671 <p>
672 For the pre-built GCC front end binaries, the LLVMGCCDIR is
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000673 <tt>llvm-gcc/<i>platform</i>/llvm-gcc</tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +0000674</dl>
675
676</div>
677
678<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000679<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000680 <a name="environment">Setting Up Your Environment</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000681</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000682
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000683<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000684
685<p>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000686In order to compile and use LLVM, you may need to set some environment
687variables.
Misha Brukman00c73d22003-11-07 19:43:14 +0000688
Misha Brukman54111c42004-01-20 00:20:17 +0000689<dl>
Gabor Greif04367bf2007-07-06 22:07:22 +0000690 <dt><tt>LLVM_LIB_SEARCH_PATH</tt>=<tt>/path/to/your/bitcode/libs</tt></dt>
Misha Brukman8f0cad12005-02-03 18:28:08 +0000691 <dd>[Optional] This environment variable helps LLVM linking tools find the
Gabor Greif04367bf2007-07-06 22:07:22 +0000692 locations of your bitcode libraries. It is provided only as a
Misha Brukman8f0cad12005-02-03 18:28:08 +0000693 convenience since you can specify the paths using the -L options of the
Gabor Greif04367bf2007-07-06 22:07:22 +0000694 tools and the C/C++ front-end will automatically use the bitcode files
John Criswell8bfe6a72005-05-18 19:43:33 +0000695 installed in its
Misha Brukman8f0cad12005-02-03 18:28:08 +0000696 <tt>lib</tt> directory.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000697</dl>
698
699</div>
700
701<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000702<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000703 <a name="unpack">Unpacking the LLVM Archives</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000704</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000705
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000706<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000707
708<p>
709If you have the LLVM distribution, you will need to unpack it before you
John Criswelld000e1d2003-12-18 16:43:17 +0000710can begin to compile it. LLVM is distributed as a set of two files: the LLVM
John Criswell9e2485c2004-12-10 15:51:16 +0000711suite and the LLVM GCC front end compiled for your platform. There is an
712additional test suite that is optional. Each file is a TAR archive that is
713compressed with the gzip program.
Misha Brukman00c73d22003-11-07 19:43:14 +0000714</p>
715
Misha Brukman3ce11032005-02-02 18:01:57 +0000716<p>The files are as follows, with <em>x.y</em> marking the version number:
Misha Brukman54111c42004-01-20 00:20:17 +0000717<dl>
Misha Brukman3ce11032005-02-02 18:01:57 +0000718 <dt><tt>llvm-x.y.tar.gz</tt></dt>
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000719 <dd>Source release for the LLVM libraries and tools.<br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +0000720
Misha Brukman3ce11032005-02-02 18:01:57 +0000721 <dt><tt>llvm-test-x.y.tar.gz</tt></dt>
Andrew Trickbcf01162010-09-23 20:26:44 +0000722 <dd>Source release for the LLVM test-suite.</dd>
Misha Brukman8f9e6d62004-11-23 19:26:24 +0000723
Misha Brukmanccd02952008-12-29 19:38:58 +0000724 <dt><tt>llvm-gcc-4.2-x.y.source.tar.gz</tt></dt>
725 <dd>Source release of the llvm-gcc-4.2 front end. See README.LLVM in the root
Misha Brukmanf00ddb02008-12-11 18:23:24 +0000726 directory for build instructions.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000727
Misha Brukmanccd02952008-12-29 19:38:58 +0000728 <dt><tt>llvm-gcc-4.2-x.y-platform.tar.gz</tt></dt>
729 <dd>Binary release of the llvm-gcc-4.2 front end for a specific platform.<br></dd>
Chris Lattner1ef81af2006-04-20 05:08:23 +0000730
Misha Brukman00c73d22003-11-07 19:43:14 +0000731</dl>
732
733</div>
734
735<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000736<h3>
John Criswell9c29bfb2007-06-29 19:12:31 +0000737 <a name="checkout">Checkout LLVM from Subversion</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000738</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000739
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000740<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000741
John Criswell9c29bfb2007-06-29 19:12:31 +0000742<p>If you have access to our Subversion repository, you can get a fresh copy of
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000743the entire source code. All you need to do is check it out from Subversion as
Misha Brukman00c73d22003-11-07 19:43:14 +0000744follows:</p>
745
746<ul>
John Criswell9c29bfb2007-06-29 19:12:31 +0000747 <li><tt>cd <i>where-you-want-llvm-to-live</i></tt></li>
Anton Korobeynikov98044e42007-06-29 20:56:49 +0000748 <li>Read-Only: <tt>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm</tt></li>
749 <li>Read-Write:<tt>svn co https://user@llvm.org/svn/llvm-project/llvm/trunk
John Criswell9c29bfb2007-06-29 19:12:31 +0000750 llvm</tt></li>
Misha Brukman00c73d22003-11-07 19:43:14 +0000751</ul>
752
John Criswell9c29bfb2007-06-29 19:12:31 +0000753
Misha Brukman00c73d22003-11-07 19:43:14 +0000754<p>This will create an '<tt>llvm</tt>' directory in the current
755directory and fully populate it with the LLVM source code, Makefiles,
756test directories, and local copies of documentation files.</p>
757
Misha Brukman54111c42004-01-20 00:20:17 +0000758<p>If you want to get a specific release (as opposed to the most recent
Anton Korobeynikovd933fa92007-06-29 23:13:42 +0000759revision), you can checkout it from the '<tt>tags</tt>' directory (instead of
Anton Korobeynikovd724dc82007-06-30 00:00:57 +0000760'<tt>trunk</tt>'). The following releases are located in the following
Misha Brukman9474d012008-12-17 16:27:23 +0000761subdirectories of the '<tt>tags</tt>' directory:</p>
Misha Brukman54111c42004-01-20 00:20:17 +0000762
John Criswelld000e1d2003-12-18 16:43:17 +0000763<ul>
Bill Wendlingc3b94fb2011-04-04 23:42:51 +0000764<li>Release 2.9: <b>RELEASE_29/final</b></li>
Bill Wendlingc44c2452010-10-06 23:50:30 +0000765<li>Release 2.8: <b>RELEASE_28</b></li>
Tanya Lattner994526c2010-10-06 05:36:01 +0000766<li>Release 2.7: <b>RELEASE_27</b></li>
Tanya Lattnerf08803b2009-10-23 06:20:06 +0000767<li>Release 2.6: <b>RELEASE_26</b></li>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +0000768<li>Release 2.5: <b>RELEASE_25</b></li>
Misha Brukman9474d012008-12-17 16:27:23 +0000769<li>Release 2.4: <b>RELEASE_24</b></li>
Tanya Lattnerb37ef512008-06-09 06:02:09 +0000770<li>Release 2.3: <b>RELEASE_23</b></li>
Tanya Lattnerdd50f0f2008-02-12 02:42:55 +0000771<li>Release 2.2: <b>RELEASE_22</b></li>
Tanya Lattner76385652007-09-28 22:50:54 +0000772<li>Release 2.1: <b>RELEASE_21</b></li>
Tanya Lattner1dcadec2007-05-22 06:06:22 +0000773<li>Release 2.0: <b>RELEASE_20</b></li>
Tanya Lattner134693a2006-11-20 06:07:10 +0000774<li>Release 1.9: <b>RELEASE_19</b></li>
Tanya Lattnerf7b6be02006-11-20 06:04:46 +0000775<li>Release 1.8: <b>RELEASE_18</b></li>
Tanya Lattner993b9802006-04-20 04:35:34 +0000776<li>Release 1.7: <b>RELEASE_17</b></li>
John Criswellc0c186d2005-11-08 21:11:33 +0000777<li>Release 1.6: <b>RELEASE_16</b></li>
John Criswell75162552005-05-09 16:49:59 +0000778<li>Release 1.5: <b>RELEASE_15</b></li>
Reid Spencer66db92e2004-12-08 16:51:31 +0000779<li>Release 1.4: <b>RELEASE_14</b></li>
John Criswell18b74642004-08-16 14:51:33 +0000780<li>Release 1.3: <b>RELEASE_13</b></li>
Misha Brukmanb9be2bf2004-05-12 19:25:59 +0000781<li>Release 1.2: <b>RELEASE_12</b></li>
782<li>Release 1.1: <b>RELEASE_11</b></li>
783<li>Release 1.0: <b>RELEASE_1</b></li>
John Criswelld000e1d2003-12-18 16:43:17 +0000784</ul>
John Criswelld000e1d2003-12-18 16:43:17 +0000785
Reid Spencer66db92e2004-12-08 16:51:31 +0000786<p>If you would like to get the LLVM test suite (a separate package as of 1.4),
John Criswell9c29bfb2007-06-29 19:12:31 +0000787you get it from the Subversion repository:</p>
Bill Wendling77f74692007-07-16 08:44:39 +0000788
789<div class="doc_code">
Reid Spencer66db92e2004-12-08 16:51:31 +0000790<pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000791% cd llvm/projects
Andrew Trickbcf01162010-09-23 20:26:44 +0000792% svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
Reid Spencer66db92e2004-12-08 16:51:31 +0000793</pre>
Bill Wendling77f74692007-07-16 08:44:39 +0000794</div>
795
Reid Spencer66db92e2004-12-08 16:51:31 +0000796<p>By placing it in the <tt>llvm/projects</tt>, it will be automatically
John Criswellc4ef3f22004-12-08 16:55:27 +0000797configured by the LLVM configure script as well as automatically updated when
John Criswell9c29bfb2007-06-29 19:12:31 +0000798you run <tt>svn update</tt>.</p>
Reid Spencer66db92e2004-12-08 16:51:31 +0000799
Chris Lattner82ad9f12007-03-06 06:27:34 +0000800<p>If you would like to get the GCC front end source code, you can also get it
Duncan Sands8655b152008-02-14 17:53:22 +0000801and build it yourself. Please follow <a href="GCCFEBuildInstrs.html">these
Chris Lattner82ad9f12007-03-06 06:27:34 +0000802instructions</a> to successfully get and build the LLVM GCC front-end.</p>
Chris Lattner604fdc12004-06-28 17:14:01 +0000803
Misha Brukman00c73d22003-11-07 19:43:14 +0000804</div>
805
806<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000807<h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000808 <a name="git_mirror">GIT mirror</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000809</h3>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000810
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000811<div>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000812
813<p>GIT mirrors are available for a number of LLVM subprojects. These mirrors
814 sync automatically with each Subversion commit and contain all necessary
815 git-svn marks (so, you can recreate git-svn metadata locally). Note that right
816 now mirrors reflect only <tt>trunk</tt> for each project. You can do the
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +0000817 read-only GIT clone of LLVM via:</p>
818
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000819<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000820git clone http://llvm.org/git/llvm.git
821</pre>
822
823<p>If you want to check out clang too, run:</p>
824
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000825<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000826git clone http://llvm.org/git/llvm.git
827cd llvm/tools
828git clone http://llvm.org/git/clang.git
829</pre>
830
NAKAMURA Takumi7a362f42011-08-12 07:48:01 +0000831<p>
832Since the upstream repository is in Subversion, you should use
833<tt>&quot;git pull --rebase&quot;</tt>
834instead of <tt>&quot;git pull&quot;</tt> to avoid generating a non-linear
835history in your clone.
836To configure <tt>&quot;git pull&quot;</tt> to pass <tt>--rebase</tt> by default
837on the master branch, run the following command:
838</p>
839
840<pre class="doc_code">
841git config branch.master.rebase true
842</pre>
843
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000844<h4>Sending patches with Git</h4>
845<div>
846<p>
847Please read <a href="DeveloperPolicy.html#patches">Developer Policy</a>, too.
848</p>
849
850<p>
851Assume <tt>master</tt> points the upstream and <tt>mybranch</tt> points your
852working branch, and <tt>mybranch</tt> is rebased onto <tt>master</tt>.
853At first you may check sanity of whitespaces:
854</p>
855
856<pre class="doc_code">
857git diff --check master..mybranch
858</pre>
859
860<p>
861The easiest way to generate a patch is as below:
862</p>
863
864<pre class="doc_code">
865git diff master..mybranch &gt; /path/to/mybranch.diff
866</pre>
867
868<p>
869It is a little different from svn-generated diff. git-diff-generated diff has
870prefixes like <tt>a/</tt> and <tt>b/</tt>. Don't worry, most developers might
871know it could be accepted with <tt>patch -p1 -N</tt>.
872</p>
873
874<p>
875But you may generate patchset with git-format-patch. It generates
876by-each-commit patchset. To generate patch files to attach to your article:
877</p>
878
879<pre class="doc_code">
880git format-patch --no-attach master..mybranch -o /path/to/your/patchset
881</pre>
882
883<p>
884If you would like to send patches directly, you may use git-send-email or
885git-imap-send. Here is an example to generate the patchset in Gmail's [Drafts].
886</p>
887
888<pre class="doc_code">
889git format-patch --attach master..mybranch --stdout | git imap-send
890</pre>
891
892<p>
893Then, your .git/config should have [imap] sections.
894</p>
895
896<pre class="doc_code">
897[imap]
898 host = imaps://imap.gmail.com
899 user = <em>your.gmail.account</em>@gmail.com
900 pass = <em>himitsu!</em>
901 port = 993
902 sslverify = false
903; in English
904 folder = "[Gmail]/Drafts"
905; example for Japanese, "Modified UTF-7" encoded.
906 folder = "[Gmail]/&amp;Tgtm+DBN-"
NAKAMURA Takumi0dd4f102011-11-06 06:51:58 +0000907; example for Traditional Chinese
908 folder = "[Gmail]/&amp;g0l6Pw-"
NAKAMURA Takumi3c757ef2011-08-12 07:48:06 +0000909</pre>
910
911</div>
912
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000913<h4>For developers to work with git-svn</h4>
914<div>
915
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000916<p>To set up clone from which you can submit code using
917 <tt>git-svn</tt>, run:</p>
918
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000919<pre class="doc_code">
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000920git clone http://llvm.org/git/llvm.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000921cd llvm
922git svn init https://llvm.org/svn/llvm-project/llvm/trunk --username=&lt;username>
923git config svn-remote.svn.fetch :refs/remotes/origin/master
924git svn rebase -l # -l avoids fetching ahead of the git mirror.
925
926# If you have clang too:
927cd tools
NAKAMURA Takumi947431e2011-07-20 22:58:28 +0000928git clone http://llvm.org/git/clang.git
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000929cd clang
930git svn init https://llvm.org/svn/llvm-project/cfe/trunk --username=&lt;username>
931git config svn-remote.svn.fetch :refs/remotes/origin/master
932git svn rebase -l
933</pre>
934
935<p>To update this clone without generating git-svn tags that conflict
936with the upstream git repo, run:</p>
937
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000938<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000939git fetch && (cd tools/clang && git fetch) # Get matching revisions of both trees.
940git checkout master
941git svn rebase -l
942(cd tools/clang &&
943 git checkout master &&
944 git svn rebase -l)
945</pre>
946
947<p>This leaves your working directories on their master branches, so
948you'll need to <tt>checkout</tt> each working branch individually and
949<tt>rebase</tt> it on top of its parent branch. (Note: This script is
950intended for relative newbies to git. If you have more experience,
951you can likely improve on it.)</p>
952
953<p>The git-svn metadata can get out of sync after you mess around with
954branches and <code>dcommit</code>. When that happens, <code>git svn
955dcommit</code> stops working, complaining about files with uncommitted
956changes. The fix is to rebuild the metadata:</p>
957
NAKAMURA Takumie65b7ec2011-07-20 23:37:51 +0000958<pre class="doc_code">
Jeffrey Yasskin343c3a52011-07-19 00:20:54 +0000959rm -rf .git/svn
960git svn rebase -l
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000961</pre>
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000962
963</div>
964
NAKAMURA Takumi24ad1112011-08-12 07:47:55 +0000965</div>
966
Anton Korobeynikov46a98cf2011-02-01 20:08:28 +0000967<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000968<h3>
Misha Brukman54111c42004-01-20 00:20:17 +0000969 <a name="installcf">Install the GCC Front End</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +0000970</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +0000971
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +0000972<div>
Misha Brukman00c73d22003-11-07 19:43:14 +0000973
Jim Grosbach18df1d42009-12-17 17:18:11 +0000974<p>Before configuring and compiling the LLVM suite (or if you want to use just the LLVM
975GCC front end) you can optionally extract the front end from the binary distribution.
Andrew Trickbcf01162010-09-23 20:26:44 +0000976It is used for running the LLVM test-suite and for compiling C/C++ programs. Note that
Jim Grosbach18df1d42009-12-17 17:18:11 +0000977you can optionally <a href="GCCFEBuildInstrs.html">build llvm-gcc yourself</a> after building the
Chris Lattnerbcb38cf2007-02-14 07:33:00 +0000978main LLVM repository.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000979
Jim Grosbach18df1d42009-12-17 17:18:11 +0000980<p>To install the GCC front end, do the following (on Windows, use an archival tool
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000981like <a href="http://www.7-zip.org/">7-zip</a> that understands gzipped tars):</p>
Misha Brukman00c73d22003-11-07 19:43:14 +0000982
983<ol>
984 <li><tt>cd <i>where-you-want-the-front-end-to-live</i></tt></li>
Misha Brukmanccd02952008-12-29 19:38:58 +0000985 <li><tt>gunzip --stdout llvm-gcc-4.2-<i>version</i>-<i>platform</i>.tar.gz | tar -xvf
Misha Brukman00c73d22003-11-07 19:43:14 +0000986 -</tt></li>
987</ol>
988
Jim Grosbach18df1d42009-12-17 17:18:11 +0000989<p>Once the binary is uncompressed, if you're using a *nix-based system, add a symlink for
990<tt>llvm-gcc</tt> and <tt>llvm-g++</tt> to some directory in your path. If you're using a
991Windows-based system, add the <tt>bin</tt> subdirectory of your front end installation directory
992to your <tt>PATH</tt> environment variable. For example, if you uncompressed the binary to
993<tt>c:\llvm-gcc</tt>, add <tt>c:\llvm-gcc\bin</tt> to your <tt>PATH</tt>.</p>
994
995<p>If you now want to build LLVM from source, when you configure LLVM, it will
996automatically detect <tt>llvm-gcc</tt>'s presence (if it is in your path) enabling its
Andrew Trickbcf01162010-09-23 20:26:44 +0000997use in test-suite. Note that you can always build or install <tt>llvm-gcc</tt> at any
Jim Grosbach18df1d42009-12-17 17:18:11 +0000998point after building the main LLVM repository: just reconfigure llvm and
Andrew Trickbcf01162010-09-23 20:26:44 +0000999test-suite will pick it up.
Chris Lattnerbcb38cf2007-02-14 07:33:00 +00001000</p>
1001
Jim Grosbach18df1d42009-12-17 17:18:11 +00001002<p>As a convenience for Windows users, the front end binaries for MinGW/x86 include
1003versions of the required w32api and mingw-runtime binaries. The last remaining step for
1004Windows users is to simply uncompress the binary binutils package from
1005<a href="http://mingw.org/">MinGW</a> into your front end installation directory. While the
1006front end installation steps are not quite the same as a typical manual MinGW installation,
1007they should be similar enough to those who have previously installed MinGW on Windows systems.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001008
Jim Grosbach18df1d42009-12-17 17:18:11 +00001009<p>To install binutils on Windows:</p>
1010
1011<ol>
1012 <li><tt><i>download GNU Binutils from <a href="http://sourceforge.net/projects/mingw/files/">MinGW Downloads</a></i></tt></li>
1013 <li><tt>cd <i>where-you-uncompressed-the-front-end</i></tt></li>
1014 <li><tt><i>uncompress archived binutils directories (not the tar file) into the current directory</i></tt></li>
1015</ol>
1016
1017<p>The binary versions of the LLVM GCC front end may not suit all of your needs. For
1018example, the binary distribution may include an old version of a system header
1019file, not "fix" a header file that needs to be fixed for GCC, or it may be linked with
1020libraries not available on your system. In cases like these, you may want to try
1021<a href="GCCFEBuildInstrs.html">building the GCC front end from source</a>. Thankfully,
1022this is much easier now than it was in the past.</p>
1023
1024<p>We also do not currently support updating of the GCC front end by manually overlaying
1025newer versions of the w32api and mingw-runtime binary packages that may become available
1026from MinGW. At this time, it's best to think of the MinGW LLVM GCC front end binary as
1027a self-contained convenience package that requires Windows users to simply download and
1028uncompress the GNU Binutils binary package from the MinGW project.</p>
1029
1030<p>Regardless of your platform, if you discover that installing the LLVM GCC front end
1031binaries is not as easy as previously described, or you would like to suggest improvements,
1032please let us know how you would like to see things improved by dropping us a note on our
1033<a href="http://llvm.org/docs/#maillist">mailing list</a>.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001034
1035</div>
1036
1037<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001038<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001039 <a name="config">Local LLVM Configuration</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001040</h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001041
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001042<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001043
John Criswell9c29bfb2007-06-29 19:12:31 +00001044 <p>Once checked out from the Subversion repository, the LLVM suite source
1045 code must be
Reid Spencer66db92e2004-12-08 16:51:31 +00001046configured via the <tt>configure</tt> script. This script sets variables in the
1047various <tt>*.in</tt> files, most notably <tt>llvm/Makefile.config</tt> and
1048<tt>llvm/include/Config/config.h</tt>. It also populates <i>OBJ_ROOT</i> with
1049the Makefiles needed to begin building LLVM.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001050
1051<p>The following environment variables are used by the <tt>configure</tt>
1052script to configure the build system:</p>
1053
Chris Lattner9abd8af2006-09-07 04:19:09 +00001054<table summary="LLVM configure script environment variables">
Reid Spencerd3f876c2004-11-01 08:19:36 +00001055 <tr><th>Variable</th><th>Purpose</th></tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001056 <tr>
1057 <td>CC</td>
1058 <td>Tells <tt>configure</tt> which C compiler to use. By default,
1059 <tt>configure</tt> will look for the first GCC C compiler in
1060 <tt>PATH</tt>. Use this variable to override
1061 <tt>configure</tt>'s default behavior.</td>
1062 </tr>
Misha Brukman00c73d22003-11-07 19:43:14 +00001063 <tr>
1064 <td>CXX</td>
1065 <td>Tells <tt>configure</tt> which C++ compiler to use. By default,
1066 <tt>configure</tt> will look for the first GCC C++ compiler in
1067 <tt>PATH</tt>. Use this variable to override
1068 <tt>configure</tt>'s default behavior.</td>
1069 </tr>
1070</table>
1071
1072<p>The following options can be used to set or enable LLVM specific options:</p>
1073
Misha Brukman54111c42004-01-20 00:20:17 +00001074<dl>
Reid Spencerfef93b72004-12-26 05:47:26 +00001075 <dt><i>--with-llvmgccdir</i></dt>
1076 <dd>Path to the LLVM C/C++ FrontEnd to be used with this LLVM configuration.
1077 The value of this option should specify the full pathname of the C/C++ Front
1078 End to be used. If this option is not provided, the PATH will be searched for
1079 a program named <i>llvm-gcc</i> and the C/C++ FrontEnd install directory will
1080 be inferred from the path found. If the option is not given, and no llvm-gcc
1081 can be found in the path then a warning will be produced by
1082 <tt>configure</tt> indicating this situation. LLVM may still be built with
1083 the <tt>tools-only</tt> target but attempting to build the runtime libraries
1084 will fail as these libraries require llvm-gcc and llvm-g++. See
1085 <a href="#installcf">Install the GCC Front End</a> for details on installing
1086 the C/C++ Front End. See
Duncan Sands8655b152008-02-14 17:53:22 +00001087 <a href="GCCFEBuildInstrs.html">Bootstrapping the LLVM C/C++ Front-End</a>
Reid Spencerfef93b72004-12-26 05:47:26 +00001088 for details on building the C/C++ Front End.</dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001089 <dt><i>--with-tclinclude</i></dt>
John Criswell8bfe6a72005-05-18 19:43:33 +00001090 <dd>Path to the tcl include directory under which <tt>tclsh</tt> can be
Reid Spencer66db92e2004-12-08 16:51:31 +00001091 found. Use this if you have multiple tcl installations on your machine and you
1092 want to use a specific one (8.x) for LLVM. LLVM only uses tcl for running the
1093 dejagnu based test suite in <tt>llvm/test</tt>. If you don't specify this
John Criswell8bfe6a72005-05-18 19:43:33 +00001094 option, the LLVM configure script will search for the tcl 8.4 and 8.3
1095 releases.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001096 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001097 </dd>
1098 <dt><i>--enable-optimized</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001099 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001100 Enables optimized compilation (debugging symbols are removed
1101 and GCC optimization flags are enabled). Note that this is the default
1102 setting if you are using the LLVM distribution. The default behavior
1103 of an Subversion checkout is to use an unoptimized build (also known as a
1104 debug build).
Chris Lattner9abd8af2006-09-07 04:19:09 +00001105 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001106 </dd>
Reid Spencer9d57b4d2005-12-21 03:46:45 +00001107 <dt><i>--enable-debug-runtime</i></dt>
1108 <dd>
1109 Enables debug symbols in the runtime libraries. The default is to strip
1110 debug symbols from the runtime libraries.
1111 </dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001112 <dt><i>--enable-jit</i></dt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001113 <dd>
John Criswelld000e1d2003-12-18 16:43:17 +00001114 Compile the Just In Time (JIT) compiler functionality. This is not
1115 available
Misha Brukman00c73d22003-11-07 19:43:14 +00001116 on all platforms. The default is dependent on platform, so it is best
1117 to explicitly enable it if you want it.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001118 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001119 </dd>
Reid Spencer2dedcf52005-04-22 17:58:03 +00001120 <dt><i>--enable-targets=</i><tt>target-option</tt></dt>
1121 <dd>Controls which targets will be built and linked into llc. The default
1122 value for <tt>target_options</tt> is "all" which builds and links all
1123 available targets. The value "host-only" can be specified to build only a
1124 native compiler (no cross-compiler targets available). The "native" target is
1125 selected as the target of the build host. You can also specify a comma
1126 separated list of target names that you want available in llc. The target
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001127 names use all lower case. The current set of targets is: <br>
Jia Liu060047f2012-02-10 04:58:24 +00001128 <tt>arm, cbe, cpp, hexagon, mblaze, mips, mipsel, msp430, powerpc, ptx, sparc, spu, x86, x86_64, xcore</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001129 <br><br></dd>
Reid Spencer66db92e2004-12-08 16:51:31 +00001130 <dt><i>--enable-doxygen</i></dt>
1131 <dd>Look for the doxygen program and enable construction of doxygen based
1132 documentation from the source code. This is disabled by default because
1133 generating the documentation can take a long time and producess 100s of
1134 megabytes of output.</dd>
Anton Korobeynikov8cea37b2007-01-23 12:35:46 +00001135 <dt><i>--with-udis86</i></dt>
1136 <dd>LLVM can use external disassembler library for various purposes (now it's
1137 used only for examining code produced by JIT). This option will enable usage
1138 of <a href="http://udis86.sourceforge.net/">udis86</a> x86 (both 32 and 64
1139 bits) disassembler library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001140</dl>
1141
1142<p>To configure LLVM, follow these steps:</p>
1143
1144<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001145 <li><p>Change directory into the object root directory:</p>
John Criswell0f6d7c02003-10-27 18:18:16 +00001146
Bill Wendling77f74692007-07-16 08:44:39 +00001147 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
1148
1149 <li><p>Run the <tt>configure</tt> script located in the LLVM source
1150 tree:</p>
1151
1152 <div class="doc_code">
1153 <pre>% <i>SRC_ROOT</i>/configure --prefix=/install/path [other options]</pre>
1154 </div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001155</ol>
John Criswell85ed3612003-06-12 19:34:44 +00001156
Misha Brukman00c73d22003-11-07 19:43:14 +00001157</div>
John Criswell85ed3612003-06-12 19:34:44 +00001158
Misha Brukman00c73d22003-11-07 19:43:14 +00001159<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001160<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001161 <a name="compile">Compiling the LLVM Suite Source Code</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001162</h3>
John Criswell85ed3612003-06-12 19:34:44 +00001163
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001164<div>
John Criswell0b459202003-07-08 20:35:59 +00001165
Misha Brukman00c73d22003-11-07 19:43:14 +00001166<p>Once you have configured LLVM, you can build it. There are three types of
1167builds:</p>
John Criswell0b459202003-07-08 20:35:59 +00001168
Misha Brukman54111c42004-01-20 00:20:17 +00001169<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001170 <dt>Debug Builds
John Criswellce760f62003-07-03 16:01:38 +00001171 <dd>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001172 These builds are the default when one is using an Subversion checkout and
1173 types <tt>gmake</tt> (unless the <tt>--enable-optimized</tt> option was
1174 used during configuration). The build system will compile the tools and
1175 libraries with debugging information. To get a Debug Build using the
1176 LLVM distribution the <tt>--disable-optimized</tt> option must be passed
1177 to <tt>configure</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001178 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001179
1180 <dt>Release (Optimized) Builds
John Criswellce760f62003-07-03 16:01:38 +00001181 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001182 These builds are enabled with the <tt>--enable-optimized</tt> option to
1183 <tt>configure</tt> or by specifying <tt>ENABLE_OPTIMIZED=1</tt> on the
1184 <tt>gmake</tt> command line. For these builds, the build system will
1185 compile the tools and libraries with GCC optimizations enabled and strip
1186 debugging information from the libraries and executables it generates.
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001187 Note that Release Builds are default when using an LLVM distribution.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001188 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001189
1190 <dt>Profile Builds
John Criswellce760f62003-07-03 16:01:38 +00001191 <dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001192 These builds are for use with profiling. They compile profiling
1193 information into the code for use with programs like <tt>gprof</tt>.
1194 Profile builds must be started by specifying <tt>ENABLE_PROFILING=1</tt>
1195 on the <tt>gmake</tt> command line.
1196</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001197
Misha Brukman00c73d22003-11-07 19:43:14 +00001198<p>Once you have LLVM configured, you can build it by entering the
1199<i>OBJ_ROOT</i> directory and issuing the following command:</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001200
Bill Wendling77f74692007-07-16 08:44:39 +00001201<div class="doc_code"><pre>% gmake</pre></div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001202
Chris Lattner95e92582004-07-18 22:32:22 +00001203<p>If the build fails, please <a href="#brokengcc">check here</a> to see if you
John Criswell3d8ba512004-12-08 17:53:54 +00001204are using a version of GCC that is known not to compile LLVM.</p>
Chris Lattner95e92582004-07-18 22:32:22 +00001205
1206<p>
1207If you have multiple processors in your machine, you may wish to use some of
Misha Brukman00c73d22003-11-07 19:43:14 +00001208the parallel build options provided by GNU Make. For example, you could use the
1209command:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001210
Bill Wendling77f74692007-07-16 08:44:39 +00001211<div class="doc_code"><pre>% gmake -j2</pre></div>
John Criswellce760f62003-07-03 16:01:38 +00001212
Misha Brukman00c73d22003-11-07 19:43:14 +00001213<p>There are several special targets which are useful when working with the LLVM
1214source code:</p>
John Criswellce760f62003-07-03 16:01:38 +00001215
Misha Brukman54111c42004-01-20 00:20:17 +00001216<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001217 <dt><tt>gmake clean</tt>
1218 <dd>
1219 Removes all files generated by the build. This includes object files,
1220 generated C/C++ files, libraries, and executables.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001221 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001222
Reid Spencer66db92e2004-12-08 16:51:31 +00001223 <dt><tt>gmake dist-clean</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001224 <dd>
Misha Brukmanad38e962004-08-21 23:40:49 +00001225 Removes everything that <tt>gmake clean</tt> does, but also removes files
1226 generated by <tt>configure</tt>. It attempts to return the source tree to the
1227 original state in which it was shipped.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001228 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001229
Misha Brukmane51c3562004-08-23 20:25:33 +00001230 <dt><tt>gmake install</tt>
1231 <dd>
John Criswell3d8ba512004-12-08 17:53:54 +00001232 Installs LLVM header files, libraries, tools, and documentation in a
1233 hierarchy
Reid Spencer66db92e2004-12-08 16:51:31 +00001234 under $PREFIX, specified with <tt>./configure --prefix=[dir]</tt>, which
1235 defaults to <tt>/usr/local</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001236 <br><br>
1237
Reid Spencer66db92e2004-12-08 16:51:31 +00001238 <dt><tt>gmake -C runtime install-bytecode</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001239 <dd>
Reid Spencer7863c402004-11-11 07:30:27 +00001240 Assuming you built LLVM into $OBJDIR, when this command is run, it will
Gabor Greif04367bf2007-07-06 22:07:22 +00001241 install bitcode libraries into the GCC front end's bitcode library
1242 directory. If you need to update your bitcode libraries,
Misha Brukmanad38e962004-08-21 23:40:49 +00001243 this is the target to use once you've built them.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001244 <br><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001245</dl>
John Criswellce760f62003-07-03 16:01:38 +00001246
Reid Spencer66db92e2004-12-08 16:51:31 +00001247<p>Please see the <a href="MakefileGuide.html">Makefile Guide</a> for further
1248details on these <tt>make</tt> targets and descriptions of other targets
1249available.</p>
1250
Misha Brukman00c73d22003-11-07 19:43:14 +00001251<p>It is also possible to override default values from <tt>configure</tt> by
1252declaring variables on the command line. The following are some examples:</p>
John Criswellce760f62003-07-03 16:01:38 +00001253
Misha Brukman54111c42004-01-20 00:20:17 +00001254<dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001255 <dt><tt>gmake ENABLE_OPTIMIZED=1</tt>
1256 <dd>
1257 Perform a Release (Optimized) build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001258 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001259
Reid Spencer004ba032006-04-09 23:45:38 +00001260 <dt><tt>gmake ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1</tt>
Chris Lattnerd4651262006-03-21 01:10:57 +00001261 <dd>
Reid Spencer004ba032006-04-09 23:45:38 +00001262 Perform a Release (Optimized) build without assertions enabled.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001263 <br><br>
Chris Lattnerefdb3bc2009-04-25 22:24:49 +00001264
1265 <dt><tt>gmake ENABLE_OPTIMIZED=0</tt>
1266 <dd>
1267 Perform a Debug build.
1268 <br><br>
Chris Lattnerd4651262006-03-21 01:10:57 +00001269
Misha Brukman00c73d22003-11-07 19:43:14 +00001270 <dt><tt>gmake ENABLE_PROFILING=1</tt>
1271 <dd>
1272 Perform a Profiling build.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001273 <br><br>
John Criswellce760f62003-07-03 16:01:38 +00001274
Misha Brukman00c73d22003-11-07 19:43:14 +00001275 <dt><tt>gmake VERBOSE=1</tt>
1276 <dd>
1277 Print what <tt>gmake</tt> is doing on standard output.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001278 <br><br>
Reid Spencer66db92e2004-12-08 16:51:31 +00001279
1280 <dt><tt>gmake TOOL_VERBOSE=1</tt></dt>
1281 <dd>Ask each tool invoked by the makefiles to print out what it is doing on
John Criswell3d8ba512004-12-08 17:53:54 +00001282 the standard output. This also implies <tt>VERBOSE=1</tt>.
Chris Lattner9abd8af2006-09-07 04:19:09 +00001283 <br><br></dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001284</dl>
John Criswellce760f62003-07-03 16:01:38 +00001285
Misha Brukman00c73d22003-11-07 19:43:14 +00001286<p>Every directory in the LLVM object tree includes a <tt>Makefile</tt> to build
1287it and any subdirectories that it contains. Entering any directory inside the
1288LLVM object tree and typing <tt>gmake</tt> should rebuild anything in or below
1289that directory that is out of date.</p>
John Criswellce760f62003-07-03 16:01:38 +00001290
Misha Brukman00c73d22003-11-07 19:43:14 +00001291</div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001292
Misha Brukman00c73d22003-11-07 19:43:14 +00001293<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001294<h3>
Reid Spencerd30a9712006-07-27 06:41:31 +00001295 <a name="cross-compile">Cross-Compiling LLVM</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001296</h3>
Reid Spencer17850ef2006-07-27 05:43:30 +00001297
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001298<div>
Jim Grosbach5bea8222009-04-17 17:25:16 +00001299 <p>It is possible to cross-compile LLVM itself. That is, you can create LLVM
1300 executables and libraries to be hosted on a platform different from the
1301 platform where they are build (a Canadian Cross build). To configure a
1302 cross-compile, supply the configure script with <tt>--build</tt> and
1303 <tt>--host</tt> options that are different. The values of these options must
1304 be legal target triples that your GCC compiler supports.</p>
1305
1306 <p>The result of such a build is executables that are not runnable on
1307 on the build host (--build option) but can be executed on the compile host
Reid Spencerd30a9712006-07-27 06:41:31 +00001308 (--host option).</p>
Reid Spencer17850ef2006-07-27 05:43:30 +00001309</div>
1310
1311<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001312<h3>
Misha Brukman00c73d22003-11-07 19:43:14 +00001313 <a name="objfiles">The Location of LLVM Object Files</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001314</h3>
John Criswell20d2d3e2003-10-10 14:26:14 +00001315
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001316<div>
John Criswellce760f62003-07-03 16:01:38 +00001317
Misha Brukman00c73d22003-11-07 19:43:14 +00001318<p>The LLVM build system is capable of sharing a single LLVM source tree among
1319several LLVM builds. Hence, it is possible to build LLVM for several different
1320platforms or configurations using the same source tree.</p>
John Criswellce760f62003-07-03 16:01:38 +00001321
Misha Brukman00c73d22003-11-07 19:43:14 +00001322<p>This is accomplished in the typical autoconf manner:</p>
John Criswellce760f62003-07-03 16:01:38 +00001323
Misha Brukman00c73d22003-11-07 19:43:14 +00001324<ul>
1325 <li><p>Change directory to where the LLVM object files should live:</p>
John Criswellce760f62003-07-03 16:01:38 +00001326
Bill Wendling77f74692007-07-16 08:44:39 +00001327 <div class="doc_code"><pre>% cd <i>OBJ_ROOT</i></pre></div></li>
John Criswellce760f62003-07-03 16:01:38 +00001328
Misha Brukman00c73d22003-11-07 19:43:14 +00001329 <li><p>Run the <tt>configure</tt> script found in the LLVM source
1330 directory:</p>
John Criswellce760f62003-07-03 16:01:38 +00001331
Bill Wendling77f74692007-07-16 08:44:39 +00001332 <div class="doc_code"><pre>% <i>SRC_ROOT</i>/configure</pre></div></li>
Misha Brukman00c73d22003-11-07 19:43:14 +00001333</ul>
John Criswell85ed3612003-06-12 19:34:44 +00001334
Misha Brukman00c73d22003-11-07 19:43:14 +00001335<p>The LLVM build will place files underneath <i>OBJ_ROOT</i> in directories
1336named after the build type:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001337
Misha Brukman54111c42004-01-20 00:20:17 +00001338<dl>
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001339 <dt>Debug Builds with assertions enabled (the default)
Misha Brukman00c73d22003-11-07 19:43:14 +00001340 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001341 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001342 <dt>Tools
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001343 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001344 <dt>Libraries
Duncan Sands67f8a7b2010-07-08 08:27:18 +00001345 <dd><tt><i>OBJ_ROOT</i>/Debug+Asserts/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001346 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001347 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001348
Misha Brukman00c73d22003-11-07 19:43:14 +00001349 <dt>Release Builds
1350 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001351 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001352 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001353 <dd><tt><i>OBJ_ROOT</i>/Release/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001354 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001355 <dd><tt><i>OBJ_ROOT</i>/Release/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001356 </dl>
Chris Lattner9abd8af2006-09-07 04:19:09 +00001357 <br><br>
John Criswell85ed3612003-06-12 19:34:44 +00001358
Misha Brukman00c73d22003-11-07 19:43:14 +00001359 <dt>Profile Builds
1360 <dd>
Misha Brukman54111c42004-01-20 00:20:17 +00001361 <dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001362 <dt>Tools
Reid Spencer66db92e2004-12-08 16:51:31 +00001363 <dd><tt><i>OBJ_ROOT</i>/Profile/bin</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001364 <dt>Libraries
Reid Spencer66db92e2004-12-08 16:51:31 +00001365 <dd><tt><i>OBJ_ROOT</i>/Profile/lib</tt>
Misha Brukman00c73d22003-11-07 19:43:14 +00001366 </dl>
1367</dl>
John Criswell85ed3612003-06-12 19:34:44 +00001368
Misha Brukman00c73d22003-11-07 19:43:14 +00001369</div>
Chris Lattner7fe7f812002-07-24 19:51:14 +00001370
Chris Lattnera553f622004-03-25 20:38:40 +00001371<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001372<h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001373 <a name="optionalconfig">Optional Configuration Items</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001374</h3>
Chris Lattnera553f622004-03-25 20:38:40 +00001375
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001376<div>
Chris Lattnera553f622004-03-25 20:38:40 +00001377
1378<p>
Misha Brukman9106eca2005-02-03 22:25:23 +00001379If you're running on a Linux system that supports the "<a
Bill Wendling22e37c32007-07-16 08:46:40 +00001380href="http://www.tat.physik.uni-tuebingen.de/~rguenth/linux/binfmt_misc.html">binfmt_misc</a>"
Chris Lattnera553f622004-03-25 20:38:40 +00001381module, and you have root access on the system, you can set your system up to
Bill Wendling22e37c32007-07-16 08:46:40 +00001382execute LLVM bitcode files directly. To do this, use commands like this (the
Chris Lattnera553f622004-03-25 20:38:40 +00001383first command may not be required if you are already using the module):</p>
1384
Misha Brukman9106eca2005-02-03 22:25:23 +00001385<div class="doc_code">
Chris Lattnera553f622004-03-25 20:38:40 +00001386<pre>
Bill Wendling77f74692007-07-16 08:44:39 +00001387$ mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
Nick Lewyckye6b5a522009-11-04 06:15:28 +00001388$ echo ':llvm:M::BC::/path/to/lli:' &gt; /proc/sys/fs/binfmt_misc/register
Bill Wendling77f74692007-07-16 08:44:39 +00001389$ chmod u+x hello.bc (if needed)
1390$ ./hello.bc
Chris Lattnera553f622004-03-25 20:38:40 +00001391</pre>
Misha Brukman9106eca2005-02-03 22:25:23 +00001392</div>
Chris Lattnera553f622004-03-25 20:38:40 +00001393
1394<p>
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001395This allows you to execute LLVM bitcode files directly. On Debian, you
NAKAMURA Takumi4d6deb02011-04-09 09:51:57 +00001396can also use this command instead of the 'echo' command above:
Chris Lattnera553f622004-03-25 20:38:40 +00001397</p>
1398
Chris Lattner3bc3d3c2010-02-17 18:33:13 +00001399<div class="doc_code">
1400<pre>
1401$ sudo update-binfmts --install llvm /path/to/lli --magic 'BC'
1402</pre>
1403</div>
1404
Chris Lattnera553f622004-03-25 20:38:40 +00001405</div>
1406
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001407</div>
1408
Misha Brukman00c73d22003-11-07 19:43:14 +00001409<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001410<h2>
1411 <a name="layout">Program Layout</a>
1412</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001413<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001414
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001415<div>
John Criswell85ed3612003-06-12 19:34:44 +00001416
Misha Brukman00c73d22003-11-07 19:43:14 +00001417<p>One useful source of information about the LLVM source base is the LLVM <a
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001418href="http://www.doxygen.org/">doxygen</a> documentation available at <tt><a
Reid Spencer05fe4b02006-03-14 05:39:39 +00001419href="http://llvm.org/doxygen/">http://llvm.org/doxygen/</a></tt>.
Misha Brukman00c73d22003-11-07 19:43:14 +00001420The following is a brief introduction to code layout:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001421
Misha Brukman00c73d22003-11-07 19:43:14 +00001422<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001423<h3>
1424 <a name="examples"><tt>llvm/examples</tt></a>
1425</h3>
1426
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001427<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001428 <p>This directory contains some simple examples of how to use the LLVM IR and
1429 JIT.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001430</div>
John Criswell85ed3612003-06-12 19:34:44 +00001431
Misha Brukman00c73d22003-11-07 19:43:14 +00001432<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001433<h3>
1434 <a name="include"><tt>llvm/include</tt></a>
1435</h3>
1436
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001437<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001438
1439<p>This directory contains public header files exported from the LLVM
1440library. The three main subdirectories of this directory are:</p>
1441
Reid Spencer77d90192004-09-05 20:50:22 +00001442<dl>
1443 <dt><tt><b>llvm/include/llvm</b></tt></dt>
1444 <dd>This directory contains all of the LLVM specific header files. This
1445 directory also has subdirectories for different portions of LLVM:
1446 <tt>Analysis</tt>, <tt>CodeGen</tt>, <tt>Target</tt>, <tt>Transforms</tt>,
1447 etc...</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001448
Reid Spencer77d90192004-09-05 20:50:22 +00001449 <dt><tt><b>llvm/include/llvm/Support</b></tt></dt>
1450 <dd>This directory contains generic support libraries that are provided with
1451 LLVM but not necessarily specific to LLVM. For example, some C++ STL utilities
1452 and a Command Line option processing library store their header files here.
1453 </dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001454
Reid Spencer77d90192004-09-05 20:50:22 +00001455 <dt><tt><b>llvm/include/llvm/Config</b></tt></dt>
1456 <dd>This directory contains header files configured by the <tt>configure</tt>
1457 script. They wrap "standard" UNIX and C header files. Source code can
1458 include these header files which automatically take care of the conditional
1459 #includes that the <tt>configure</tt> script generates.</dd>
1460</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001461</div>
1462
1463<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001464<h3>
1465 <a name="lib"><tt>llvm/lib</tt></a>
1466</h3>
1467
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001468<div>
Misha Brukman00c73d22003-11-07 19:43:14 +00001469
1470<p>This directory contains most of the source files of the LLVM system. In LLVM,
1471almost all code exists in libraries, making it very easy to share code among the
1472different <a href="#tools">tools</a>.</p>
1473
Misha Brukman54111c42004-01-20 00:20:17 +00001474<dl>
Reid Spencer77d90192004-09-05 20:50:22 +00001475 <dt><tt><b>llvm/lib/VMCore/</b></tt></dt>
1476 <dd> This directory holds the core LLVM source files that implement core
1477 classes like Instruction and BasicBlock.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001478
Reid Spencer77d90192004-09-05 20:50:22 +00001479 <dt><tt><b>llvm/lib/AsmParser/</b></tt></dt>
1480 <dd>This directory holds the source code for the LLVM assembly language parser
1481 library.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001482
Gabor Greif04367bf2007-07-06 22:07:22 +00001483 <dt><tt><b>llvm/lib/BitCode/</b></tt></dt>
1484 <dd>This directory holds code for reading and write LLVM bitcode.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001485
Reid Spencer77d90192004-09-05 20:50:22 +00001486 <dt><tt><b>llvm/lib/Analysis/</b></tt><dd>This directory contains a variety of
Misha Brukman00c73d22003-11-07 19:43:14 +00001487 different program analyses, such as Dominator Information, Call Graphs,
1488 Induction Variables, Interval Identification, Natural Loop Identification,
Reid Spencer77d90192004-09-05 20:50:22 +00001489 etc.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001490
Reid Spencer77d90192004-09-05 20:50:22 +00001491 <dt><tt><b>llvm/lib/Transforms/</b></tt></dt>
1492 <dd> This directory contains the source code for the LLVM to LLVM program
1493 transformations, such as Aggressive Dead Code Elimination, Sparse Conditional
1494 Constant Propagation, Inlining, Loop Invariant Code Motion, Dead Global
1495 Elimination, and many others.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001496
Reid Spencer77d90192004-09-05 20:50:22 +00001497 <dt><tt><b>llvm/lib/Target/</b></tt></dt>
1498 <dd> This directory contains files that describe various target architectures
Chris Lattner2a607032006-04-20 17:42:23 +00001499 for code generation. For example, the <tt>llvm/lib/Target/X86</tt>
1500 directory holds the X86 machine description while
John Criswell8bfe6a72005-05-18 19:43:33 +00001501 <tt>llvm/lib/Target/CBackend</tt> implements the LLVM-to-C converter.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001502
Reid Spencer77d90192004-09-05 20:50:22 +00001503 <dt><tt><b>llvm/lib/CodeGen/</b></tt></dt>
1504 <dd> This directory contains the major parts of the code generator: Instruction
1505 Selector, Instruction Scheduling, and Register Allocation.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001506
NAKAMURA Takumia8b3e182011-04-05 08:24:15 +00001507 <dt><tt><b>llvm/lib/MC/</b></tt></dt>
1508 <dd>(FIXME: T.B.D.)</dd>
1509
1510 <!--FIXME: obsoleted -->
Reid Spencer77d90192004-09-05 20:50:22 +00001511 <dt><tt><b>llvm/lib/Debugger/</b></tt></dt>
1512 <dd> This directory contains the source level debugger library that makes
1513 it possible to instrument LLVM programs so that a debugger could identify
1514 source code locations at which the program is executing.</dd>
1515
1516 <dt><tt><b>llvm/lib/ExecutionEngine/</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001517 <dd> This directory contains libraries for executing LLVM bitcode directly
Reid Spencer77d90192004-09-05 20:50:22 +00001518 at runtime in both interpreted and JIT compiled fashions.</dd>
1519
1520 <dt><tt><b>llvm/lib/Support/</b></tt></dt>
Daniel Dunbar2c607b62011-10-11 20:02:52 +00001521 <dd> This directory contains the source code that corresponds to the header
1522 files located in <tt>llvm/include/ADT/</tt>
1523 and <tt>llvm/include/Support/</tt>.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001524</dl>
John Criswell7a73b802003-06-30 21:59:07 +00001525
Misha Brukman00c73d22003-11-07 19:43:14 +00001526</div>
John Criswell85ed3612003-06-12 19:34:44 +00001527
Misha Brukman00c73d22003-11-07 19:43:14 +00001528<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001529<h3>
1530 <a name="projects"><tt>llvm/projects</tt></a>
1531</h3>
1532
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001533<div>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001534 <p>This directory contains projects that are not strictly part of LLVM but are
1535 shipped with LLVM. This is also the directory where you should create your own
1536 LLVM-based projects. See <tt>llvm/projects/sample</tt> for an example of how
Chris Lattner4630e4d2008-08-11 06:13:31 +00001537 to set up your own project.</p>
Reid Spencerc4b09ba2004-12-08 16:18:26 +00001538</div>
1539
1540<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001541<h3>
1542 <a name="runtime"><tt>llvm/runtime</tt></a>
1543</h3>
1544
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001545<div>
John Criswell85ed3612003-06-12 19:34:44 +00001546
Gabor Greif04367bf2007-07-06 22:07:22 +00001547<p>This directory contains libraries which are compiled into LLVM bitcode and
Misha Brukman00c73d22003-11-07 19:43:14 +00001548used when linking programs with the GCC front end. Most of these libraries are
1549skeleton versions of real libraries; for example, libc is a stripped down
1550version of glibc.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001551
Misha Brukman00c73d22003-11-07 19:43:14 +00001552<p>Unlike the rest of the LLVM suite, this directory needs the LLVM GCC front
1553end to compile.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001554
Misha Brukman00c73d22003-11-07 19:43:14 +00001555</div>
John Criswell85ed3612003-06-12 19:34:44 +00001556
Misha Brukman00c73d22003-11-07 19:43:14 +00001557<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001558<h3>
1559 <a name="test"><tt>llvm/test</tt></a>
1560</h3>
1561
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001562<div>
Reid Spencer77d90192004-09-05 20:50:22 +00001563 <p>This directory contains feature and regression tests and other basic sanity
1564 checks on the LLVM infrastructure. These are intended to run quickly and cover
1565 a lot of territory without being exhaustive.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001566</div>
John Criswell85ed3612003-06-12 19:34:44 +00001567
Misha Brukman00c73d22003-11-07 19:43:14 +00001568<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001569<h3>
1570 <a name="test-suite"><tt>test-suite</tt></a>
1571</h3>
1572
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001573<div>
John Criswell9c29bfb2007-06-29 19:12:31 +00001574 <p>This is not a directory in the normal llvm module; it is a separate
1575 Subversion
1576 module that must be checked out (usually to <tt>projects/test-suite</tt>).
1577 This
John Criswell3d8ba512004-12-08 17:53:54 +00001578 module contains a comprehensive correctness, performance, and benchmarking
1579 test
John Criswell9c29bfb2007-06-29 19:12:31 +00001580 suite for LLVM. It is a separate Subversion module because not every LLVM
1581 user is
John Criswell838bce52005-05-09 16:39:27 +00001582 interested in downloading or building such a comprehensive test suite. For
1583 further details on this test suite, please see the
Reid Spencer77d90192004-09-05 20:50:22 +00001584 <a href="TestingGuide.html">Testing Guide</a> document.</p>
Misha Brukman00c73d22003-11-07 19:43:14 +00001585</div>
John Criswell85ed3612003-06-12 19:34:44 +00001586
Reid Spencer77d90192004-09-05 20:50:22 +00001587<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001588<h3>
1589 <a name="tools"><tt>llvm/tools</tt></a>
1590</h3>
1591
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001592<div>
John Criswell20d2d3e2003-10-10 14:26:14 +00001593
Misha Brukman00c73d22003-11-07 19:43:14 +00001594<p>The <b>tools</b> directory contains the executables built out of the
1595libraries above, which form the main part of the user interface. You can
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001596always get help for a tool by typing <tt>tool_name -help</tt>. The
Misha Brukmane12215f2004-11-15 23:20:51 +00001597following is a brief introduction to the most important tools. More detailed
1598information is in the <a href="CommandGuide/index.html">Command Guide</a>.</p>
John Criswell20d2d3e2003-10-10 14:26:14 +00001599
Misha Brukman54111c42004-01-20 00:20:17 +00001600<dl>
John Criswell85ed3612003-06-12 19:34:44 +00001601
Reid Spencer77d90192004-09-05 20:50:22 +00001602 <dt><tt><b>bugpoint</b></tt></dt>
1603 <dd><tt>bugpoint</tt> is used to debug
Misha Brukman00c73d22003-11-07 19:43:14 +00001604 optimization passes or code generation backends by narrowing down the
1605 given test case to the minimum number of passes and/or instructions that
1606 still cause a problem, whether it is a crash or miscompilation. See <a
1607 href="HowToSubmitABug.html">HowToSubmitABug.html</a> for more information
Reid Spencer77d90192004-09-05 20:50:22 +00001608 on using <tt>bugpoint</tt>.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001609
Reid Spencer77d90192004-09-05 20:50:22 +00001610 <dt><tt><b>llvm-ar</b></tt></dt>
1611 <dd>The archiver produces an archive containing
Gabor Greif04367bf2007-07-06 22:07:22 +00001612 the given LLVM bitcode files, optionally with an index for faster
Reid Spencer77d90192004-09-05 20:50:22 +00001613 lookup.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001614
Reid Spencer77d90192004-09-05 20:50:22 +00001615 <dt><tt><b>llvm-as</b></tt></dt>
1616 <dd>The assembler transforms the human readable LLVM assembly to LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001617 bitcode.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001618
Reid Spencer77d90192004-09-05 20:50:22 +00001619 <dt><tt><b>llvm-dis</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001620 <dd>The disassembler transforms the LLVM bitcode to human readable
Reid Spencer77d90192004-09-05 20:50:22 +00001621 LLVM assembly.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001622
Reid Spencer079e9452004-12-08 18:00:30 +00001623 <dt><tt><b>llvm-ld</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001624 <dd><tt>llvm-ld</tt> is a general purpose and extensible linker for LLVM.
Eric Christopher78d08352011-09-20 00:42:28 +00001625 It performs standard link time optimizations and allows optimization
1626 modules to be loaded and run so that language specific optimizations can
1627 be applied at link time.</dd>
Reid Spencer079e9452004-12-08 18:00:30 +00001628
Reid Spencer77d90192004-09-05 20:50:22 +00001629 <dt><tt><b>llvm-link</b></tt></dt>
1630 <dd><tt>llvm-link</tt>, not surprisingly, links multiple LLVM modules into
1631 a single program.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001632
Reid Spencer77d90192004-09-05 20:50:22 +00001633 <dt><tt><b>lli</b></tt></dt>
1634 <dd><tt>lli</tt> is the LLVM interpreter, which
Nick Lewycky64270d52007-12-03 01:58:01 +00001635 can directly execute LLVM bitcode (although very slowly...). For architectures
1636 that support it (currently x86, Sparc, and PowerPC), by default, <tt>lli</tt>
1637 will function as a Just-In-Time compiler (if the functionality was compiled
1638 in), and will execute the code <i>much</i> faster than the interpreter.</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001639
Reid Spencer77d90192004-09-05 20:50:22 +00001640 <dt><tt><b>llc</b></tt></dt>
1641 <dd> <tt>llc</tt> is the LLVM backend compiler, which
Gabor Greif04367bf2007-07-06 22:07:22 +00001642 translates LLVM bitcode to a native code assembly file or to C code (with
Reid Spencer77d90192004-09-05 20:50:22 +00001643 the -march=c option).</dd>
Misha Brukmanef0ad412003-10-06 19:23:34 +00001644
Reid Spencerd4694f92004-12-22 06:29:07 +00001645 <dt><tt><b>llvm-gcc</b></tt></dt>
Reid Spencer434262a2007-02-09 15:59:08 +00001646 <dd><tt>llvm-gcc</tt> is a GCC-based C frontend that has been retargeted to
1647 use LLVM as its backend instead of GCC's RTL backend. It can also emit LLVM
Gabor Greif04367bf2007-07-06 22:07:22 +00001648 bitcode or assembly (with the <tt>-emit-llvm</tt> option) instead of the
Reid Spencer434262a2007-02-09 15:59:08 +00001649 usual machine code output. It works just like any other GCC compiler,
1650 taking the typical <tt>-c, -S, -E, -o</tt> options that are typically used.
1651 Additionally, the the source code for <tt>llvm-gcc</tt> is available as a
John Criswell9c29bfb2007-06-29 19:12:31 +00001652 separate Subversion module.</dd>
John Criswell85ed3612003-06-12 19:34:44 +00001653
Reid Spencer77d90192004-09-05 20:50:22 +00001654 <dt><tt><b>opt</b></tt></dt>
Gabor Greif04367bf2007-07-06 22:07:22 +00001655 <dd><tt>opt</tt> reads LLVM bitcode, applies a series of LLVM to LLVM
Reid Spencer84f82f72006-08-28 00:34:19 +00001656 transformations (which are specified on the command line), and then outputs
Duncan Sands7e7ae5a2010-02-18 14:08:13 +00001657 the resultant bitcode. The '<tt>opt -help</tt>' command is a good way to
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001658 get a list of the program transformations available in LLVM.<br>
Reid Spencer84f82f72006-08-28 00:34:19 +00001659 <dd><tt>opt</tt> can also be used to run a specific analysis on an input
Gabor Greif04367bf2007-07-06 22:07:22 +00001660 LLVM bitcode file and print out the results. It is primarily useful for
Reid Spencer84f82f72006-08-28 00:34:19 +00001661 debugging analyses, or familiarizing yourself with what an analysis does.</dd>
Misha Brukman00c73d22003-11-07 19:43:14 +00001662</dl>
Misha Brukman00c73d22003-11-07 19:43:14 +00001663</div>
John Criswell85ed3612003-06-12 19:34:44 +00001664
Misha Brukman00c73d22003-11-07 19:43:14 +00001665<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001666<h3>
1667 <a name="utils"><tt>llvm/utils</tt></a>
1668</h3>
1669
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001670<div>
John Criswell85ed3612003-06-12 19:34:44 +00001671
Misha Brukman00c73d22003-11-07 19:43:14 +00001672<p>This directory contains utilities for working with LLVM source code, and some
1673of the utilities are actually required as part of the build process because they
1674are code generators for parts of LLVM infrastructure.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001675
Misha Brukman54111c42004-01-20 00:20:17 +00001676<dl>
Misha Brukman54111c42004-01-20 00:20:17 +00001677 <dt><tt><b>codegen-diff</b></tt> <dd><tt>codegen-diff</tt> is a script
Misha Brukman00c73d22003-11-07 19:43:14 +00001678 that finds differences between code that LLC generates and code that LLI
1679 generates. This is a useful tool if you are debugging one of them,
1680 assuming that the other generates correct output. For the full user
Chris Lattner9abd8af2006-09-07 04:19:09 +00001681 manual, run <tt>`perldoc codegen-diff'</tt>.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001682
Misha Brukman54111c42004-01-20 00:20:17 +00001683 <dt><tt><b>emacs/</b></tt> <dd>The <tt>emacs</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001684 syntax-highlighting files which will work with Emacs and XEmacs editors,
1685 providing syntax highlighting support for LLVM assembly files and TableGen
1686 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001687 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001688
Misha Brukman54111c42004-01-20 00:20:17 +00001689 <dt><tt><b>getsrcs.sh</b></tt> <dd>The <tt>getsrcs.sh</tt> script finds
Misha Brukman00c73d22003-11-07 19:43:14 +00001690 and outputs all non-generated source files, which is useful if one wishes
1691 to do a lot of development across directories and does not want to
1692 individually find each file. One way to use it is to run, for example:
1693 <tt>xemacs `utils/getsources.sh`</tt> from the top of your LLVM source
Chris Lattner9abd8af2006-09-07 04:19:09 +00001694 tree.<br><br>
1695
Reid Spencer77d90192004-09-05 20:50:22 +00001696 <dt><tt><b>llvmgrep</b></tt></dt>
1697 <dd>This little tool performs an "egrep -H -n" on each source file in LLVM and
1698 passes to it a regular expression provided on <tt>llvmgrep</tt>'s command
1699 line. This is a very efficient way of searching the source base for a
1700 particular regular expression.</dd>
1701
Misha Brukman54111c42004-01-20 00:20:17 +00001702 <dt><tt><b>makellvm</b></tt> <dd>The <tt>makellvm</tt> script compiles all
Misha Brukman00c73d22003-11-07 19:43:14 +00001703 files in the current directory and then compiles and links the tool that
1704 is the first argument. For example, assuming you are in the directory
1705 <tt>llvm/lib/Target/Sparc</tt>, if <tt>makellvm</tt> is in your path,
1706 simply running <tt>makellvm llc</tt> will make a build of the current
1707 directory, switch to directory <tt>llvm/tools/llc</tt> and build it,
Chris Lattner9abd8af2006-09-07 04:19:09 +00001708 causing a re-linking of LLC.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001709
Misha Brukman54111c42004-01-20 00:20:17 +00001710 <dt><tt><b>TableGen/</b></tt> <dd>The <tt>TableGen</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001711 the tool used to generate register descriptions, instruction set
1712 descriptions, and even assemblers from common TableGen description
Chris Lattner9abd8af2006-09-07 04:19:09 +00001713 files.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001714
Misha Brukman54111c42004-01-20 00:20:17 +00001715 <dt><tt><b>vim/</b></tt> <dd>The <tt>vim</tt> directory contains
Misha Brukman00c73d22003-11-07 19:43:14 +00001716 syntax-highlighting files which will work with the VIM editor, providing
1717 syntax highlighting support for LLVM assembly files and TableGen
1718 description files. For information on how to use the syntax files, consult
Chris Lattner9abd8af2006-09-07 04:19:09 +00001719 the <tt>README</tt> file in that directory.<br><br>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001720
Misha Brukman00c73d22003-11-07 19:43:14 +00001721</dl>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001722
Misha Brukman00c73d22003-11-07 19:43:14 +00001723</div>
Misha Brukmanc103adf2003-08-11 18:45:46 +00001724
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001725</div>
1726
Misha Brukman00c73d22003-11-07 19:43:14 +00001727<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001728<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001729 <a name="tutorial">An Example Using the LLVM Tool Chain</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001730</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001731<!-- *********************************************************************** -->
Misha Brukmanc103adf2003-08-11 18:45:46 +00001732
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001733<div>
Chad Rosier372b8222012-02-26 21:31:25 +00001734<p>This section gives an example of using LLVM with the Clang front end.</p>
Chris Lattner5907d402006-08-14 20:45:25 +00001735
1736<!-- ======================================================================= -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001737<h3>
Chad Rosier372b8222012-02-26 21:31:25 +00001738 <a name="tutorial4">Example with clang</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001739</h3>
Chris Lattner5907d402006-08-14 20:45:25 +00001740
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001741<div>
Chris Lattner5907d402006-08-14 20:45:25 +00001742
1743<ol>
Bill Wendling77f74692007-07-16 08:44:39 +00001744 <li><p>First, create a simple C file, name it 'hello.c':</p>
1745
1746<div class="doc_code">
1747<pre>
1748#include &lt;stdio.h&gt;
1749
1750int main() {
1751 printf("hello world\n");
1752 return 0;
1753}
1754</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001755
1756 <li><p>Next, compile the C file into a native executable:</p>
1757
Chad Rosier372b8222012-02-26 21:31:25 +00001758 <div class="doc_code"><pre>% clang hello.c -o hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001759
Chad Rosier372b8222012-02-26 21:31:25 +00001760 <p>Note that clang works just like GCC by default. The standard -S and
Chris Lattner5907d402006-08-14 20:45:25 +00001761 -c arguments work as usual (producing a native .s or .o file,
Bill Wendling77f74692007-07-16 08:44:39 +00001762 respectively).</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001763
Gabor Greif04367bf2007-07-06 22:07:22 +00001764 <li><p>Next, compile the C file into a LLVM bitcode file:</p>
Bill Wendling77f74692007-07-16 08:44:39 +00001765
1766 <div class="doc_code">
Chad Rosier372b8222012-02-26 21:31:25 +00001767 <pre>% clang -O3 -emit-llvm hello.c -c -o hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001768
1769 <p>The -emit-llvm option can be used with the -S or -c options to emit an
1770 LLVM ".ll" or ".bc" file (respectively) for the code. This allows you
1771 to use the <a href="CommandGuide/index.html">standard LLVM tools</a> on
Chad Rosier372b8222012-02-26 21:31:25 +00001772 the bitcode file.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001773
1774 <li><p>Run the program in both forms. To run the program, use:</p>
1775
Bill Wendling77f74692007-07-16 08:44:39 +00001776 <div class="doc_code"><pre>% ./hello</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001777
1778 <p>and</p>
1779
Bill Wendling77f74692007-07-16 08:44:39 +00001780 <div class="doc_code"><pre>% lli hello.bc</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001781
1782 <p>The second examples shows how to invoke the LLVM JIT, <a
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001783 href="CommandGuide/html/lli.html">lli</a>.</p></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001784
1785 <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
1786 code:</p>
1787
Bill Wendling77f74692007-07-16 08:44:39 +00001788<div class="doc_code">
1789<pre>llvm-dis &lt; hello.bc | less</pre>
1790</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001791
1792 <li><p>Compile the program to native assembly using the LLC code
1793 generator:</p>
1794
Bill Wendling77f74692007-07-16 08:44:39 +00001795 <div class="doc_code"><pre>% llc hello.bc -o hello.s</pre></div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001796
1797 <li><p>Assemble the native assembly language file into a program:</p>
1798
Bill Wendling77f74692007-07-16 08:44:39 +00001799<div class="doc_code">
1800<pre>
1801<b>Solaris:</b> % /opt/SUNWspro/bin/cc -xarch=v9 hello.s -o hello.native
1802
1803<b>Others:</b> % gcc hello.s -o hello.native
1804</pre>
1805</div></li>
Chris Lattner5907d402006-08-14 20:45:25 +00001806
1807 <li><p>Execute the native code program:</p>
1808
Bill Wendling77f74692007-07-16 08:44:39 +00001809 <div class="doc_code"><pre>% ./hello.native</pre></div>
Chris Lattner5907d402006-08-14 20:45:25 +00001810
Chad Rosier372b8222012-02-26 21:31:25 +00001811 <p>Note that using clang to compile directly to native code (i.e. when
Chris Lattner5907d402006-08-14 20:45:25 +00001812 the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
Chris Lattner6e3b7c22006-08-14 20:51:35 +00001813 </li>
Chris Lattner5907d402006-08-14 20:45:25 +00001814
1815</ol>
1816
1817</div>
1818
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001819</div>
John Criswell85ed3612003-06-12 19:34:44 +00001820
Misha Brukman00c73d22003-11-07 19:43:14 +00001821<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001822<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001823 <a name="problems">Common Problems</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001824</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001825<!-- *********************************************************************** -->
John Criswellce760f62003-07-03 16:01:38 +00001826
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001827<div>
John Criswellce760f62003-07-03 16:01:38 +00001828
Misha Brukman00c73d22003-11-07 19:43:14 +00001829<p>If you are having problems building or using LLVM, or if you have any other
1830general questions about LLVM, please consult the <a href="FAQ.html">Frequently
1831Asked Questions</a> page.</p>
John Criswell85ed3612003-06-12 19:34:44 +00001832
Misha Brukman00c73d22003-11-07 19:43:14 +00001833</div>
John Criswell85ed3612003-06-12 19:34:44 +00001834
Misha Brukman00c73d22003-11-07 19:43:14 +00001835<!-- *********************************************************************** -->
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001836<h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001837 <a name="links">Links</a>
NAKAMURA Takumi05d02652011-04-18 23:59:50 +00001838</h2>
Misha Brukman00c73d22003-11-07 19:43:14 +00001839<!-- *********************************************************************** -->
John Criswell85ed3612003-06-12 19:34:44 +00001840
NAKAMURA Takumif5af6ad2011-04-23 00:30:22 +00001841<div>
John Criswell85ed3612003-06-12 19:34:44 +00001842
Bill Wendling2d4c2152008-07-22 01:10:25 +00001843<p>This document is just an <b>introduction</b> on how to use LLVM to do
Misha Brukman00c73d22003-11-07 19:43:14 +00001844some simple things... there are many more interesting and complicated things
1845that you can do that aren't documented here (but we'll gladly accept a patch
1846if you want to write something up!). For more information about LLVM, check
1847out:</p>
John Criswell85ed3612003-06-12 19:34:44 +00001848
Misha Brukman00c73d22003-11-07 19:43:14 +00001849<ul>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001850 <li><a href="http://llvm.org/">LLVM homepage</a></li>
1851 <li><a href="http://llvm.org/doxygen/">LLVM doxygen tree</a></li>
1852 <li><a href="http://llvm.org/docs/Projects.html">Starting a Project
Misha Brukman00c73d22003-11-07 19:43:14 +00001853 that Uses LLVM</a></li>
1854</ul>
1855
1856</div>
1857
1858<!-- *********************************************************************** -->
1859
1860<hr>
Misha Brukman142207b2003-11-22 01:30:01 +00001861<address>
Misha Brukman54111c42004-01-20 00:20:17 +00001862 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001863 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001864 <a href="http://validator.w3.org/check/referer"><img
Misha Brukmanf00ddb02008-12-11 18:23:24 +00001865 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman54111c42004-01-20 00:20:17 +00001866
Misha Brukman142207b2003-11-22 01:30:01 +00001867 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer77d90192004-09-05 20:50:22 +00001868 <a href="http://llvm.x10sys.com/rspencer/">Reid Spencer</a><br>
NAKAMURA Takumib9a33632011-04-09 02:13:37 +00001869 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
Misha Brukman00c73d22003-11-07 19:43:14 +00001870 Last modified: $Date$
Misha Brukman142207b2003-11-22 01:30:01 +00001871</address>
Misha Brukman00c73d22003-11-07 19:43:14 +00001872</body>
Guochun Shif4688a82002-07-17 23:05:56 +00001873</html>