Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / a844a3e7b2bae7a0b3c0ed4547b26346c17e2779 / . / docs / ReleaseNotes.html
blob: bc86bd4452242bea2337d44759d2eb937faa16e2 [file] [log] [blame]
Misha Brukman500bc302003-11-22 00:38:41 +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>
Reid Spencer6454ed32004-11-18 18:38:58 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Chris Lattner2fb6e5c2010-10-03 23:09:03 +0000[diff] [blame]6 <meta encoding="utf8">
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]7 <link rel="stylesheet" href="llvm.css" type="text/css">
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]8 <title>LLVM 2.9 Release Notes</title>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]9</head>
10<body>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]11
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]12<h1 class="doc_title">LLVM 2.9 Release Notes</h1>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]13
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]14<img align=right src="http://llvm.org/img/DragonSmall.png"
Gabor Greifee2187a2010-04-22 10:21:43 +0000[diff] [blame]15 width="136" height="136" alt="LLVM Dragon Logo">
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]16
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]17<ol>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]18 <li><a href="#intro">Introduction</a></li>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]19 <li><a href="#subproj">Sub-project Status Update</a></li>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]20 <li><a href="#externalproj">External Projects Using LLVM 2.9</a></li>
21 <li><a href="#whatsnew">What's New in LLVM 2.9?</a></li>
Chris Lattner4b538b92004-04-30 22:17:12 +0000[diff] [blame]22 <li><a href="GettingStarted.html">Installation Instructions</a></li>
Dan Gohman44aa9212008-10-14 16:23:02 +0000[diff] [blame]23 <li><a href="#knownproblems">Known Problems</a></li>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]24 <li><a href="#additionalinfo">Additional Information</a></li>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]25</ol>
26
Chris Lattner7911ce22004-05-23 21:07:27 +0000[diff] [blame]27<div class="doc_author">
Dan Gohman44aa9212008-10-14 16:23:02 +0000[diff] [blame]28 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]29</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]30
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]31<!--
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]32<h1 style="color:red">These are in-progress notes for the upcoming LLVM 2.9
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]33release.<br>
34You may prefer the
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]35<a href="http://llvm.org/releases/2.8/docs/ReleaseNotes.html">LLVM 2.8
Dan Gohmanb44f6c62010-05-03 23:51:05 +0000[diff] [blame]36Release Notes</a>.</h1>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]37 -->
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]38
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]39<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]40<h1>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]41 <a name="intro">Introduction</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]42</h1>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]43<!-- *********************************************************************** -->
44
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]45<div class="doc_text">
46
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]47<p>This document contains the release notes for the LLVM Compiler
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]48Infrastructure, release 2.9. Here we describe the status of LLVM, including
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]49major improvements from the previous release and significant known problems.
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]50All LLVM releases may be downloaded from the <a
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]51href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
Chris Lattner19092612003-10-02 16:38:05 +0000[diff] [blame]52
Chris Lattner7506b1d2004-12-07 08:04:13 +0000[diff] [blame]53<p>For more information about LLVM, including information about the latest
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]54release, please check out the <a href="http://llvm.org/">main LLVM
Chris Lattner47ad72c2003-10-07 21:38:31 +0000[diff] [blame]55web site</a>. If you have questions or comments, the <a
Chris Lattnerc66bfef2010-03-17 04:41:49 +0000[diff] [blame]56href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's
57Mailing List</a> is a good place to send them.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]58
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]59<p>Note that if you are reading this file from a Subversion checkout or the
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]60main LLVM web page, this document applies to the <i>next</i> release, not the
Gabor Greiffa933f82008-10-14 11:00:32 +0000[diff] [blame]61current one. To see the release notes for a specific release, please see the
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]62<a href="http://llvm.org/releases/">releases page</a>.</p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]63
64</div>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]65
Chris Lattnere4dc1962011-04-05 23:22:33 +0000[diff] [blame]66<!-- Features that need text if they're finished for 3.1:
67 ARM EHABI
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]68 combiner-aa?
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]69 strong phi elim
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]70 loop dependence analysis
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]71 CorrelatedValuePropagation
Chris Lattnere4dc1962011-04-05 23:22:33 +0000[diff] [blame]72 lib/Transforms/IPO/MergeFunctions.cpp => consider for 3.1.
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]73 -->
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]74
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]75<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]76<h1>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]77 <a name="subproj">Sub-project Status Update</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]78</h1>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]79<!-- *********************************************************************** -->
Chris Lattnerea34f642008-06-08 21:34:41 +0000[diff] [blame]80
81<div class="doc_text">
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]82<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]83The LLVM 2.9 distribution currently consists of code from the core LLVM
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]84repository (which roughly includes the LLVM optimizers, code generators
85and supporting tools), the Clang repository and the llvm-gcc repository. In
86addition to this code, the LLVM Project includes other sub-projects that are in
87development. Here we include updates on these subprojects.
Bill Wendling63d8c552009-03-02 04:28:57 +0000[diff] [blame]88</p>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]89
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]90</div>
91
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]92
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]93<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]94<h2>
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]95<a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]96</h2>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]97
98<div class="doc_text">
99
Chris Lattner095539f2010-04-26 17:42:18 +0000[diff] [blame]100<p><a href="http://clang.llvm.org/">Clang</a> is an LLVM front end for the C,
101C++, and Objective-C languages. Clang aims to provide a better user experience
102through expressive diagnostics, a high level of conformance to language
103standards, fast compilation, and low memory use. Like LLVM, Clang provides a
104modular, library-based architecture that makes it suitable for creating or
105integrating with other development tools. Clang is considered a
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]106production-quality compiler for C, Objective-C, C++ and Objective-C++ on x86
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]107(32- and 64-bit), and for darwin/arm targets.</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]108
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]109<p>In the LLVM 2.9 time-frame, the Clang team has made many improvements in C,
110C++ and Objective-C support. C++ support is now generally rock solid, has
Chris Lattnerdf448a32011-04-06 00:56:12 +0000[diff] [blame]111been exercised on a broad variety of code, and has several new <a
112href="http://clang.llvm.org/cxx_status.html#cxx0x">C++'0x features</a>
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]113implemented (such as rvalue references and variadic templates). LLVM 2.9 has
114also brought in a large range of bug fixes and minor features (e.g. __label__
115support), and is much more compatible with the Linux Kernel.</p>
116
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]117<p>If Clang rejects your code but another compiler accepts it, please take a
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]118look at the <a href="http://clang.llvm.org/compatibility.html">language
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]119compatibility</a> guide to make sure this is not intentional or a known issue.
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]120</p>
Bill Wendling741748a2008-10-27 09:27:33 +0000[diff] [blame]121
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]122<ul>
123</ul>
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]124</div>
125
126<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]127<h2>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]128<a name="dragonegg">DragonEgg: GCC front-ends, LLVM back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]129</h2>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]130
131<div class="doc_text">
132<p>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]133<a href="http://dragonegg.llvm.org/">DragonEgg</a> is a
134<a href="http://gcc.gnu.org/wiki/plugins">gcc plugin</a> that replaces GCC's
135optimizers and code generators with LLVM's.
136Currently it requires a patched version of gcc-4.5.
137The plugin can target the x86-32 and x86-64 processor families and has been
138used successfully on the Darwin, FreeBSD and Linux platforms.
139The Ada, C, C++ and Fortran languages work well.
140The plugin is capable of compiling plenty of Obj-C, Obj-C++ and Java but it is
141not known whether the compiled code actually works or not!
Duncan Sands749fd832010-04-02 09:23:15 +0000[diff] [blame]142</p>
143
144<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]145The 2.9 release has the following notable changes:
Duncan Sands4b1da2b2010-09-30 17:37:34 +0000[diff] [blame]146<ul>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]147<li>The plugin is much more stable when compiling Fortran.</li>
Chris Lattnerdf448a32011-04-06 00:56:12 +0000[diff] [blame]148<li>Inline assembly where an asm output is tied to an input of a different size
149is now supported in many more cases.</li>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]150<li>Basic support for the __float128 type was added. It is now possible to
151generate LLVM IR from programs using __float128 but code generation does not
152work yet.</li>
153<li>Compiling Java programs no longer systematically crashes the plugin.</li>
Duncan Sands4b1da2b2010-09-30 17:37:34 +0000[diff] [blame]154</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]155
156</div>
157
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]158<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]159<h2>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]160<a name="compiler-rt">compiler-rt: Compiler Runtime Library</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]161</h2>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]162
163<div class="doc_text">
164<p>
165The new LLVM <a href="http://compiler-rt.llvm.org/">compiler-rt project</a>
166is a simple library that provides an implementation of the low-level
167target-specific hooks required by code generation and other runtime components.
168For example, when compiling for a 32-bit target, converting a double to a 64-bit
169unsigned integer is compiled into a runtime call to the "__fixunsdfdi"
170function. The compiler-rt library provides highly optimized implementations of
171this and other low-level routines (some are 3x faster than the equivalent
172libgcc routines).</p>
173
Chris Lattnerdf448a32011-04-06 00:56:12 +0000[diff] [blame]174<p>In the LLVM 2.9 timeframe, compiler_rt has had several minor changes for
175 better ARM support, and a fairly major license change. All of the code in the
176 compiler-rt project is now <a href="DeveloperPolicy.html#license">dual
177 licensed</a> under MIT and UIUC license, which allows you to use compiler-rt
178 in applications without the binary copyright reproduction clause. If you
179 prefer the LLVM/UIUC license, you are free to continue using it under that
180 license as well.</p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]181
182</div>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]183
184<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]185<h2>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]186<a name="lldb">LLDB: Low Level Debugger</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]187</h2>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]188
189<div class="doc_text">
190<p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]191<a href="http://lldb.llvm.org/">LLDB</a> is a brand new member of the LLVM
192umbrella of projects. LLDB is a next generation, high-performance debugger. It
193is built as a set of reusable components which highly leverage existing
194libraries in the larger LLVM Project, such as the Clang expression parser, the
195LLVM disassembler and the LLVM JIT.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]196
197<p>
Chris Lattnerdf448a32011-04-06 00:56:12 +0000[diff] [blame]198LLDB is has advanced by leaps and bounds in the 2.9 timeframe. It is
199dramatically more stable and useful, and includes both a new <a
200href="http://lldb.llvm.org/tutorial.html">tutorial</a> and a <a
201href="http://lldb.llvm.org/lldb-gdb.html">side-by-side comparison with
202GDB</a>.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]203
204</div>
205
206<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]207<h2>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]208<a name="libc++">libc++: C++ Standard Library</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]209</h2>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]210
211<div class="doc_text">
212<p>
Tobias Grossercdce44b2010-10-06 21:07:30 +0000[diff] [blame]213<a href="http://libcxx.llvm.org/">libc++</a> is another new member of the LLVM
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]214family. It is an implementation of the C++ standard library, written from the
215ground up to specifically target the forthcoming C++'0X standard and focus on
216delivering great performance.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]217
218<p>
Chris Lattner2009c492011-04-06 00:59:18 +0000[diff] [blame]219In the LLVM 2.9 timeframe, libc++ has had numerous bugs fixed, and is now being
220co-developed with Clang's C++'0x mode.</p>
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]221
Chris Lattner2009c492011-04-06 00:59:18 +0000[diff] [blame]222<p>
223Like compiler_rt, libc++ is now <a href="DeveloperPolicy.html#license">dual
224 licensed</a> under the MIT and UIUC license, allowing it to be used more
225 permissively.
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]226</p>
227
228</div>
229
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]230
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]231<!--=========================================================================-->
232<h2>
233<a name="LLBrowse">LLBrowse: IR Browser</a>
234</h2>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]235
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]236<div class="doc_text">
237<p>
238<a href="http://llvm.org/svn/llvm-project/llbrowse/trunk/doc/LLBrowse.html">
239 LLBrowse</a> is an interactive viewer for LLVM modules. It can load any LLVM
240 module and displays its contents as an expandable tree view, facilitating an
241 easy way to inspect types, functions, global variables, or metadata nodes. It
242 is fully cross-platform, being based on the popular wxWidgets GUI toolkit.
243</p>
244</div>
245
246<!--=========================================================================-->
247<h2>
248<a name="vmkit">VMKit</a>
249</h2>
250
251<div class="doc_text">
252<p>The <a href="http://vmkit.llvm.org/">VMKit project</a> is an implementation
253 of a Java Virtual Machine (Java VM or JVM) that uses LLVM for static and
254 just-in-time compilation. As of LLVM 2.9, VMKit now supports generational
255 garbage collectors. The garbage collectors are provided by the MMTk framework,
256 and VMKit can be configured to use one of the numerous implemented collectors
257 of MMTk.
258</p>
259</div>
260
261
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]262<!--=========================================================================-->
Chris Lattner7a8e6c52011-04-05 18:38:45 +0000[diff] [blame]263<!--
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]264<h2>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]265<a name="klee">KLEE: A Symbolic Execution Virtual Machine</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]266</h2>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]267
268<div class="doc_text">
269<p>
270<a href="http://klee.llvm.org/">KLEE</a> is a symbolic execution framework for
271programs in LLVM bitcode form. KLEE tries to symbolically evaluate "all" paths
272through the application and records state transitions that lead to fault
273states. This allows it to construct testcases that lead to faults and can even
274be used to verify some algorithms.
275</p>
276
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]277<p>UPDATE!</p>
Chris Lattner7a8e6c52011-04-05 18:38:45 +0000[diff] [blame]278</div>-->
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]279
280
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]281<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]282<h1>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]283 <a name="externalproj">External Open Source Projects Using LLVM 2.9</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]284</h1>
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]285<!-- *********************************************************************** -->
286
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]287<div class="doc_text">
288
289<p>An exciting aspect of LLVM is that it is used as an enabling technology for
290 a lot of other language and tools projects. This section lists some of the
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]291 projects that have already been updated to work with LLVM 2.9.</p>
Chris Lattner7c8e7962010-04-26 17:38:10 +0000[diff] [blame]292</div>
293
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]294
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]295<!--=========================================================================-->
296<h2>Crack Programming Language</h2>
297
298<div class="doc_text">
299<p>
300<a href="http://code.google.com/p/crack-language/">Crack</a> aims to provide the
301ease of development of a scripting language with the performance of a compiled
302language. The language derives concepts from C++, Java and Python, incorporating
303object-oriented programming, operator overloading and strong typing.</p>
304</div>
305
306
307<!--=========================================================================-->
308<h2>TTA-based Codesign Environment (TCE)</h2>
309
310<div class="doc_text">
311<p>TCE is a toolset for designing application-specific processors (ASP) based on
312the Transport triggered architecture (TTA). The toolset provides a complete
313co-design flow from C/C++ programs down to synthesizable VHDL and parallel
314program binaries. Processor customization points include the register files,
315function units, supported operations, and the interconnection network.</p>
316
317<p>TCE uses Clang and LLVM for C/C++ language support, target independent
318optimizations and also for parts of code generation. It generates new LLVM-based
319code generators "on the fly" for the designed TTA processors and loads them in
320to the compiler backend as runtime libraries to avoid per-target recompilation
321of larger parts of the compiler chain.</p>
322</div>
323
324
325
326<!--=========================================================================-->
327<h2>PinaVM</h2>
328
329<div class="doc_text">
330<p><a href="http://gitorious.org/pinavm/pages/Home">PinaVM</a> is an open
331source, <a href="http://www.systemc.org/">SystemC</a> front-end. Unlike many
332other front-ends, PinaVM actually executes the elaboration of the
333program analyzed using LLVM's JIT infrastructure. It later enriches the
334bitcode with SystemC-specific information.</p>
335</div>
336
337<!--=========================================================================-->
338<h2>Pure</h2>
339
340<div class="doc_text">
341<p><a href="http://pure-lang.googlecode.com/">Pure</a> is an
342 algebraic/functional
343 programming language based on term rewriting. Programs are collections
344 of equations which are used to evaluate expressions in a symbolic
345 fashion. The interpreter uses LLVM as a backend to JIT-compile Pure
346 programs to fast native code. Pure offers dynamic typing, eager and lazy
347 evaluation, lexical closures, a hygienic macro system (also based on
348 term rewriting), built-in list and matrix support (including list and
349 matrix comprehensions) and an easy-to-use interface to C and other
350 programming languages (including the ability to load LLVM bitcode
351 modules, and inline C, C++, Fortran and Faust code in Pure programs if
352 the corresponding LLVM-enabled compilers are installed).</p>
353
354<p>Pure version 0.47 has been tested and is known to work with LLVM 2.9
355 (and continues to work with older LLVM releases &gt;= 2.5).</p>
356</div>
357
358<!--=========================================================================-->
359<h2 id="icedtea">IcedTea Java Virtual Machine Implementation</h2>
360
361<div class="doc_text">
362<p>
363<a href="http://icedtea.classpath.org/wiki/Main_Page">IcedTea</a> provides a
364harness to build OpenJDK using only free software build tools and to provide
365replacements for the not-yet free parts of OpenJDK. One of the extensions that
366IcedTea provides is a new JIT compiler named <a
367href="http://icedtea.classpath.org/wiki/ZeroSharkFaq">Shark</a> which uses LLVM
368to provide native code generation without introducing processor-dependent
369code.
370</p>
371
372<p> OpenJDK 7 b112, IcedTea6 1.9 and IcedTea7 1.13 and later have been tested
373and are known to work with LLVM 2.9 (and continue to work with older LLVM
374releases &gt;= 2.6 as well).</p>
375</div>
376
377<!--=========================================================================-->
378<h2>Glasgow Haskell Compiler (GHC)</h2>
379
380<div class="doc_text">
381<p>GHC is an open source, state-of-the-art programming suite for Haskell,
382a standard lazy functional programming language. It includes an
383optimizing static compiler generating good code for a variety of
384platforms, together with an interactive system for convenient, quick
385development.</p>
386
387<p>In addition to the existing C and native code generators, GHC 7.0 now
388supports an LLVM code generator. GHC supports LLVM 2.7 and later.</p>
389</div>
390
391<!--=========================================================================-->
392<h2>Polly - Polyhedral optimizations for LLVM</h2>
393
394<div class="doc_text">
395<p>Polly is a project that aims to provide advanced memory access optimizations
396to better take advantage of SIMD units, cache hierarchies, multiple cores or
397even vector accelerators for LLVM. Built around an abstract mathematical
398description based on Z-polyhedra, it provides the infrastructure to develop
399advanced optimizations in LLVM and to connect complex external optimizers. In
400its first year of existence Polly already provides an exact value-based
401dependency analysis as well as basic SIMD and OpenMP code generation support.
402Furthermore, Polly can use PoCC(Pluto) an advanced optimizer for data-locality
403and parallelism.</p>
404</div>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]405
Chris Lattner0fa5da92011-04-06 16:14:25 +0000[diff] [blame]406<!--=========================================================================-->
407<h2>Rubinius</h2>
408
409<div class="doc_text">
410 <p><a href="http://github.com/evanphx/rubinius">Rubinius</a> is an environment
411 for running Ruby code which strives to write as much of the implementation in
412 Ruby as possible. Combined with a bytecode interpreting VM, it uses LLVM to
413 optimize and compile ruby code down to machine code. Techniques such as type
414 feedback, method inlining, and deoptimization are all used to remove dynamism
415 from ruby execution and increase performance.</p>
416</div>
417
418
Chris Lattnera844a3e2011-04-07 03:09:21 +0000[diff] [blame^]419<!--=========================================================================-->
420<div class="doc_subsection">
421<a name="FAUST">FAUST Real-Time Audio Signal Processing Language</a>
422</div>
Chris Lattnere0518442010-10-01 06:34:49 +0000[diff] [blame]423
Chris Lattnera844a3e2011-04-07 03:09:21 +0000[diff] [blame^]424<div class="doc_text">
425<p>
426<a href="http://faust.grame.fr">FAUST</a> is a compiled language for real-time
427audio signal processing. The name FAUST stands for Functional AUdio STream. Its
428programming model combines two approaches: functional programming and block
429diagram composition. In addition with the C, C++, JAVA output formats, the
430Faust compiler can now generate LLVM bitcode, and works with LLVM 2.7-2.9.</p>
431
432</div>
433
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]434<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]435<h1>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]436 <a name="whatsnew">What's New in LLVM 2.9?</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]437</h1>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]438<!-- *********************************************************************** -->
439
Chris Lattnerf8e0b4e2008-06-08 22:59:35 +0000[diff] [blame]440<div class="doc_text">
441
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]442<p>This release includes a huge number of bug fixes, performance tweaks and
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]443minor improvements. Some of the major improvements and new features are listed
444in this section.
Chris Lattnerf8e0b4e2008-06-08 22:59:35 +0000[diff] [blame]445</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]446
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]447</div>
448
449<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]450<h2>
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]451<a name="majorfeatures">Major New Features</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]452</h2>
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]453
454<div class="doc_text">
455
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]456<p>LLVM 2.9 includes several major new capabilities:</p>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]457
458<ul>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]459
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]460<li>Type Based Alias Analysis (TBAA) is now implemented and turned on by default
461 in Clang. This allows substantially better load/store optimization in some
462 cases. TBAA can be disabled by passing -fno-strict-aliasing.
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]463</li>
464
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]465<li>This release has seen a continued focus on quality of debug information.
466 LLVM now generates much higher fidelity debug information, particularly when
467 debugging optimized code.</li>
468
469<li>Inline assembly now supports multiple alternative constraints.</li>
470
471<li>A new backend for the NVIDIA PTX virtual ISA (used to target its GPUs) is
472 under rapid development. It is not generally useful in 2.9, but is making
473 rapid progress.</li>
Chris Lattner7a8e6c52011-04-05 18:38:45 +0000[diff] [blame]474
Chris Lattner8170c102008-02-10 08:18:42 +0000[diff] [blame]475</ul>
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]476
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]477</div>
478
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]479<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]480<h2>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]481<a name="coreimprovements">LLVM IR and Core Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]482</h2>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]483
484<div class="doc_text">
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]485<p>LLVM IR has several new features for better support of new targets and that
486expose new optimization opportunities:</p>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]487
Chris Lattner791f77b2008-06-05 06:25:56 +0000[diff] [blame]488<ul>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]489<li>The <a href="LangRef.html#bitwiseops">udiv, ashr, lshr, and shl</a>
490 instructions now have support exact and nuw/nsw bits to indicate that they
491 don't overflow or shift out bits. This is useful for optimization of <a
492 href="http://llvm.org/PR8862">pointer differences</a> and other cases.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]493
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]494<li>LLVM IR now supports the <a href="LangRef.html#globalvars">unnamed_addr</a>
495 attribute to indicate that constant global variables with identical
496 initializers can be merged. This fixed <a href="http://llvm.org/PR8927">an
497 issue</a> where LLVM would incorrectly merge two globals which were supposed
498 to have distinct addresses.</li>
499
500<li>The new <a href="LangRef.html#fnattrs">hotpatch attribute</a> has been added
501 to allow runtime patching of functions.</li>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]502</ul>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]503
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]504</div>
505
506<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]507<h2>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]508<a name="optimizer">Optimizer Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]509</h2>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]510
511<div class="doc_text">
512
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]513<p>In addition to a large array of minor performance tweaks and bug fixes, this
Chris Lattnerf3013872008-10-13 21:50:36 +0000[diff] [blame]514release includes a few major enhancements and additions to the optimizers:</p>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]515
516<ul>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]517<li>Link Time Optimization (LTO) has been improved to use MC for parsing inline
518 assembly and now can build large programs like Firefox 4 on both Mac OS X and
519 Linux.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]520
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]521<li>The new -loop-idiom pass recognizes memset/memcpy loops (and memset_pattern
522 on darwin), turning them into library calls, which are typically better
523 optimized than inline code. If you are building a libc and notice that your
524 memcpy and memset functions are compiled into infinite recursion, please build
525 with -ffreestanding or -fno-builtin to disable this pass.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]526
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]527<li>A new -early-cse pass does a fast pass over functions to fold constants,
528 simplify expressions, perform simple dead store elimination, and perform
529 common subexpression elimination. It does a good job at catching some of the
530 trivial redundancies that exist in unoptimized code, making later passes more
Roman Divacky77b42e92011-04-06 19:12:21 +0000[diff] [blame]531 effective.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]532
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]533<li>A new -loop-instsimplify pass is used to clean up loop bodies in the loop
534 optimizer.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]535
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]536<li>The new TargetLibraryInfo interface allows mid-level optimizations to know
537 whether the current target's runtime library has certain functions. For
538 example, the optimizer can now transform integer-only printf calls to call
539 iprintf, allowing reduced code size for embedded C libraries (e.g. newlib).
540</li>
541
542<li>LLVM has a new <a href="WritingAnLLVMPass.html#RegionPass">RegionPass</a>
543 infrastructure for region-based optimizations.</li>
544
545<li>Several optimizer passes have been substantially sped up:
546 GVN is much faster on functions with deep dominator trees and lots of basic
547 blocks. The dominator tree and dominance frontier passes are much faster to
548 compute, and preserved by more passes (so they are computed less often). The
549 -scalar-repl pass is also much faster and doesn't use DominanceFrontier.
550</li>
551
552<li>The Dead Store Elimination pass is more aggressive optimizing stores of
553 different types: e.g. a large store following a small one to the same address.
554 The MemCpyOptimizer pass handles several new forms of memcpy elimination.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]555
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]556<li>LLVM now optimizes various idioms for overflow detection into check of the
557 flag register on various CPUs. For example, we now compile:
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]558
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]559 <pre>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]560 unsigned long t = a+b;
561 if (t &lt; a) ...
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]562 </pre>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]563 into:
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]564 <pre>
565 addq %rdi, %rbx
566 jno LBB0_2
567 </pre>
568</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]569
Chris Lattner11b66112010-10-04 02:42:39 +0000[diff] [blame]570</ul>
571
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]572</div>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]573
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]574<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]575<h2>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]576<a name="mc">MC Level Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]577</h2>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]578
579<div class="doc_text">
580<p>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]581The LLVM Machine Code (aka MC) subsystem was created to solve a number
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]582of problems in the realm of assembly, disassembly, object file format handling,
583and a number of other related areas that CPU instruction-set level tools work
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]584in.</p>
585
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]586<ul>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]587<li>ELF MC support has matured enough for the integrated assembler to be turned
588 on by default in Clang on X86-32 and X86-64 ELF systems.</li>
589
590<li>MC supports and CodeGen uses the <tt>.file</tt> and <tt>.loc</tt> directives
591 for producing line number debug info. This produces more compact line
592 tables and easier to read .s files.</li>
593
594<li>MC supports the <tt>.cfi_*</tt> directives for producing DWARF
Rafael Espindolaa26f36c2011-03-18 04:07:44 +0000[diff] [blame]595 frame information, but it is still not used by CodeGen by default.</li>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]596
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]597
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]598<li>The MC assembler now generates much better diagnostics for common errors,
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]599 is much faster at matching instructions, is much more bug-compatible with
600 the GAS assembler, and is now generally useful for a broad range of X86
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]601 assembly.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]602
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]603<li>We now have some basic <a href="CodeGenerator.html#mc">internals
604 documentation</a> for MC.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]605
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]606<li>.td files can now specify assembler aliases directly with the <a
607 href="CodeGenerator.html#na_instparsing">MnemonicAlias and InstAlias</a>
608 tblgen classes.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]609
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]610<li>LLVM now has an experimental format-independent object file manipulation
611 library (lib/Object). It supports both PE/COFF and ELF. The llvm-nm tool has
612 been extended to work with native object files, and the new llvm-objdump tool
613 supports disassembly of object files (but no relocations are displayed yet).
614</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]615
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]616<li>Win32 PE-COFF support in the MC assembler has made a lot of progress in the
617 2.9 timeframe, but is still not generally useful.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]618
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]619</ul>
620
621<p>For more information, please see the <a
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]622href="http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html">Intro to the
623LLVM MC Project Blog Post</a>.
624</p>
625
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame]626</div>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]627
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]628<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]629<h2>
Chris Lattner511433e2009-03-02 03:24:11 +0000[diff] [blame]630<a name="codegen">Target Independent Code Generator Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]631</h2>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]632
633<div class="doc_text">
634
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]635<p>We have put a significant amount of work into the code generator
636infrastructure, which allows us to implement more aggressive algorithms and make
637it run faster:</p>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]638
639<ul>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]640<li>The pre-register-allocation (preRA) instruction scheduler models register
641 pressure much more accurately in some cases. This allows the adoption of more
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]642 aggressive scheduling heuristics without causing spills to be generated.
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]643</li>
644
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]645<li>LiveDebugVariables is a new pass that keeps track of debugging information
646 for user variables that are promoted to registers in optimized builds.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]647
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]648<li>The scheduler now models operand latency and pipeline forwarding.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]649
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]650<li>A major register allocator infrastructure rewrite is underway. It is not on
651 by default for 2.9 and you are not advised to use it, but it has made
652 substantial progress in the 2.9 timeframe:
653 <ul>
654 <li>A new -regalloc=basic "basic" register allocator can be used as a simple
655 fallback when debugging. It uses the new infrastructure.</li>
656 <li>New infrastructure is in place for live range splitting. "SplitKit" can
657 break a live interval into smaller pieces while preserving SSA form, and
658 SpillPlacement can help find the best split points. This is a work in
659 progress so the API is changing quickly.</li>
660 <li>The inline spiller has learned to clean up after live range splitting. It
661 can hoist spills out of loops, and it can eliminate redundant spills.</li>
662 <li>Rematerialization works with live range splitting.</li>
663 <li>The new "greedy" register allocator using live range splitting. This will
664 be the default register allocator in the next LLVM release, but it is not
665 turned on by default in 2.9.</li>
666 </ul>
667</li>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]668</ul>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]669</div>
670
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]671<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]672<h2>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]673<a name="x86">X86-32 and X86-64 Target Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]674</h2>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]675
676<div class="doc_text">
Chris Lattner7714c912010-10-04 04:39:25 +0000[diff] [blame]677<p>New features and major changes in the X86 target include:
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]678</p>
679
680<ul>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]681<li>LLVM 2.9 includes a complete reimplementation of the MMX instruction set.
682 The reimplementation uses a new LLVM IR <a
683 href="LangRef.html#t_x86mmx">x86_mmx</a> type to ensure that MMX operations
684 are <em>only</em> generated from source that uses MMX builtin operations. With
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]685 this, random types like &lt;2 x i32&gt; are not turned into MMX operations
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]686 (which can be catastrophic without proper "emms" insertion). Because the X86
687 code generator always generates reliable code, the -disable-mmx flag is now
688 removed.
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]689</li>
690
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]691<li>X86 support for FS/GS relative loads and stores using <a
Jay Foadcb88ec32011-04-06 07:55:30 +0000[diff] [blame]692 href="CodeGenerator.html#x86_memory">address space 256/257</a> works reliably
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]693 now.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]694
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]695<li>LLVM 2.9 generates much better code in several cases by using adc/sbb to
696 avoid generation of conditional move instructions for conditional increment
697 and other idioms.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]698
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]699<li>The X86 backend has adopted a new preRA scheduling mode, "list-ilp", to
700 shorten the height of instruction schedules without inducing register spills.
701</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]702
Jay Foadcb88ec32011-04-06 07:55:30 +0000[diff] [blame]703<li>The MC assembler supports 3dNow! and 3DNowA instructions.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]704
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]705<li>Several bugs have been fixed for Windows x64 code generator.</li>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]706</ul>
707
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]708</div>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]709
710<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]711<h2>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]712<a name="ARM">ARM Target Improvements</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]713</h2>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]714
715<div class="doc_text">
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]716<p>New features of the ARM target include:
717</p>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]718
719<ul>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]720<li>The ARM backend now has a fast instruction selector, which dramatically
721 improves -O0 compile times.</li>
722<li>The ARM backend has new tuning for Cortex-A8 and Cortex-A9 CPUs.</li>
723<li>The __builtin_prefetch builtin (and llvm.prefetch intrinsic) is compiled
724 into prefetch instructions instead of being discarded.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]725
726<li> The ARM backend preRA scheduler now models machine resources at cycle
727 granularity. This allows the scheduler to both accurately model
728 instruction latency and avoid overcommitting functional units.</li>
729
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]730<li>Countless ARM microoptimizations have landed in LLVM 2.9.</li>
Bob Wilsone8472772010-09-13 17:39:35 +0000[diff] [blame]731</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]732</div>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]733
734<!--=========================================================================-->
735<h2>
736<a name="OtherTS">Other Target Specific Improvements</a>
737</h2>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]738
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]739<div class="doc_text">
740<ul>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]741<li>MicroBlaze: major updates for aggressive delay slot filler, MC-based
742 assembly printing, assembly instruction parsing, ELF .o file emission, and MC
743 instruction disassembler have landed.</li>
744
745<li>SPARC: Many improvements, including using the Y registers for
746 multiplications and addition of a simple delay slot filler.</li>
747
748<li>PowerPC: The backend has been largely MC'ized and is ready to support
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]749 directly writing out mach-o object files. No one seems interested in finishing
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]750 this final step though.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]751
752</ul>
753</div>
Chris Lattner77d29b12008-06-05 08:02:49 +0000[diff] [blame]754
755<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]756<h2>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]757<a name="changes">Major Changes and Removed Features</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]758</h2>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]759
760<div class="doc_text">
761
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]762<p>If you're already an LLVM user or developer with out-of-tree changes based
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]763on LLVM 2.8, this section lists some "gotchas" that you may run into upgrading
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]764from the previous release.</p>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]765
766<ul>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]767<li><b>This is the last release to support the llvm-gcc frontend.</b></li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]768
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]769<li>LLVM has a new <a href="CodingStandards.html#ll_naming">naming
770 convention standard</a>, though the codebase hasn't fully adopted it yet.</li>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]771
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]772<li>The new DIBuilder class provides a simpler interface for front ends to
773 encode debug info in LLVM IR, and has replaced DIFactory.</li>
Chris Lattnerc5ac61d2011-04-06 05:50:04 +0000[diff] [blame]774
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]775<li>LLVM IR and other tools always work on normalized target triples (which have
776 been run through <tt>Triple::normalize</tt>).</li>
777
778<li>The target triple x86_64--mingw64 is obsoleted. Use x86_64--mingw32
779 instead.</li>
780
781<li>The PointerTracking pass has been removed from mainline, and moved to The
782 ClamAV project (its only client).</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]783
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]784<li>The LoopIndexSplit, LiveValues, SimplifyHalfPowrLibCalls, GEPSplitter, and
785 PartialSpecialization passes were removed. They were unmaintained,
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]786 buggy, or deemed to be a bad idea.</li>
Devang Patelb34dd132008-10-14 20:03:43 +0000[diff] [blame]787</ul>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]788
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]789</div>
790
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]791<!--=========================================================================-->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]792<h2>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]793<a name="api_changes">Internal API Changes</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]794</h2>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]795
796<div class="doc_text">
797
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]798<p>In addition, many APIs have changed in this release. Some of the major
799 LLVM API changes are:</p>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]800
801<ul>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]802<li>include/llvm/System merged into include/llvm/Support.</li>
803<li>The <a href="http://llvm.org/PR5207">llvm::APInt API</a> was significantly
804 cleaned up.</li>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]805
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]806<li>In the code generator, MVT::Flag was renamed to MVT::Glue to more accurately
807 describe its behavior.</li>
808
809<li>The system_error header from C++0x was added, and is now pervasively used to
810 capture and handle i/o and other errors in LLVM.</li>
811
812<li>The old sys::Path API has been deprecated in favor of the new PathV2 API,
813 which is more efficient and flexible.</li>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]814</ul>
815</div>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]816
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]817<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]818<h1>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]819 <a name="knownproblems">Known Problems</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]820</h1>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]821<!-- *********************************************************************** -->
822
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]823<div class="doc_text">
824
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]825<p>This section contains significant known problems with the LLVM system,
Chris Lattnere18b32e2008-11-10 05:40:34 +0000[diff] [blame]826listed by component. If you run into a problem, please check the <a
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]827href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
Chris Lattner5eccca42003-12-12 21:22:16 +0000[diff] [blame]828there isn't already one.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]829
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]830</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]831
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]832<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]833<h2>
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]834 <a name="experimental">Experimental features included with this release</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]835</h2>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]836
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]837<div class="doc_text">
838
Misha Brukman6df9e2c2004-05-12 21:46:05 +0000[diff] [blame]839<p>The following components of this LLVM release are either untested, known to
840be broken or unreliable, or are in early development. These components should
841not be relied on, and bugs should not be filed against them, but they may be
842useful to some people. In particular, if you would like to work on one of these
Chris Lattner2b659ef2008-02-12 06:29:45 +0000[diff] [blame]843components, please contact us on the <a
844href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]845
846<ul>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]847<li>The Alpha, Blackfin, CellSPU, MicroBlaze, MSP430, MIPS, PTX, SystemZ
Chris Lattnerbb117712010-10-04 01:29:06 +0000[diff] [blame]848 and XCore backends are experimental.</li>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]849<li><tt>llc</tt> "<tt>-filetype=obj</tt>" is experimental on all targets
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]850 other than darwin and ELF X86 systems.</li>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]851
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]852</ul>
853
854</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]855
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]856<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]857<h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]858 <a name="x86-be">Known problems with the X86 back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]859</h2>
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]860
861<div class="doc_text">
862
863<ul>
Anton Korobeynikova6094be2008-06-08 10:24:13 +0000[diff] [blame]864 <li>The X86 backend does not yet support
865 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
866 floating point stack</a>. It supports the 'f' and 't' constraints, but not
867 'u'.</li>
Dan Gohman8207ba92008-06-08 23:05:11 +0000[diff] [blame]868 <li>The X86-64 backend does not yet support the LLVM IR instruction
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]869 <tt>va_arg</tt>. Currently, front-ends support variadic
Dan Gohman8207ba92008-06-08 23:05:11 +0000[diff] [blame]870 argument constructs on X86-64 by lowering them manually.</li>
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame]871 <li>Windows x64 (aka Win64) code generator has a few issues.
872 <ul>
873 <li>llvm-gcc cannot build the mingw-w64 runtime currently
874 due to lack of support for the 'u' inline assembly
875 constraint and for X87 floating point inline assembly.</li>
876 <li>On mingw-w64, you will see unresolved symbol <tt>__chkstk</tt>
877 due to <a href="http://llvm.org/bugs/show_bug.cgi?id=8919">Bug 8919</a>.
878 It is fixed in <a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110321/118499.html">r128206</a>.</li>
879 <li>Miss-aligned MOVDQA might crash your program. It is due to
880 <a href="http://llvm.org/bugs/show_bug.cgi?id=9483">Bug 9483</a>,
881 lack of handling aligned internal globals.</li>
882 </ul>
883 </li>
884
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]885</ul>
886
887</div>
888
889<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]890<h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]891 <a name="ppc-be">Known problems with the PowerPC back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]892</h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]893
894<div class="doc_text">
895
896<ul>
Nicolas Geoffraye4285dc2007-05-15 09:21:28 +0000[diff] [blame]897<li>The Linux PPC32/ABI support needs testing for the interpreter and static
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]898compilation, and lacks support for debug information.</li>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]899</ul>
900
901</div>
902
903<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]904<h2>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]905 <a name="arm-be">Known problems with the ARM back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]906</h2>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]907
908<div class="doc_text">
909
910<ul>
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]911<li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
Duncan Sandsc90d68b2007-09-26 15:59:54 +0000[diff] [blame]912processors, thumb programs can crash or produce wrong
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]913results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
John Criswell524a5dd2009-03-02 15:28:15 +0000[diff] [blame]914<li>Compilation for ARM Linux OABI (old ABI) is supported but not fully tested.
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]915</li>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]916</ul>
917
918</div>
919
920<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]921<h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]922 <a name="sparc-be">Known problems with the SPARC back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]923</h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]924
925<div class="doc_text">
926
927<ul>
John Criswell524a5dd2009-03-02 15:28:15 +0000[diff] [blame]928<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]929 support the 64-bit SPARC ABI (-m64).</li>
930</ul>
931
932</div>
933
934<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]935<h2>
Bruno Cardoso Lopesb7e1a4f2008-10-25 14:56:26 +0000[diff] [blame]936 <a name="mips-be">Known problems with the MIPS back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]937</h2>
Bruno Cardoso Lopesb7e1a4f2008-10-25 14:56:26 +0000[diff] [blame]938
939<div class="doc_text">
940
941<ul>
Bruno Cardoso Lopesb7e1a4f2008-10-25 14:56:26 +0000[diff] [blame]942<li>64-bit MIPS targets are not supported yet.</li>
943</ul>
944
945</div>
946
947<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]948<h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]949 <a name="alpha-be">Known problems with the Alpha back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]950</h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]951
952<div class="doc_text">
953
954<ul>
955
956<li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
957appropriate nops inserted to ensure restartability.</li>
958
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]959</ul>
960</div>
961
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]962<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]963<h2>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]964 <a name="c-be">Known problems with the C back-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]965</h2>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]966
967<div class="doc_text">
968
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]969<p>The C backend has numerous problems and is not being actively maintained.
970Depending on it for anything serious is not advised.</p>
971
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]972<ul>
Chris Lattner5733b272008-06-05 06:35:40 +0000[diff] [blame]973<li><a href="http://llvm.org/PR802">The C backend has only basic support for
974 inline assembly code</a>.</li>
Chris Lattner725a0d82007-09-26 06:01:35 +0000[diff] [blame]975<li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
976 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
Gabor Greif4906abe2009-03-02 12:02:51 +0000[diff] [blame]977 C++ code compiled with <tt>llc</tt> or native compilers.</li>
Duncan Sandsf74c0cc2008-02-10 13:40:55 +0000[diff] [blame]978<li>The C backend does not support all exception handling constructs.</li>
Duncan Sands50723a92009-02-25 11:51:54 +0000[diff] [blame]979<li>The C backend does not support arbitrary precision integers.</li>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]980</ul>
981
982</div>
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]983
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]984
985<!-- ======================================================================= -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]986<h2>
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]987 <a name="llvm-gcc">Known problems with the llvm-gcc front-end</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]988</h2>
Chris Lattner47588f92003-10-02 05:07:23 +0000[diff] [blame]989
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]990<div class="doc_text">
Chris Lattnerc5d658a2006-03-03 00:34:26 +0000[diff] [blame]991
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]992<p><b>LLVM 2.9 will be the last release of llvm-gcc.</b></p>
993
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]994<p>llvm-gcc is generally very stable for the C family of languages. The only
995 major language feature of GCC not supported by llvm-gcc is the
996 <tt>__builtin_apply</tt> family of builtins. However, some extensions
997 are only supported on some targets. For example, trampolines are only
998 supported on some targets (these are used when you take the address of a
999 nested function).</p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1000
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]1001<p>Fortran support generally works, but there are still several unresolved bugs
1002 in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the
1003 tools/gfortran component for details. Note that llvm-gcc is missing major
1004 Fortran performance work in the frontend and library that went into GCC after
1005 4.2. If you are interested in Fortran, we recommend that you consider using
1006 <a href="#dragonegg">dragonegg</a> instead.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1007
Duncan Sands3af96332010-10-04 10:06:56 +0000[diff] [blame]1008<p>The llvm-gcc 4.2 Ada compiler has basic functionality, but is no longer being
1009actively maintained. If you are interested in Ada, we recommend that you
1010consider using <a href="#dragonegg">dragonegg</a> instead.</p>
Chris Lattner2b659ef2008-02-12 06:29:45 +0000[diff] [blame]1011</div>
1012
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1013<!-- *********************************************************************** -->
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]1014<h1>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1015 <a name="additionalinfo">Additional Information</a>
NAKAMURA Takumic6319312011-04-05 21:55:14 +0000[diff] [blame]1016</h1>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1017<!-- *********************************************************************** -->
1018
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1019<div class="doc_text">
1020
Chris Lattner416db102005-05-16 17:13:10 +0000[diff] [blame]1021<p>A wide variety of additional information is available on the <a
Chris Lattnerb4b0ce72007-05-18 00:44:29 +0000[diff] [blame]1022href="http://llvm.org">LLVM web page</a>, in particular in the <a
1023href="http://llvm.org/docs/">documentation</a> section. The web page also
Reid Spencer669ed452007-07-09 08:04:31 +0000[diff] [blame]1024contains versions of the API documentation which is up-to-date with the
1025Subversion version of the source code.
Misha Brukman109d9e82005-03-30 19:14:24 +0000[diff] [blame]1026You can access versions of these documents specific to this release by going
1027into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1028
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1029<p>If you have any questions or comments about LLVM, please feel free to contact
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]1030us via the <a href="http://llvm.org/docs/#maillist"> mailing
Chris Lattner5eccca42003-12-12 21:22:16 +0000[diff] [blame]1031lists</a>.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1032
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1033</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1034
1035<!-- *********************************************************************** -->
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1036
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1037<hr>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1038<address>
Misha Brukman38847d52003-12-21 22:53:21 +0000[diff] [blame]1039 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]1040 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1041 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]1042 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1043
Chris Lattnerb4b0ce72007-05-18 00:44:29 +0000[diff] [blame]1044 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1045 Last modified: $Date$
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1046</address>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1047
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1048</body>
1049</html>