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