Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / c97507ba8dde7b8d6ee38414e7faa05337954b91 / . / docs / ReleaseNotes.html
blob: b6ae1136439a0c3919a1fa82a2ed0ddd3976d705 [file] [log] [blame]
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css">
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]7 <title>LLVM 2.5 Release Notes</title>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]8</head>
9<body>
10
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]11<div class="doc_title">LLVM 2.5 Release Notes</div>
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]12
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]13<ol>
14 <li><a href="#intro">Introduction</a></li>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]15 <li><a href="#subproj">Sub-project Status Update</a></li>
16 <li><a href="#whatsnew">What's New in LLVM?</a></li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]17 <li><a href="GettingStarted.html">Installation Instructions</a></li>
18 <li><a href="#portability">Portability and Supported Platforms</a></li>
Dan Gohman0de549c2008-10-14 16:23:02 +0000[diff] [blame]19 <li><a href="#knownproblems">Known Problems</a></li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]20 <li><a href="#additionalinfo">Additional Information</a></li>
21</ol>
22
23<div class="doc_author">
Dan Gohman0de549c2008-10-14 16:23:02 +0000[diff] [blame]24 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]25</div>
26
27<!-- *********************************************************************** -->
28<div class="doc_section">
29 <a name="intro">Introduction</a>
30</div>
31<!-- *********************************************************************** -->
32
33<div class="doc_text">
34
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]35<p>This document contains the release notes for the LLVM Compiler
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]36Infrastructure, release 2.5. Here we describe the status of LLVM, including
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]37major improvements from the previous release and significant known problems.
38All LLVM releases may be downloaded from the <a
39href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]40
41<p>For more information about LLVM, including information about the latest
42release, please check out the <a href="http://llvm.org/">main LLVM
43web site</a>. If you have questions or comments, the <a
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]44href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's Mailing
45List</a> is a good place to send them.</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]46
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]47<p>Note that if you are reading this file from a Subversion checkout or the
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]48main LLVM web page, this document applies to the <i>next</i> release, not the
Gabor Greif7c65c4f2008-10-14 11:00:32 +0000[diff] [blame]49current one. To see the release notes for a specific release, please see the
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]50<a href="http://llvm.org/releases/">releases page</a>.</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]51
52</div>
53
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]54<!-- Unfinished features in 2.5:
Chris Lattner8fda4952008-02-10 07:46:44 +0000[diff] [blame]55 Machine LICM
56 Machine Sinking
57 LegalizeDAGTypes
Chris Lattner4f076402008-10-12 19:47:48 +0000[diff] [blame]58 llc -enable-value-prop, propagation of value info (sign/zero ext info) from
59 one MBB to another
Chris Lattner8fda4952008-02-10 07:46:44 +0000[diff] [blame]60 -->
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]61
Chris Lattner4f076402008-10-12 19:47:48 +0000[diff] [blame]62 <!-- for announcement email:
63 mention dev mtg
Chris Lattner548493b2008-10-12 22:57:58 +0000[diff] [blame]64 Xcode 3.1 and 3.1.1.
Chris Lattner4f076402008-10-12 19:47:48 +0000[diff] [blame]65 -->
Chris Lattner8fda4952008-02-10 07:46:44 +0000[diff] [blame]66
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]67<!-- *********************************************************************** -->
68<div class="doc_section">
69 <a name="subproj">Sub-project Status Update</a>
Chris Lattnerf65224f2008-06-08 21:34:41 +0000[diff] [blame]70</div>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]71<!-- *********************************************************************** -->
Chris Lattnerf65224f2008-06-08 21:34:41 +0000[diff] [blame]72
73<div class="doc_text">
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]74<p>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]75The LLVM 2.5 distribution currently consists of code from the core LLVM
Chris Lattnera3c683b2008-10-13 18:11:54 +0000[diff] [blame]76repository (which roughly includes the LLVM optimizers, code generators and
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]77supporting tools) and the llvm-gcc repository. In addition to this code, the
78LLVM Project includes other sub-projects that are in development. The two which
Chris Lattner2c3ef982008-10-11 18:18:28 +0000[diff] [blame]79are the most actively developed are the <a href="#clang">Clang Project</a> and
Nicolas Geoffray2b139382008-10-14 19:23:04 +0000[diff] [blame]80the <a href="#vmkit">VMKit Project</a>.
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]81</p>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]82
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]83</div>
84
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]85
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]86<!--=========================================================================-->
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]87<div class="doc_subsection">
Chris Lattnera3c683b2008-10-13 18:11:54 +0000[diff] [blame]88<a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]89</div>
90
91<div class="doc_text">
92
93<p>The <a href="http://clang.llvm.org/">Clang project</a> is an effort to build
94a set of new 'LLVM native' front-end technologies for the LLVM optimizer
Chris Lattnerc97507b2009-02-25 05:09:54 +0000[diff] [blame^]95and code generator. While Clang is not included in the LLVM 2.5 release, it
96is continuing to make major strides forward in all areas. Its C and Objective-C
97parsing and code generation support is now very solid. For example, it is
98capable of successfully building many real applications for X86-32 and X86-64,
99including the FreeBSD kernel. C++ is also making <a
100href="http://clang.llvm.org/cxx_status.html">incredible progress</a>, and work
101on templates has recently started.</p>
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]102
Chris Lattnerc97507b2009-02-25 05:09:54 +0000[diff] [blame^]103<p>While Clang is not yet production quality, it is progressing very nicely and
104is quite usable for building many C and Objective-C applications. If you are
105interested in fast compiles and good diagnostics, we encourage you to try it out
106by <a href="http://clang.llvm.org/get_started.html">building from mainlnie</a>
107and reporting any issues you hit to the <a
108href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">Clang front-end mailing
109list</a>.</p>
110
111<p>In the LLVM 2.5 time-frame, the Clang team has made many improvements:</p>
Bill Wendling385b0d32008-10-27 09:27:33 +0000[diff] [blame]112
Daniel Dunbarf3e35782008-10-14 23:25:09 +0000[diff] [blame]113<ul>
Chris Lattnerc97507b2009-02-25 05:09:54 +0000[diff] [blame^]114<li>Clang now has a new driver, which is focused on providing a GCC-compatible
115 interface.</li>
116<li>The X86-64 ABI is now supported.</li>
117<li>Precompiled header support is now implemented.</li>
118<li>Objective-C support is significantly improved beyond LLVM 2.4, supporting
119 many features, such as Objective-C Garbage Collection.</li>
120<li>Many many bugs are fixed.</li>
Chris Lattnera3c683b2008-10-13 18:11:54 +0000[diff] [blame]121</div>
122
123<!--=========================================================================-->
124<div class="doc_subsection">
125<a name="clangsa">Clang Static Analyzer</a>
126</div>
127
128<div class="doc_text">
129
Ted Kremenek0437b2c2008-10-14 05:14:21 +0000[diff] [blame]130<p>The Clang project also includes an early stage static source code analysis
131tool for <a href="http://clang.llvm.org/StaticAnalysis.html">automatically
132finding bugs</a> in C and Objective-C programs. The tool performs a growing set
Chris Lattnerff170152008-10-14 06:02:29 +0000[diff] [blame]133of checks to find bugs that occur on a specific path within a program. Examples
Ted Kremenek0437b2c2008-10-14 05:14:21 +0000[diff] [blame]134of bugs the tool finds include logic errors such as null dereferences,
135violations of various API rules, dead code, and potential memory leaks in
Chris Lattnerff170152008-10-14 06:02:29 +0000[diff] [blame]136Objective-C programs. Since its inception, public feedback on the tool has been
137extremely positive, and conservative estimates put the number of real bugs it
138has found in industrial-quality software on the order of thousands.</p>
Chris Lattnerc2d84672008-10-14 00:52:49 +0000[diff] [blame]139
Ted Kremenek0437b2c2008-10-14 05:14:21 +0000[diff] [blame]140<p>The tool also provides a simple web GUI to inspect potential bugs found by
Chris Lattnerff170152008-10-14 06:02:29 +0000[diff] [blame]141the tool. While still early in development, the GUI illustrates some of the key
Ted Kremenek0437b2c2008-10-14 05:14:21 +0000[diff] [blame]142features of Clang: accurate source location information, which is used by the
143GUI to highlight specific code expressions that relate to a bug (including those
Bill Wendling385b0d32008-10-27 09:27:33 +0000[diff] [blame]144that span multiple lines); and built-in knowledge of macros, which is used to
Ted Kremenek0437b2c2008-10-14 05:14:21 +0000[diff] [blame]145perform inline expansion of macros within the GUI itself.</p>
146
Chris Lattnerff170152008-10-14 06:02:29 +0000[diff] [blame]147<p>The set of checks performed by the static analyzer is gradually expanding,
Bill Wendling385b0d32008-10-27 09:27:33 +0000[diff] [blame]148and future plans for the tool include full source-level inter-procedural
149analysis and deeper checks such as buffer overrun detection. There are many
150opportunities to extend and enhance the static analyzer, and anyone interested
151in working on this project is encouraged to get involved!</p>
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]152
153</div>
154
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]155<!--=========================================================================-->
156<div class="doc_subsection">
Nicolas Geoffray2b139382008-10-14 19:23:04 +0000[diff] [blame]157<a name="vmkit">VMKit: JVM/CLI Virtual Machine Implementation</a>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]158</div>
159
160<div class="doc_text">
161<p>
Nicolas Geoffray2b139382008-10-14 19:23:04 +0000[diff] [blame]162The <a href="http://vmkit.llvm.org/">VMKit project</a> is an implementation of
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]163a JVM and a CLI Virtual Machines (Microsoft .NET is an
164implementation of the CLI) using the Just-In-Time compiler of LLVM.</p>
165
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]166<p>Following LLVM 2.5, VMKit has its first release 0.24 that you can find on its
Nicolas Geoffray20cfdd42008-10-15 20:25:04 +0000[diff] [blame]167<a href="http://vmkit.llvm.org/releases/">webpage</a>. The release includes
168bug fixes, cleanup and new features. The major changes are:</p>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]169
Nicolas Geoffray2b139382008-10-14 19:23:04 +0000[diff] [blame]170<ul>
171
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]172<li>?</li>
Nicolas Geoffray2b139382008-10-14 19:23:04 +0000[diff] [blame]173
174</ul>
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]175</div>
176
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]177
178<!-- *********************************************************************** -->
179<div class="doc_section">
Chris Lattner78a130b2008-10-13 18:01:01 +0000[diff] [blame]180 <a name="whatsnew">What's New in LLVM?</a>
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]181</div>
182<!-- *********************************************************************** -->
183
Chris Lattner5cce7a52008-06-08 22:59:35 +0000[diff] [blame]184<div class="doc_text">
185
Bill Wendling385b0d32008-10-27 09:27:33 +0000[diff] [blame]186<p>This release includes a huge number of bug fixes, performance tweaks, and
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]187minor improvements. Some of the major improvements and new features are listed
188in this section.
Chris Lattner5cce7a52008-06-08 22:59:35 +0000[diff] [blame]189</p>
190</div>
191
Chris Lattnerf6a0d382008-06-08 21:58:17 +0000[diff] [blame]192<!--=========================================================================-->
Chris Lattnerf65224f2008-06-08 21:34:41 +0000[diff] [blame]193<div class="doc_subsection">
Chris Lattnere0798082008-02-06 18:00:06 +0000[diff] [blame]194<a name="majorfeatures">Major New Features</a>
195</div>
196
197<div class="doc_text">
198
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]199<p>LLVM 2.5 includes several major new capabilities:</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]200
201<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]202<li><p>?</p></li>
Chris Lattnerba948522008-06-05 06:57:39 +0000[diff] [blame]203
Chris Lattner5ba16862008-02-10 08:18:42 +0000[diff] [blame]204</ul>
205
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]206</div>
207
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]208
209<!--=========================================================================-->
210<div class="doc_subsection">
Chris Lattnerf65224f2008-06-08 21:34:41 +0000[diff] [blame]211<a name="llvm-gcc">llvm-gcc 4.2 Improvements</a>
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]212</div>
213
214<div class="doc_text">
215
Chris Lattner4352cc82008-10-13 20:47:20 +0000[diff] [blame]216<p>LLVM fully supports the llvm-gcc 4.2 front-end, which marries the GCC
217front-ends and driver with the LLVM optimizer and code generator. It currently
218includes support for the C, C++, Objective-C, Ada, and Fortran front-ends.</p>
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]219
Chris Lattner5cce7a52008-06-08 22:59:35 +0000[diff] [blame]220<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]221<li>?</li>
Gabor Greif0e49cc82008-06-09 06:06:18 +0000[diff] [blame]222</ul>
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]223
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]224</div>
225
226
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]227<!--=========================================================================-->
228<div class="doc_subsection">
Chris Lattnerc3649452008-02-10 08:17:19 +0000[diff] [blame]229<a name="coreimprovements">LLVM Core Improvements</a>
230</div>
231
232<div class="doc_text">
Bill Wendling385b0d32008-10-27 09:27:33 +0000[diff] [blame]233<p>New features include:</p>
Chris Lattnerc3649452008-02-10 08:17:19 +0000[diff] [blame]234
Chris Lattnerc5a4e312008-06-05 06:25:56 +0000[diff] [blame]235<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]236<li>?</li>
Chris Lattnerf7bae6d2008-10-13 20:59:32 +0000[diff] [blame]237
Chris Lattnerc3649452008-02-10 08:17:19 +0000[diff] [blame]238</ul>
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]239
Chris Lattnerc3649452008-02-10 08:17:19 +0000[diff] [blame]240</div>
241
242<!--=========================================================================-->
243<div class="doc_subsection">
Chris Lattner8fda4952008-02-10 07:46:44 +0000[diff] [blame]244<a name="optimizer">Optimizer Improvements</a>
245</div>
246
247<div class="doc_text">
248
Chris Lattnerea9c2242008-10-13 21:50:36 +0000[diff] [blame]249<p>In addition to a huge array of bug fixes and minor performance tweaks, this
250release includes a few major enhancements and additions to the optimizers:</p>
Chris Lattner8fda4952008-02-10 07:46:44 +0000[diff] [blame]251
252<ul>
253
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]254<li>?</li>
Chris Lattnerea9c2242008-10-13 21:50:36 +0000[diff] [blame]255
Chris Lattner0eef6e42008-06-08 02:45:07 +0000[diff] [blame]256</ul>
257
258</div>
259
260<!--=========================================================================-->
261<div class="doc_subsection">
262<a name="codegen">Code Generator Improvements</a>
263</div>
264
265<div class="doc_text">
266
Gabor Greifaa53e562008-10-14 11:31:14 +0000[diff] [blame]267<p>We have put a significant amount of work into the code generator infrastructure,
Chris Lattner0eef6e42008-06-08 02:45:07 +0000[diff] [blame]268which allows us to implement more aggressive algorithms and make it run
269faster:</p>
270
271<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]272<li>?</li>
Chris Lattner0eef6e42008-06-08 02:45:07 +0000[diff] [blame]273
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]274</ul>
275
276</div>
277
278
279<!--=========================================================================-->
280<div class="doc_subsection">
Chris Lattnercc64a322008-10-13 22:06:31 +0000[diff] [blame]281<a name="targetspecific">Target Specific Improvements</a>
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]282</div>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]283
284<div class="doc_text">
Chris Lattnerc3649452008-02-10 08:17:19 +0000[diff] [blame]285<p>New target-specific features include:
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]286</p>
287
288<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]289<li>?</li>
Chris Lattnere45f18b2008-06-05 08:02:49 +0000[diff] [blame]290</ul>
Chris Lattnere45f18b2008-06-05 08:02:49 +0000[diff] [blame]291
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]292</div>
Chris Lattnere45f18b2008-06-05 08:02:49 +0000[diff] [blame]293
294
295<!--=========================================================================-->
296<div class="doc_subsection">
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]297<a name="otherimprovements">Other Improvements</a>
298</div>
299
300<div class="doc_text">
301<p>New features include:
302</p>
303
304<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]305<li>?</li>
Tanya Lattnerc79f7542008-11-04 18:40:27 +0000[diff] [blame]306
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]307</ul>
Mikhail Glushenkov808cd3e2008-10-13 02:08:34 +0000[diff] [blame]308
Chris Lattnerb0d6c502007-09-21 03:54:09 +0000[diff] [blame]309</div>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]310
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]311<!--=========================================================================-->
312<div class="doc_subsection">
313<a name="changes">Major Changes and Removed Features</a>
314</div>
315
316<div class="doc_text">
317
Chris Lattnercc64a322008-10-13 22:06:31 +0000[diff] [blame]318<p>If you're already an LLVM user or developer with out-of-tree changes based
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]319on LLVM 2.4, this section lists some "gotchas" that you may run into upgrading
Chris Lattnercc64a322008-10-13 22:06:31 +0000[diff] [blame]320from the previous release.</p>
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]321
322<ul>
323
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]324<li>?</li>
Chris Lattnercc64a322008-10-13 22:06:31 +0000[diff] [blame]325</ul>
326
327
328<p>In addition, many APIs have changed in this release. Some of the major LLVM
329API changes are:</p>
330
331<ul>
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]332<li>?</li>
Devang Patel0e3da1a2008-10-14 20:03:43 +0000[diff] [blame]333</ul>
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]334
Chris Lattner95d25072009-02-25 04:41:31 +0000[diff] [blame]335<li>?</li>
Chris Lattner92eacf82008-10-13 17:57:36 +0000[diff] [blame]336</ul>
337
338</div>
339
340
341
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]342<!-- *********************************************************************** -->
343<div class="doc_section">
344 <a name="portability">Portability and Supported Platforms</a>
345</div>
346<!-- *********************************************************************** -->
347
348<div class="doc_text">
349
350<p>LLVM is known to work on the following platforms:</p>
351
352<ul>
Chris Lattnerb1ad47c2008-11-10 05:40:34 +0000[diff] [blame]353<li>Intel and AMD machines (IA32, X86-64, AMD64, EMT-64) running Red Hat
354Linux, Fedora Core and FreeBSD (and probably other unix-like systems).</li>
355<li>PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit
356and 64-bit modes.</li>
Chris Lattnere0798082008-02-06 18:00:06 +0000[diff] [blame]357<li>Intel and AMD machines running on Win32 using MinGW libraries (native).</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]358<li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
359 support is available for native builds with Visual C++).</li>
Gabor Greif5e75e652008-06-05 18:39:01 +0000[diff] [blame]360<li>Sun UltraSPARC workstations running Solaris 10.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]361<li>Alpha-based machines running Debian GNU/Linux.</li>
Gabor Greif5e75e652008-06-05 18:39:01 +0000[diff] [blame]362<li>Itanium-based (IA64) machines running Linux and HP-UX.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]363</ul>
364
Chris Lattnerba948522008-06-05 06:57:39 +0000[diff] [blame]365<p>The core LLVM infrastructure uses GNU autoconf to adapt itself
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]366to the machine and operating system on which it is built. However, minor
367porting may be required to get LLVM to work on new platforms. We welcome your
368portability patches and reports of successful builds or error messages.</p>
369
370</div>
371
372<!-- *********************************************************************** -->
373<div class="doc_section">
374 <a name="knownproblems">Known Problems</a>
375</div>
376<!-- *********************************************************************** -->
377
378<div class="doc_text">
379
Chris Lattnerb1ad47c2008-11-10 05:40:34 +0000[diff] [blame]380<p>This section contains significant known problems with the LLVM system,
381listed by component. If you run into a problem, please check the <a
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]382href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
383there isn't already one.</p>
384
385</div>
386
387<!-- ======================================================================= -->
388<div class="doc_subsection">
389 <a name="experimental">Experimental features included with this release</a>
390</div>
391
392<div class="doc_text">
393
394<p>The following components of this LLVM release are either untested, known to
395be broken or unreliable, or are in early development. These components should
396not be relied on, and bugs should not be filed against them, but they may be
397useful to some people. In particular, if you would like to work on one of these
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]398components, please contact us on the <a
399href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]400
401<ul>
Gabor Greifaa53e562008-10-14 11:31:14 +0000[diff] [blame]402<li>The MSIL, IA64, Alpha, SPU, MIPS, and PIC16 backends are experimental.</li>
Duncan Sandsa73561c2008-06-08 20:18:35 +0000[diff] [blame]403<li>The llc "<tt>-filetype=asm</tt>" (the default) is the only supported
Chris Lattnerbd633de92008-02-06 06:30:34 +0000[diff] [blame]404 value for this option.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]405</ul>
406
407</div>
408
409<!-- ======================================================================= -->
410<div class="doc_subsection">
411 <a name="x86-be">Known problems with the X86 back-end</a>
412</div>
413
414<div class="doc_text">
415
416<ul>
Anton Korobeynikov77d15e22008-06-08 10:24:13 +0000[diff] [blame]417 <li>The X86 backend does not yet support
418 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
419 floating point stack</a>. It supports the 'f' and 't' constraints, but not
420 'u'.</li>
Chris Lattnerd95b5962008-06-08 21:19:07 +0000[diff] [blame]421 <li>The X86 backend generates inefficient floating point code when configured
422 to generate code for systems that don't have SSE2.</li>
Duncan Sands8b4f3772008-06-08 19:38:43 +0000[diff] [blame]423 <li>Win64 code generation wasn't widely tested. Everything should work, but we
Anton Korobeynikov77d15e22008-06-08 10:24:13 +0000[diff] [blame]424 expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime
425 currently due
426 to <a href="http://llvm.org/PR2255">several</a>
Chris Lattnerf06141a2008-06-08 23:12:47 +0000[diff] [blame]427 <a href="http://llvm.org/PR2257">bugs</a> due to lack of support for the
428 'u' inline assembly constraint and X87 floating point inline assembly.</li>
Dan Gohman3882ecb2008-06-08 23:05:11 +0000[diff] [blame]429 <li>The X86-64 backend does not yet support the LLVM IR instruction
430 <tt>va_arg</tt>. Currently, the llvm-gcc front-end supports variadic
431 argument constructs on X86-64 by lowering them manually.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]432</ul>
433
434</div>
435
436<!-- ======================================================================= -->
437<div class="doc_subsection">
438 <a name="ppc-be">Known problems with the PowerPC back-end</a>
439</div>
440
441<div class="doc_text">
442
443<ul>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]444<li>The Linux PPC32/ABI support needs testing for the interpreter and static
445compilation, and lacks support for debug information.</li>
446</ul>
447
448</div>
449
450<!-- ======================================================================= -->
451<div class="doc_subsection">
452 <a name="arm-be">Known problems with the ARM back-end</a>
453</div>
454
455<div class="doc_text">
456
457<ul>
458<li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
Duncan Sands1827fa62007-09-26 15:59:54 +0000[diff] [blame]459processors, thumb programs can crash or produce wrong
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]460results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
461<li>Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested.
462</li>
Chris Lattnerd95b5962008-06-08 21:19:07 +0000[diff] [blame]463<li>There is a bug in QEMU-ARM (&lt;= 0.9.0) which causes it to incorrectly
464 execute
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]465programs compiled with LLVM. Please use more recent versions of QEMU.</li>
466</ul>
467
468</div>
469
470<!-- ======================================================================= -->
471<div class="doc_subsection">
472 <a name="sparc-be">Known problems with the SPARC back-end</a>
473</div>
474
475<div class="doc_text">
476
477<ul>
478<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not
479 support the 64-bit SPARC ABI (-m64).</li>
480</ul>
481
482</div>
483
484<!-- ======================================================================= -->
485<div class="doc_subsection">
Bruno Cardoso Lopes62d45d72008-10-25 14:56:26 +0000[diff] [blame]486 <a name="mips-be">Known problems with the MIPS back-end</a>
487</div>
488
489<div class="doc_text">
490
491<ul>
492<li>The O32 ABI is not fully supported.</li>
493<li>64-bit MIPS targets are not supported yet.</li>
494</ul>
495
496</div>
497
498<!-- ======================================================================= -->
499<div class="doc_subsection">
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]500 <a name="alpha-be">Known problems with the Alpha back-end</a>
501</div>
502
503<div class="doc_text">
504
505<ul>
506
507<li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
508appropriate nops inserted to ensure restartability.</li>
509
510</ul>
511</div>
512
513<!-- ======================================================================= -->
514<div class="doc_subsection">
515 <a name="ia64-be">Known problems with the IA64 back-end</a>
516</div>
517
518<div class="doc_text">
519
520<ul>
Chris Lattnerf06141a2008-06-08 23:12:47 +0000[diff] [blame]521<li>The Itanium backend is highly experimental, and has a number of known
522 issues. We are looking for a maintainer for the Itanium backend. If you
Gabor Greif45fc8b12008-10-15 10:47:24 +0000[diff] [blame]523 are interested, please contact the LLVMdev mailing list.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]524</ul>
525
526</div>
527
528<!-- ======================================================================= -->
529<div class="doc_subsection">
530 <a name="c-be">Known problems with the C back-end</a>
531</div>
532
533<div class="doc_text">
534
535<ul>
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]536<li><a href="http://llvm.org/PR802">The C backend has only basic support for
537 inline assembly code</a>.</li>
Chris Lattnere0194462007-09-26 06:01:35 +0000[diff] [blame]538<li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
539 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
Duncan Sandsa73561c2008-06-08 20:18:35 +0000[diff] [blame]540 C++ code compiled with llc or native compilers.</li>
Duncan Sandsbd0ad6e2008-02-10 13:40:55 +0000[diff] [blame]541<li>The C backend does not support all exception handling constructs.</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]542</ul>
543
544</div>
545
546
547<!-- ======================================================================= -->
548<div class="doc_subsection">
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]549 <a name="c-fe">Known problems with the llvm-gcc C front-end</a>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]550</div>
551
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]552<div class="doc_text">
553
Chris Lattnere0798082008-02-06 18:00:06 +0000[diff] [blame]554<p>llvm-gcc does not currently support <a href="http://llvm.org/PR869">Link-Time
555Optimization</a> on most platforms "out-of-the-box". Please inquire on the
Gabor Greif45fc8b12008-10-15 10:47:24 +0000[diff] [blame]556LLVMdev mailing list if you are interested.</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]557
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]558<p>The only major language feature of GCC not supported by llvm-gcc is
559 the <tt>__builtin_apply</tt> family of builtins. However, some extensions
560 are only supported on some targets. For example, trampolines are only
Duncan Sandsa73561c2008-06-08 20:18:35 +0000[diff] [blame]561 supported on some targets (these are used when you take the address of a
562 nested function).</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]563
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]564<p>If you run into GCC extensions which are not supported, please let us know.
565</p>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]566
567</div>
568
569<!-- ======================================================================= -->
570<div class="doc_subsection">
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]571 <a name="c++-fe">Known problems with the llvm-gcc C++ front-end</a>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]572</div>
573
574<div class="doc_text">
575
576<p>The C++ front-end is considered to be fully
577tested and works for a number of non-trivial programs, including LLVM
578itself, Qt, Mozilla, etc.</p>
579
580<ul>
Anton Korobeynikovd9a17932008-10-11 18:27:16 +0000[diff] [blame]581<li>Exception handling works well on the X86 and PowerPC targets. Currently
Chris Lattnerb1ad47c2008-11-10 05:40:34 +0000[diff] [blame]582 only Linux and Darwin targets are supported (both 32 and 64 bit).</li>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]583</ul>
584
585</div>
586
Chris Lattner6c8a1b82008-10-30 03:58:13 +0000[diff] [blame]587<!-- ======================================================================= -->
588<div class="doc_subsection">
589 <a name="fortran-fe">Known problems with the llvm-gcc Fortran front-end</a>
590</div>
591
592<div class="doc_text">
Gabor Greif1fc8fbc2008-11-04 21:50:59 +0000[diff] [blame]593<ul>
Chris Lattner6c8a1b82008-10-30 03:58:13 +0000[diff] [blame]594<li>Fortran support generally works, but there are still several unresolved bugs
595 in Bugzilla. Please see the tools/gfortran component for details.</li>
596
597<li>The Fortran front-end currently does not build on Darwin (without tweaks)
598 due to unresolved dependencies on the C front-end.</li>
Gabor Greif1fc8fbc2008-11-04 21:50:59 +0000[diff] [blame]599</ul>
Chris Lattner6c8a1b82008-10-30 03:58:13 +0000[diff] [blame]600</div>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]601
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]602<!-- ======================================================================= -->
603<div class="doc_subsection">
Chris Lattner499c07c2008-06-05 06:35:40 +0000[diff] [blame]604 <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a>
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]605</div>
606
607<div class="doc_text">
608The llvm-gcc 4.2 Ada compiler works fairly well, however this is not a mature
609technology and problems should be expected.
610<ul>
Duncan Sandsa73561c2008-06-08 20:18:35 +0000[diff] [blame]611<li>The Ada front-end currently only builds on X86-32. This is mainly due
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]612to lack of trampoline support (pointers to nested functions) on other platforms,
Duncan Sandsa73561c2008-06-08 20:18:35 +0000[diff] [blame]613however it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]614which does support trampolines.</li>
615<li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
616Workaround: configure with --disable-bootstrap.</li>
Duncan Sands2dbc2e82008-10-13 17:27:23 +0000[diff] [blame]617<li>The c380004, <a href="http://llvm.org/PR2010">c393010</a>
618and <a href="http://llvm.org/PR2421">cxg2021</a> ACATS tests fail
619(c380004 also fails with gcc-4.2 mainline).</li>
620<li>Some gcc specific Ada tests continue to crash the compiler.</li>
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]621<li>The -E binder option (exception backtraces)
622<a href="http://llvm.org/PR1982">does not work</a> and will result in programs
623crashing if an exception is raised. Workaround: do not use -E.</li>
624<li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
625or finish at a non-byte offset</a> in a record. Workaround: do not pack records
626or use representation clauses that result in a field of a non-discrete type
627starting or finishing in the middle of a byte.</li>
Chris Lattnerd95b5962008-06-08 21:19:07 +0000[diff] [blame]628<li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
629'main' as generated by the Ada binder to be invalid</a>.
630Workaround: hand edit the file to use pointers for <tt>argv</tt> and
631<tt>envp</tt> rather than integers.</li>
632<li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
633ignored</a>.</li>
Chris Lattnerdaeb3232008-02-12 06:29:45 +0000[diff] [blame]634</ul>
635</div>
636
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]637<!-- *********************************************************************** -->
638<div class="doc_section">
639 <a name="additionalinfo">Additional Information</a>
640</div>
641<!-- *********************************************************************** -->
642
643<div class="doc_text">
644
645<p>A wide variety of additional information is available on the <a
646href="http://llvm.org">LLVM web page</a>, in particular in the <a
647href="http://llvm.org/docs/">documentation</a> section. The web page also
648contains versions of the API documentation which is up-to-date with the
649Subversion version of the source code.
650You can access versions of these documents specific to this release by going
651into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
652
653<p>If you have any questions or comments about LLVM, please feel free to contact
654us via the <a href="http://llvm.org/docs/#maillist"> mailing
655lists</a>.</p>
656
657</div>
658
659<!-- *********************************************************************** -->
660
661<hr>
662<address>
663 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman947321d2008-12-11 17:34:48 +0000[diff] [blame]664 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]665 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman947321d2008-12-11 17:34:48 +0000[diff] [blame]666 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Dan Gohmanf17a25c2007-07-18 16:29:46 +0000[diff] [blame]667
668 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
669 Last modified: $Date$
670</address>
671
672</body>
673</html>