Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / llvm / bdef6feef478d41707d225caccd25bc6af17081b / . / docs / ReleaseNotes.html
blob: faf9a4bd2b3dbe198b273f995bebe9ccdb1ec6b3 [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">
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]6 <link rel="stylesheet" href="llvm.css" type="text/css">
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]7 <title>LLVM 3.0 Release Notes</title>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]8</head>
9<body>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]10
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]11<h1>LLVM 3.0 Release Notes</h1>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]12
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]13<img align=right src="http://llvm.org/img/DragonSmall.png"
Gabor Greifee2187a2010-04-22 10:21:43 +0000[diff] [blame]14 width="136" height="136" alt="LLVM Dragon Logo">
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]15
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]16<ol>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]17 <li><a href="#intro">Introduction</a></li>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]18 <li><a href="#subproj">Sub-project Status Update</a></li>
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]19 <li><a href="#externalproj">External Projects Using LLVM 3.0</a></li>
20 <li><a href="#whatsnew">What's New in LLVM 3.0?</a></li>
Chris Lattner4b538b92004-04-30 22:17:12 +0000[diff] [blame]21 <li><a href="GettingStarted.html">Installation Instructions</a></li>
Dan Gohman44aa9212008-10-14 16:23:02 +0000[diff] [blame]22 <li><a href="#knownproblems">Known Problems</a></li>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]23 <li><a href="#additionalinfo">Additional Information</a></li>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]24</ol>
25
Chris Lattner7911ce22004-05-23 21:07:27 +0000[diff] [blame]26<div class="doc_author">
NAKAMURA Takumib9a33632011-04-09 02:13:37 +0000[diff] [blame]27 <p>Written by the <a href="http://llvm.org/">LLVM Team</a></p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]28</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]29
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]30<!--
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]31<h1 style="color:red">These are in-progress notes for the upcoming LLVM 3.0
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]32release.<br>
33You may prefer the
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]34<a href="http://llvm.org/releases/2.9/docs/ReleaseNotes.html">LLVM 2.9
Dan Gohmanb44f6c62010-05-03 23:51:05 +0000[diff] [blame]35Release Notes</a>.</h1>
Chris Lattner49123fd2011-04-06 06:29:50 +0000[diff] [blame]36 -->
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]37
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]38<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]39<h2>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]40 <a name="intro">Introduction</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]41</h2>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]42<!-- *********************************************************************** -->
43
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]44<div>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]45
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]46<p>This document contains the release notes for the LLVM Compiler
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]47 Infrastructure, release 3.0. Here we describe the status of LLVM, including
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]48 major improvements from the previous release, improvements in various
49 subprojects of LLVM, and some of the current users of the code.
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]50 All LLVM releases may be downloaded from
51 the <a href="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
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]54 release, please check out the <a href="http://llvm.org/">main LLVM web
55 site</a>. If you have questions or comments,
56 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM
57 Developer's Mailing List</a> is a good place to send them.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]58
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]59<p>Note that if you are reading this file from a Subversion checkout or the main
60 LLVM web page, this document applies to the <i>next</i> release, not the
61 current one. To see the release notes for a specific release, please see the
62 <a href="http://llvm.org/releases/">releases page</a>.</p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]63
64</div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]65
66
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]67<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]68<h2>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]69 <a name="subproj">Sub-project Status Update</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]70</h2>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]71<!-- *********************************************************************** -->
Chris Lattnerea34f642008-06-08 21:34:41 +0000[diff] [blame]72
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]73<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]74
75<p>The LLVM 3.0 distribution currently consists of code from the core LLVM
76 repository (which roughly includes the LLVM optimizers, code generators and
Chris Lattnerc343e312011-11-10 20:15:40 +0000[diff] [blame]77 supporting tools), and the Clang repository. In
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]78 addition to this code, the LLVM Project includes other sub-projects that are
79 in development. Here we include updates on these subprojects.</p>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]80
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]81<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]82<h3>
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]83<a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]84</h3>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]85
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]86<div>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]87
Chris Lattner095539f2010-04-26 17:42:18 +0000[diff] [blame]88<p><a href="http://clang.llvm.org/">Clang</a> is an LLVM front end for the C,
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]89 C++, and Objective-C languages. Clang aims to provide a better user
90 experience through expressive diagnostics, a high level of conformance to
91 language standards, fast compilation, and low memory use. Like LLVM, Clang
92 provides a modular, library-based architecture that makes it suitable for
93 creating or integrating with other development tools. Clang is considered a
94 production-quality compiler for C, Objective-C, C++ and Objective-C++ on x86
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]95 (32- and 64-bit), and for Darwin/ARM targets.</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]96
Chandler Carruthcc966de2011-11-29 00:32:43 +0000[diff] [blame]97<p>In the LLVM 3.0 time-frame, the Clang team has made many improvements:
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]98<ul>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]99 <li>Greatly improved support for building C++ applications, with greater
100 stability and better diagnostics.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]101
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]102 <li><a href="http://clang.llvm.org/cxx_status.html">Improved support</a> for
103 the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50372">C++
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]104 2011</a> standard (aka "C++'0x"), including implementations of non-static data member
105 initializers, alias templates, delegating constructors, range-based
106 for loops, and implicitly-generated move constructors and move assignment
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]107 operators, among others.</li>
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]108
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]109 <li>Implemented support for some features of the upcoming C1x standard,
110 including static assertions and generic selections.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]111
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]112 <li>Better detection of include and linking paths for system headers and
113 libraries, especially for Linux distributions.</li>
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]114
David Chisnall553284e2011-11-26 10:56:17 +0000[diff] [blame]115 <li>Several improvements to Objective-C support, including:
116
117 <ul>
118 <li><a href="http://clang.llvm.org/docs/AutomaticReferenceCounting.html">
119 Automatic Reference Counting</a> (ARC) and an improved memory model
120 cleanly separating object and C memory.</li>
121
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]122 <li>A migration tool for moving manual retain/release code to ARC</li>
David Chisnall553284e2011-11-26 10:56:17 +0000[diff] [blame]123
124 <li>Better support for data hiding, allowing instance variables to be
125 declared in implementation contexts or class extensions</li>
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]126 <li>Weak linking support for Objective-C classes</li>
David Chisnall553284e2011-11-26 10:56:17 +0000[diff] [blame]127 <li>Improved static type checking by inferring the return type of methods
128 such as +alloc and -init.</li>
129 </ul>
130
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]131 Some new Objective-C features require either the Mac OS X 10.7 / iOS 5
132 Objective-C runtime, or version 1.6 or later of the GNUstep Objective-C
133 runtime version.</li>
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]134
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]135 <li>Implemented a number of optimizations in <tt>libclang</tt>, the Clang C
136 interface, to improve the performance of code completion and the mapping
137 from source locations to abstract syntax tree nodes.</li>
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]138</ul>
Chandler Carruthcc966de2011-11-29 00:32:43 +0000[diff] [blame]139For more details about the changes to Clang since the 2.9 release, see the
140<a href="http://clang.llvm.org/docs/ReleaseNotes.html">Clang release notes</a>
141</p>
Douglas Gregorba087df2011-10-15 00:48:01 +0000[diff] [blame]142
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]143
Duncan Sandsf3ba7af2011-04-06 08:07:40 +0000[diff] [blame]144<p>If Clang rejects your code but another compiler accepts it, please take a
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]145 look at the <a href="http://clang.llvm.org/compatibility.html">language
146 compatibility</a> guide to make sure this is not intentional or a known
147 issue.</p>
Bill Wendling741748a2008-10-27 09:27:33 +0000[diff] [blame]148
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]149</div>
150
151<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]152<h3>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]153<a name="dragonegg">DragonEgg: GCC front-ends, LLVM back-end</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]154</h3>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]155
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]156<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]157<p><a href="http://dragonegg.llvm.org/">DragonEgg</a> is a
158 <a href="http://gcc.gnu.org/wiki/plugins">gcc plugin</a> that replaces GCC's
Duncan Sands77352c92011-11-10 18:44:29 +0000[diff] [blame]159 optimizers and code generators with LLVM's. It works with gcc-4.5 or gcc-4.6,
160 targets the x86-32 and x86-64 processor families, and has been successfully
161 used on the Darwin, FreeBSD, KFreeBSD, Linux and OpenBSD platforms. It fully
162 supports Ada, C, C++ and Fortran. It has partial support for Go, Java, Obj-C
163 and Obj-C++.</p>
Duncan Sands749fd832010-04-02 09:23:15 +0000[diff] [blame]164
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]165<p>The 3.0 release has the following notable changes:</p>
166
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]167 <ul>
Duncan Sands77352c92011-11-10 18:44:29 +0000[diff] [blame]168 <li>GCC version 4.6 is now fully supported.</li>
169
170 <li>Patching and building GCC is no longer required: the plugin should work
171 with your system GCC (version 4.5 or 4.6; on Debian/Ubuntu systems the
172 gcc-4.5-plugin-dev or gcc-4.6-plugin-dev package is also needed).</li>
173
174 <li>The <tt>-fplugin-arg-dragonegg-enable-gcc-optzns</tt> option, which runs
175 GCC's optimizers as well as LLVM's, now works much better. This is the
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]176 option to use if you want ultimate performance! It is still experimental
177 though: it may cause the plugin to crash.</li>
Duncan Sands77352c92011-11-10 18:44:29 +0000[diff] [blame]178
179 <li>The type and constant conversion logic has been almost entirely rewritten,
180 fixing a multitude of obscure bugs.</li>
181
Duncan Sands4b1da2b2010-09-30 17:37:34 +0000[diff] [blame]182</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]183
184</div>
185
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]186<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]187<h3>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]188<a name="compiler-rt">compiler-rt: Compiler Runtime Library</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]189</h3>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]190
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]191<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]192
193<p>The new LLVM <a href="http://compiler-rt.llvm.org/">compiler-rt project</a>
194 is a simple library that provides an implementation of the low-level
195 target-specific hooks required by code generation and other runtime
196 components. For example, when compiling for a 32-bit target, converting a
197 double to a 64-bit unsigned integer is compiled into a runtime call to the
198 "__fixunsdfdi" function. The compiler-rt library provides highly optimized
199 implementations of this and other low-level routines (some are 3x faster than
200 the equivalent libgcc routines).</p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]201
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]202<p>In the LLVM 3.0 timeframe, the target specific ARM code has converted to
203 "unified" assembly syntax, and several new functions have been added to the
204 library.</p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]205
206</div>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]207
208<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]209<h3>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]210<a name="lldb">LLDB: Low Level Debugger</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]211</h3>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]212
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]213<div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]214
Chris Lattner9e896712011-11-27 18:53:41 +0000[diff] [blame]215<p>LLDB is a ground-up implementation of a command line debugger, as well as a
216 debugger API that can be used from other applications. LLDB makes use of the
217 Clang parser to provide high-fidelity expression parsing (particularly for
218 C++) and uses the LLVM JIT for target support.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]219
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]220<p>LLDB has advanced by leaps and bounds in the 3.0 timeframe. It is
221 dramatically more stable and useful, and includes both a
222 new <a href="http://lldb.llvm.org/tutorial.html">tutorial</a> and
223 a <a href="http://lldb.llvm.org/lldb-gdb.html">side-by-side comparison with
224 GDB</a>.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]225
226</div>
227
228<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]229<h3>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]230<a name="libc++">libc++: C++ Standard Library</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]231</h3>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]232
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]233<div>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]234
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]235<p>Like compiler_rt, libc++ is now <a href="DeveloperPolicy.html#license">dual
236 licensed</a> under the MIT and UIUC license, allowing it to be used more
237 permissively.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]238
David Chisnall553284e2011-11-26 10:56:17 +0000[diff] [blame]239<p>Libc++ has been ported to FreeBSD and imported into the base system. It is
240 planned to be the default STL implementation for FreeBSD 10.</p>
241
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]242</div>
243
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]244<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]245<h3>
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]246<a name="vmkit">VMKit</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]247</h3>
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]248
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]249<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]250
Nicolas Geoffray54d5df92011-11-10 23:37:56 +0000[diff] [blame]251 <p>The <a href="http://vmkit.llvm.org/">VMKit project</a> is an
252 implementation of a Java Virtual Machine (Java VM or JVM) that uses LLVM for
253 static and just-in-time compilation.
254
255 <p>In the LLVM 3.0 time-frame, VMKit has had significant improvements on both
256 runtime and startup performance:</p>
257
258 <ul>
259 <li>Precompilation: by compiling ahead of time a small subset of Java's core
260 library, the startup performance have been highly optimized to the point that
261 running a 'Hello World' program takes less than 30 milliseconds.</li>
262
263 <li>Customization: by customizing virtual methods for individual classes,
264 the VM can statically determine the target of a virtual call, and decide to
265 inline it.</li>
266
267 <li>Inlining: the VM does more inlining than it did before, by allowing more
268 bytecode instructions to be inlined, and thanks to customization. It also
269 inlines GC barriers, and object allocations.</li>
270
271 <li>New exception model: the generated code for a method that does not do
272 any try/catch is not penalized anymore by the eventuality of calling a
273 method that throws an exception. Instead, the method that throws the
274 exception jumps directly to the method that could catch it.</li>
275 </ul>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]276
Chris Lattner3d6a80a2011-04-07 03:08:22 +0000[diff] [blame]277</div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]278
Chris Lattner9e896712011-11-27 18:53:41 +0000[diff] [blame]279
280<!--=========================================================================-->
281<h3>
282<a name="LLBrowse">LLBrowse: IR Browser</a>
283</h3>
284
285<div>
286
287<p><a href="http://llvm.org/svn/llvm-project/llbrowse/trunk/doc/LLBrowse.html">
288 LLBrowse</a> is an interactive viewer for LLVM modules. It can load any LLVM
289 module and displays its contents as an expandable tree view, facilitating an
290 easy way to inspect types, functions, global variables, or metadata nodes. It
291 is fully cross-platform, being based on the popular wxWidgets GUI
292 toolkit.</p>
293
294</div>
295
296
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]297<!--=========================================================================-->
Chris Lattner7a8e6c52011-04-05 18:38:45 +0000[diff] [blame]298<!--
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]299<h3>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]300<a name="klee">KLEE: A Symbolic Execution Virtual Machine</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]301</h3>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]302
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]303<div>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]304<p>
305<a href="http://klee.llvm.org/">KLEE</a> is a symbolic execution framework for
306programs in LLVM bitcode form. KLEE tries to symbolically evaluate "all" paths
307through the application and records state transitions that lead to fault
308states. This allows it to construct testcases that lead to faults and can even
309be used to verify some algorithms.
310</p>
311
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]312<p>UPDATE!</p>
Chris Lattner7a8e6c52011-04-05 18:38:45 +0000[diff] [blame]313</div>-->
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]314
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]315</div>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]316
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]317<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]318<h2>
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]319 <a name="externalproj">External Open Source Projects Using LLVM 3.0</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]320</h2>
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]321<!-- *********************************************************************** -->
322
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]323<div>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]324
325<p>An exciting aspect of LLVM is that it is used as an enabling technology for
326 a lot of other language and tools projects. This section lists some of the
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]327 projects that have already been updated to work with LLVM 3.0.</p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]328
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]329<!--=========================================================================-->
Bill Wendling7be6bc52011-10-26 00:17:54 +0000[diff] [blame]330<h3>AddressSanitizer</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]331
Bill Wendling7be6bc52011-10-26 00:17:54 +0000[diff] [blame]332<div>
333
334<p><a href="http://code.google.com/p/address-sanitizer/">AddressSanitizer</a>
335 uses compiler instrumentation and a specialized malloc library to find C/C++
336 bugs such as use-after-free and out-of-bound accesses to heap, stack, and
337 globals. The key feature of the tool is speed: the average slowdown
338 introduced by AddressSanitizer is less than 2x.</p>
339
340</div>
341
342<!--=========================================================================-->
Bill Wendling29817ea2011-10-26 00:14:36 +0000[diff] [blame]343<h3>ClamAV</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]344
Bill Wendling29817ea2011-10-26 00:14:36 +0000[diff] [blame]345<div>
Bill Wendlingf2a78332011-10-25 01:01:42 +0000[diff] [blame]346
Bill Wendling29817ea2011-10-26 00:14:36 +0000[diff] [blame]347<p><a href="http://www.clamav.net">Clam AntiVirus</a> is an open source (GPL)
348 anti-virus toolkit for UNIX, designed especially for e-mail scanning on mail
349 gateways.</p>
350
351<p>Since version 0.96 it
352 has <a href="http://vrt-sourcefire.blogspot.com/2010/09/introduction-to-clamavs-low-level.html">bytecode
Chris Lattner4f0fe432011-11-27 19:26:30 +0000[diff] [blame]353 signatures</a> that allow writing detections for complex malware.
354 It uses LLVM's JIT to speed up the execution of bytecode on X86, X86-64,
Bill Wendling29817ea2011-10-26 00:14:36 +0000[diff] [blame]355 PPC32/64, falling back to its own interpreter otherwise. The git version was
356 updated to work with LLVM 3.0.</p>
357
358</div>
359
360<!--=========================================================================-->
Tobias Grosserae5a6fd2011-11-14 09:09:26 +0000[diff] [blame]361<h3>clang_complete for VIM</h3>
362
363<div>
364
365<p><a href="https://github.com/Rip-Rip/clang_complete">clang_complete</a> is a
366 VIM plugin, that provides accurate C/C++ autocompletion using the clang front
367 end. The development version of clang complete, can directly use libclang
368 which can maintain a cache to speed up auto completion.</p>
369
370</div>
371
372<!--=========================================================================-->
Bill Wendling65d1f412011-10-26 18:23:06 +0000[diff] [blame]373<h3>clReflect</h3>
374
375<div>
376
377<p><a href="https://bitbucket.org/dwilliamson/clreflect">clReflect</a> is a C++
378 parser that uses clang/LLVM to derive a light-weight reflection database
379 suitable for use in game development. It comes with a very simple runtime
380 library for loading and querying the database, requiring no external
381 dependencies (including CRT), and an additional utility library for object
382 management and serialisation.</p>
383
384</div>
385
386<!--=========================================================================-->
Bill Wendling63507d12011-10-29 01:10:01 +0000[diff] [blame]387<h3>Cling C++ Interpreter</h3>
388
389<div>
390
391<p><a href="http://cern.ch/cling">Cling</a> is an interactive compiler interface
Chris Lattner4f0fe432011-11-27 19:26:30 +0000[diff] [blame]392 (aka C++ interpreter). It supports C++ and C, and uses LLVM's JIT and the
393 Clang parser. It has a prompt interface, runs source files, calls into shared
Bill Wendling63507d12011-10-29 01:10:01 +0000[diff] [blame]394 libraries, prints the value of expressions, even does runtime lookup of
395 identifiers (dynamic scopes). And it just behaves like one would expect from
396 an interpreter.</p>
397
398</div>
399
400<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]401<h3>Crack Programming Language</h3>
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]402
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]403<div>
Bill Wendling55d6e672011-11-03 20:10:01 +0000[diff] [blame]404
405<p><a href="http://code.google.com/p/crack-language/">Crack</a> aims to provide
406 the ease of development of a scripting language with the performance of a
407 compiled language. The language derives concepts from C++, Java and Python,
408 incorporating object-oriented programming, operator overloading and strong
409 typing.</p>
410
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]411</div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]412
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]413<!--=========================================================================-->
Bill Wendlingb99486f2011-11-08 05:22:54 +0000[diff] [blame]414<h3>Eero</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]415
Bill Wendlingb99486f2011-11-08 05:22:54 +0000[diff] [blame]416<div>
417
418<p><a href="http://eerolanguage.org/">Eero</a> is a fully
419 header-and-binary-compatible dialect of Objective-C 2.0, implemented with a
420 patched version of the Clang/LLVM compiler. It features a streamlined syntax,
421 Python-like indentation, and new operators, for improved readability and
422 reduced code clutter. It also has new features such as limited forms of
423 operator overloading and namespaces, and strict (type-and-operator-safe)
424 enumerations. It is inspired by languages such as Smalltalk, Python, and
425 Ruby.</p>
426
427</div>
428
429<!--=========================================================================-->
Chris Lattneradb417a2011-11-25 20:28:16 +0000[diff] [blame]430<h3>FAUST Real-Time Audio Signal Processing Language</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]431
Chris Lattneradb417a2011-11-25 20:28:16 +0000[diff] [blame]432<div>
433
434<p><a href="http://faust.grame.fr/">FAUST</a> is a compiled language for
435 real-time audio signal processing. The name FAUST stands for Functional
436 AUdio STream. Its programming model combines two approaches: functional
437 programming and block diagram composition. In addition with the C, C++, Java
438 output formats, the Faust compiler can now generate LLVM bitcode, and works
439 with LLVM 2.7-3.0.
440 </p>
441
442</div>
443
444<!--=========================================================================-->
Bill Wendlingf9778192011-10-26 00:09:55 +0000[diff] [blame]445<h3>Glasgow Haskell Compiler (GHC)</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]446
Bill Wendlingf9778192011-10-26 00:09:55 +0000[diff] [blame]447<div>
448
449<p>GHC is an open source, state-of-the-art programming suite for Haskell, a
450 standard lazy functional programming language. It includes an optimizing
451 static compiler generating good code for a variety of platforms, together
452 with an interactive system for convenient, quick development.</p>
453
454<p>GHC 7.0 and onwards include an LLVM code generator, supporting LLVM 2.8 and
455 later. Since LLVM 2.9, GHC now includes experimental support for the ARM
456 platform with LLVM 3.0.</p>
457
458</div>
459
460<!--=========================================================================-->
Bill Wendlingf62333d2011-10-25 20:35:31 +0000[diff] [blame]461<h3>gwXscript</h3>
462
463<div>
464
465<p><a href="http://botwars.tk/gwscript/">gwXscript</a> is an object oriented,
Bill Wendling7c38de22011-10-26 04:24:15 +0000[diff] [blame]466 aspect oriented programming language which can create both executables (ELF,
Bill Wendlingf62333d2011-10-25 20:35:31 +0000[diff] [blame]467 EXE) and shared libraries (DLL, SO, DYNLIB). The compiler is implemented in
468 its own language and translates scripts into LLVM-IR which can be optimized
469 and translated into native code by the LLVM framework. Source code in
470 gwScript contains definitions that expand the namespaces. So you can build
471 your project and simply 'plug out' features by removing a file. The remaining
472 project does not leave scars since you directly separate concerns by the
473 'template' feature of gwX. It is also possible to add new features to a
474 project by just adding files and without editing the original project. This
475 language is used for example to create games or content management systems
476 that should be extendable.</p>
477
478<p>gwXscript is strongly typed and offers comfort with its native types string,
479 hash and array. You can easily write new libraries in gwXscript or native
480 code. gwXscript is type safe and users should not be able to crash your
481 program or execute malicious code except code that is eating CPU time.</p>
482
483</div>
484
485<!--=========================================================================-->
Bill Wendling50cacc82011-10-26 22:55:18 +0000[diff] [blame]486<h3>include-what-you-use</h3>
487
488<div>
489
490<p><a href="http://code.google.com/p/include-what-you-use">include-what-you-use</a>
491 is a tool to ensure that a file directly <code>#include</code>s
492 all <code>.h</code> files that provide a symbol that the file uses. It also
493 removes superfluous <code>#include</code>s from source files.</p>
494
495</div>
496
497<!--=========================================================================-->
Bill Wendling32dc4d92011-11-07 22:05:17 +0000[diff] [blame]498<h3>ispc: The Intel SPMD Program Compiler</h3>
499
500<div>
501
502<p><a href="http://ispc.github.com">ispc</a> is a compiler for "single program,
503 multiple data" (SPMD) programs. It compiles a C-based SPMD programming
504 language to run on the SIMD units of CPUs; it often delivers 5-6x speedups on
505 a single core of a CPU with an 8-wide SIMD unit compared to serial code,
506 while still providing a clean and easy-to-understand programming model. For
507 an introduction to the language and its performance,
Chris Lattnerc343e312011-11-10 20:15:40 +0000[diff] [blame]508 see <a href="http://ispc.github.com/example.html">the walkthrough</a> of a short
Bill Wendling32dc4d92011-11-07 22:05:17 +0000[diff] [blame]509 example program. ispc is licensed under the BSD license.</p>
510
511</div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]512
Chris Lattnercc089772011-11-25 20:36:17 +0000[diff] [blame]513<!--=========================================================================-->
514<h3>The Julia Programming Language</h3>
515
516<div>
517
518<p><a href="http://github.com/JuliaLang/julia">Julia</a> is a high-level,
519 high-performance dynamic language for technical
520 computing. It provides a sophisticated compiler, distributed parallel
521 execution, numerical accuracy, and an extensive mathematical function
522 library. The compiler uses type inference to generate fast code
523 without any type declarations, and uses LLVM's optimization passes and
524 JIT compiler. The language is designed around multiple dispatch,
525 giving programs a large degree of flexibility. It is ready for use on many
526 kinds of problems.</p>
527</div>
Bill Wendling32dc4d92011-11-07 22:05:17 +0000[diff] [blame]528
529<!--=========================================================================-->
Bill Wendling57fd8762011-10-26 18:20:54 +0000[diff] [blame]530<h3>LanguageKit and Pragmatic Smalltalk</h3>
531
532<div>
533
534<p><a href="http://etoileos.com/etoile/features/languagekit/">LanguageKit</a> is
535 a framework for implementing dynamic languages sharing an object model with
536 Objective-C. It provides static and JIT compilation using LLVM along with
537 its own interpreter. Pragmatic Smalltalk is a dialect of Smalltalk, built on
538 top of LanguageKit, that interfaces directly with Objective-C, sharing the
539 same object representation and message sending behaviour. These projects are
Benjamin Kramer7c5025b2011-11-25 21:26:00 +0000[diff] [blame]540 developed as part of the &Eacute;toil&eacute; desktop environment.</p>
Bill Wendling57fd8762011-10-26 18:20:54 +0000[diff] [blame]541
542</div>
543
544<!--=========================================================================-->
Bill Wendling03250532011-11-01 04:08:23 +0000[diff] [blame]545<h3>LuaAV</h3>
546
547<div>
548
549<p><a href="http://lua-av.mat.ucsb.edu/blog/">LuaAV</a> is a real-time
550 audiovisual scripting environment based around the Lua language and a
551 collection of libraries for sound, graphics, and other media protocols. LuaAV
552 uses LLVM and Clang to JIT compile efficient user-defined audio synthesis
553 routines specified in a declarative syntax.</p>
554
555</div>
556
557<!--=========================================================================-->
Bill Wendlingd4821b82011-10-26 00:16:17 +0000[diff] [blame]558<h3>Mono</h3>
559
560<div>
561
562<p>An open source, cross-platform implementation of C# and the CLR that is
563 binary compatible with Microsoft.NET. Has an optional, dynamically-loaded
564 LLVM code generation backend in Mini, the JIT compiler.</p>
565
Chris Lattner4f0fe432011-11-27 19:26:30 +0000[diff] [blame]566<p>Note that we use a Git mirror of LLVM <a
567 href="https://github.com/mono/llvm">with some patches</a>.</p>
Bill Wendlingd4821b82011-10-26 00:16:17 +0000[diff] [blame]568
569</div>
570
571<!--=========================================================================-->
Tobias Grosser093cb7e2011-11-14 09:09:23 +0000[diff] [blame]572<h3>Polly</h3>
573
574<div>
575
576<p><a href="http://polly.grosser.es">Polly</a> is an advanced data-locality
577 optimizer and automatic parallelizer. It uses an advanced, mathematical
578 model to calculate detailed data dependency information which it uses to
579 optimize the loop structure of a program. Polly can speed up sequential code
580 by improving memory locality and consequently the cache use. Furthermore,
581 Polly is able to expose different kind of parallelism which it exploits by
582 introducing (basic) OpenMP and SIMD code. A mid-term goal of Polly is to
583 automatically create optimized GPU code.</p>
584
585</div>
586
587<!--=========================================================================-->
Bill Wendlingba226272011-10-25 20:37:45 +0000[diff] [blame]588<h3>Portable OpenCL (pocl)</h3>
589
590<div>
591
592<p>Portable OpenCL is an open source implementation of the OpenCL standard which
593 can be easily adapted for new targets. One of the goals of the project is
594 improving performance portability of OpenCL programs, avoiding the need for
595 target-dependent manual optimizations. A "native" target is included, which
596 allows running OpenCL kernels on the host (CPU).</p>
597
598</div>
599
600<!--=========================================================================-->
Bill Wendling0bad98c2011-10-25 20:39:06 +0000[diff] [blame]601<h3>Pure</h3>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]602
Bill Wendling0bad98c2011-10-25 20:39:06 +0000[diff] [blame]603<div>
604<p><a href="http://pure-lang.googlecode.com/">Pure</a> is an
605 algebraic/functional programming language based on term rewriting. Programs
606 are collections of equations which are used to evaluate expressions in a
607 symbolic fashion. The interpreter uses LLVM as a backend to JIT-compile Pure
608 programs to fast native code. Pure offers dynamic typing, eager and lazy
609 evaluation, lexical closures, a hygienic macro system (also based on term
610 rewriting), built-in list and matrix support (including list and matrix
611 comprehensions) and an easy-to-use interface to C and other programming
612 languages (including the ability to load LLVM bitcode modules, and inline C,
613 C++, Fortran and Faust code in Pure programs if the corresponding LLVM-enabled
614 compilers are installed).</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]615
Bill Wendling0bad98c2011-10-25 20:39:06 +0000[diff] [blame]616<p>Pure version 0.48 has been tested and is known to work with LLVM 3.0
617 (and continues to work with older LLVM releases &gt;= 2.5).</p>
618
619</div>
620
621<!--=========================================================================-->
Bill Wendling537d85b2011-10-26 00:12:04 +0000[diff] [blame]622<h3>Renderscript</h3>
623
624<div>
625
626<p><a href="http://developer.android.com/guide/topics/renderscript/index.html">Renderscript</a>
627 is Android's advanced 3D graphics rendering and compute API. It provides a
628 portable C99-based language with extensions to facilitate common use cases
629 for enhancing graphics and thread level parallelism. The Renderscript
630 compiler frontend is based on Clang/LLVM. It emits a portable bitcode format
631 for the actual compiled script code, as well as reflects a Java interface for
632 developers to control the execution of the compiled bitcode. Executable
633 machine code is then generated from this bitcode by an LLVM backend on the
634 device. Renderscript is thus able to provide a mechanism by which Android
635 developers can improve performance of their applications while retaining
636 portability.</p>
637
638</div>
639
640<!--=========================================================================-->
Bill Wendling7d5b6212011-10-25 20:40:26 +0000[diff] [blame]641<h3>SAFECode</h3>
642
643<div>
644
645<p><a href="http://safecode.cs.illinois.edu">SAFECode</a> is a memory safe C/C++
646 compiler built using LLVM. It takes standard, unannotated C/C++ code,
647 analyzes the code to ensure that memory accesses and array indexing
648 operations are safe, and instruments the code with run-time checks when
649 safety cannot be proven statically. SAFECode can be used as a debugging aid
650 (like Valgrind) to find and repair memory safety bugs. It can also be used
651 to protect code from security attacks at run-time.</p>
652
653</div>
654
655<!--=========================================================================-->
Bill Wendling02b77b72011-10-26 07:38:19 +0000[diff] [blame]656<h3>The Stupid D Compiler (SDC)</h3>
657
658<div>
659
660<p><a href="https://github.com/bhelyer/SDC">The Stupid D Compiler</a> is a
661 project seeking to write a self-hosting compiler for the D programming
662 language without using the frontend of the reference compiler (DMD).</p>
663
664</div>
665
666<!--=========================================================================-->
Bill Wendling2d7b4af2011-10-25 20:24:32 +0000[diff] [blame]667<h3>TTA-based Co-design Environment (TCE)</h3>
668
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]669<div>
Bill Wendling2d7b4af2011-10-25 20:24:32 +0000[diff] [blame]670
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]671<p>TCE is a toolset for designing application-specific processors (ASP) based on
Bill Wendling2d7b4af2011-10-25 20:24:32 +0000[diff] [blame]672 the Transport triggered architecture (TTA). The toolset provides a complete
673 co-design flow from C/C++ programs down to synthesizable VHDL and parallel
674 program binaries. Processor customization points include the register files,
675 function units, supported operations, and the interconnection network.</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]676
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]677<p>TCE uses Clang and LLVM for C/C++ language support, target independent
Bill Wendling2d7b4af2011-10-25 20:24:32 +0000[diff] [blame]678 optimizations and also for parts of code generation. It generates new
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]679 LLVM-based code generators "on the fly" for the designed TTA processors and
680 loads them in to the compiler backend as runtime libraries to avoid
Bill Wendling2d7b4af2011-10-25 20:24:32 +0000[diff] [blame]681 per-target recompilation of larger parts of the compiler chain.</p>
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]682
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]683</div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]684
Chris Lattner3bfe57e2011-04-06 01:13:49 +0000[diff] [blame]685<!--=========================================================================-->
Bill Wendling628c2662011-10-25 20:27:37 +0000[diff] [blame]686<h3>Tart Programming Language</h3>
687
688<div>
689
690<p><a href="http://code.google.com/p/tart/">Tart</a> is a general-purpose,
691 strongly typed programming language designed for application
692 developers. Strongly inspired by Python and C#, Tart focuses on practical
693 solutions for the professional software developer, while avoiding the clutter
694 and boilerplate of legacy languages like Java and C++. Although Tart is still
695 in development, the current implementation supports many features expected of
696 a modern programming language, such as garbage collection, powerful
697 bidirectional type inference, a greatly simplified syntax for template
698 metaprogramming, closures and function literals, reflection, operator
699 overloading, explicit mutability and immutability, and much more. Tart is
700 flexible enough to accommodate a broad range of programming styles and
701 philosophies, while maintaining a strong commitment to simplicity, minimalism
702 and elegance in design.</p>
703
704</div>
705
706<!--=========================================================================-->
Bill Wendling644ce532011-10-26 09:25:01 +0000[diff] [blame]707<h3>ThreadSanitizer</h3>
708
709<div>
710
711<p><a href="http://code.google.com/p/data-race-test/">ThreadSanitizer</a> is a
712 data race detector for (mostly) C and C++ code, available for Linux, Mac OS
713 and Windows. On different systems, we use binary instrumentation frameworks
Bill Wendlingae8538e2011-10-29 01:11:15 +0000[diff] [blame]714 (Valgrind and Pin) as frontends that generate the program events for the race
715 detection algorithm. On Linux, there's an option of using LLVM-based
716 compile-time instrumentation.</p>
Bill Wendling644ce532011-10-26 09:25:01 +0000[diff] [blame]717
718</div>
719
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]720</div>
721
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]722<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]723<h2>
Chad Rosiere6291d02011-05-27 22:50:46 +0000[diff] [blame]724 <a name="whatsnew">What's New in LLVM 3.0?</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]725</h2>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]726<!-- *********************************************************************** -->
727
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]728<div>
Chris Lattnerf8e0b4e2008-06-08 22:59:35 +0000[diff] [blame]729
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]730<p>This release includes a huge number of bug fixes, performance tweaks and
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]731 minor improvements. Some of the major improvements and new features are
732 listed in this section.</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]733
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]734<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]735<h3>
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]736<a name="majorfeatures">Major New Features</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]737</h3>
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]738
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]739<div>
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]740
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]741 <!-- Features that need text if they're finished for 3.1:
742 ARM EHABI
743 combiner-aa?
744 strong phi elim
745 loop dependence analysis
746 CorrelatedValuePropagation
747 lib/Transforms/IPO/MergeFunctions.cpp => consider for 3.1.
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]748 Integrated assembler on by default for arm/thumb?
749
Chris Lattner1ab8ce92011-11-27 18:47:37 +0000[diff] [blame]750 -->
751
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]752 <!-- Near dead:
Chris Lattnerdec23b62011-11-15 22:13:27 +0000[diff] [blame]753 Analysis/RegionInfo.h + Dom Frontiers
754 SparseBitVector: used in LiveVar.
Chris Lattner5a1731d2011-11-27 08:32:32 +0000[diff] [blame]755 llvm/lib/Archive - replace with lib object?
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]756 -->
Chris Lattner6a007d12011-11-25 20:33:27 +0000[diff] [blame]757
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]758<p>LLVM 3.0 includes several major changes and big features:</p>
Bill Wendlingbc5f6dd2011-10-26 18:33:01 +0000[diff] [blame]759
Chris Lattner791f77b2008-06-05 06:25:56 +0000[diff] [blame]760<ul>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]761<li>llvm-gcc is no longer supported, and not included in the release. We
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]762 recommend switching to <a
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]763 href="http://clang.llvm.org/">Clang</a> or <a
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]764 href="http://dragonegg.llvm.org/">DragonEgg</a>.</li>
Bill Wendlingbc5f6dd2011-10-26 18:33:01 +0000[diff] [blame]765
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]766<li>The linear scan register allocator has been replaced with a new "greedy"
767 register allocator, enabling live range splitting and many other
768 optimizations that lead to better code quality. Please see its <a
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]769 href="http://blog.llvm.org/2011/09/greedy-register-allocation-in-llvm-30.html">blog post</a> or its talk at the <a
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]770 href="http://llvm.org/devmtg/2011-11/">Developer Meeting</a>
771 for more information.</li>
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]772<li>LLVM IR now includes full support for <a href="Atomics.html">atomics
773 memory operations</a> intended to support the C++'11 and C'1x memory models.
774 This includes <a href="LangRef.html#memoryops">atomic load and store,
775 compare and exchange, and read/modify/write instructions</a> as well as a
776 full set of <a href="LangRef.html#ordering">memory ordering constraints</a>.
777 Please see the <a href="Atomics.html">Atomics Guide</a> for more
778 information.
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]779</li>
780<li>The LLVM IR exception handling representation has been redesigned and
781 reimplemented, making it more elegant, fixing a huge number of bugs, and
782 enabling inlining and other optimizations. Please see its blog post (XXX
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]783 not yet) and the <a href="ExceptionHandling.html">Exception Handling
784 documentation</a> for more information.</li>
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]785<li>The LLVM IR Type system has been redesigned and reimplemented, making it
786 faster and solving some long-standing problems.
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]787 Please see its <a
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]788 href="http://blog.llvm.org/2011/11/llvm-30-type-system-rewrite.html">blog
789 post</a> for more information.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]790
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]791<li>The MIPS backend has made major leaps in this release, going from an
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]792 experimental target to being virtually production quality and supporting a
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]793 wide variety of MIPS subtargets. See the <a href="#MIPS">MIPS section</a>
794 below for more information.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]795
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]796<li>The optimizer and code generator now supports gprof and gcov-style coverage
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]797 and profiling information, and includes a new llvm-cov tool (but also works
798 with gcov). Clang exposes coverage and profiling through GCC-compatible
799 command line options.</li>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]800</ul>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]801
Bill Wendlingbc5f6dd2011-10-26 18:33:01 +0000[diff] [blame]802</div>
803
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]804
Chris Lattner4f0fe432011-11-27 19:26:30 +0000[diff] [blame]805<!--=========================================================================-->
806<h3>
807<a name="coreimprovements">LLVM IR and Core Improvements</a>
808</h3>
809
810<div>
811
812<p>LLVM IR has several new features for better support of new targets and that
813 expose new optimization opportunities:</p>
814
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]815 <ul>
816 <li><a href="Atomics.html">Atomic memory accesses and memory ordering</a> are
817 now directly expressible in the IR.</li>
818 <li>A new <a href="LangRef.html#int_fma">llvm.fma intrinsic</a> directly
819 represents floating point multiply accumulate operations without an
820 intermediate rounding stage.</li>
821 <li>A new llvm.expect intrinsic (XXX not documented in langref) allows a
822 frontend to express expected control flow (and the __builtin_expect builtin
823 from GNU C).</li>
824 <li>The <a href="LangRef.html#int_prefetch">llvm.prefetch intrinsic</a> now
825 takes a 4th argument that specifies whether the prefetch happens from the
826 icache or dcache.</li>
827 <li>The new <a href="LangRef.html#uwtable">uwtable function attribute</a>
828 allows a frontend to control emission of unwind tables.</li>
829 <li>The new <a href="LangRef.html#fnattrs">nonlazybind function
830 attribute</a> allow optimization of Global Offset Table (GOT) accesses.</li>
831 <li>The new <a href="LangRef.html#returns_twice">returns_twice attribute</a>
832 allows better modeling of functions like setjmp.</li>
833 <li>The <a href="LangRef.html#datalayout">target datalayout</a> string can now
834 encode the natural alignment of the target's stack for better optimization.
835 </li>
836 </ul>
Andrew Trick5aab6382011-11-06 17:59:24 +0000[diff] [blame]837</div>
838
839<!--=========================================================================-->
840<h3>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]841<a name="optimizer">Optimizer Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]842</h3>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]843
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]844<div>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]845
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]846<p>In addition to many minor performance tweaks and bug fixes, this
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]847 release includes a few major enhancements and additions to the
848 optimizers:</p>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]849
850<ul>
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]851<li>The pass manager now has an extension API that allows front-ends and plugins
852 to insert their own optimizations in the well-known places in the standard
853 pass optimization pipeline.</li>
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]854
Benjamin Kramer933a78c2011-11-26 11:14:54 +0000[diff] [blame]855<li>Information about <a href="BranchWeightMetadata.html">branch probability</a>
856 and basic block frequency is now available within LLVM, based on a
857 combination of static branch prediction heuristics and
858 <code>__builtin_expect</code> calls. That information is currently used for
859 register spill placement and if-conversion, with additional optimizations
860 planned for future releases. The same framework is intended for eventual
861 use with profile-guided optimization.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]862
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]863<li>The "-indvars" induction variable simplification pass only modifies
864 induction variables when profitable. Sign and zero extension
865 elimination, linear function test replacement, loop unrolling, and
866 other simplifications that require induction variable analysis have
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]867 been generalized so they no longer require loops to be rewritten into
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]868 canonical form prior to optimization. This new design
869 preserves more IR level information, avoids undoing earlier loop
870 optimizations (particularly hand-optimized loops), and no longer
871 requires the code generator to reconstruct loops into an optimal form -
872 an intractable problem.</li>
873
874<li>LLVM now includes a pass to optimize retain/release calls for the
875 <a href="http://clang.llvm.org/docs/AutomaticReferenceCounting.html">Automatic
876 Reference Counting</a> (ARC) Objective-C language feature (in
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]877 lib/Transforms/Scalar/ObjCARC.cpp). It is a decent example of implementing
878 a source-language-specific optimization in LLVM.</li>
Chris Lattner064caf92011-11-27 21:30:28 +0000[diff] [blame]879
Chris Lattner11b66112010-10-04 02:42:39 +0000[diff] [blame]880</ul>
881
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]882</div>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]883
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]884<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]885<h3>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]886<a name="mc">MC Level Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]887</h3>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]888
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]889<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]890
891<p>The LLVM Machine Code (aka MC) subsystem was created to solve a number of
892 problems in the realm of assembly, disassembly, object file format handling,
893 and a number of other related areas that CPU instruction-set level tools work
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]894 in. For more information, please see
895 the <a href="http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html">Intro
896 to the LLVM MC Project Blog Post</a>.</p>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]897
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]898<ul>
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]899 <li>The MC layer has undergone significant refactoring to eliminate layering
900 violations that caused it to pull in the LLVM compiler backend code.</li>
901 <li>The ELF object file writers are much more full featured.</li>
902 <li>The integrated assembler now supports #line directives.</li>
903 <li>An early implementation of a JIT built on top of the MC framework (known
904 as MC-JIT) has been implemented and will eventually replace the old JIT.
905 It emits object files direct to memory and uses a runtime dynamic linker to
906 resolve references and drive lazy compilation. The MC-JIT enables much
907 greater code reuse between the JIT and the static compiler and provides
908 better integration with the platform ABI as a result.
909 </li>
910 <li>The assembly printer now makes uses of assemblers instruction aliases
911 (InstAliases) to print simplified mneumonics when possible.</li>
912 <li>TableGen can now autogenerate MC expansion logic for pseudo
913 instructions that expand to multiple MC instructions (through the
914 PseudoInstExpansion class).</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]915 <li>A new llvm-dwarfdump tool provides a start of a drop-in
916 replacement for the corresponding tool that use LLVM libraries. As part of
Chris Lattner7c224462011-11-27 22:39:23 +0000[diff] [blame]917 this, LLVM has the beginnings of a dwarf parsing library.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]918 <li>llvm-objdump has more output including, symbol by symbol disassembly,
919 inline relocations, section headers, symbol tables, and section contents.
920 Support for archive files has also been added.</li>
921 <li>llvm-nm has gained support for archives of binary files.</li>
922 <li>llvm-size has been added. This tool prints out section sizes.</li>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]923</ul>
924
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame]925</div>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]926
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]927<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]928<h3>
Chris Lattner511433e2009-03-02 03:24:11 +0000[diff] [blame]929<a name="codegen">Target Independent Code Generator Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]930</h3>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]931
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]932<div>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]933
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]934<p>We have put a significant amount of work into the code generator
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]935 infrastructure, which allows us to implement more aggressive algorithms and
936 make it run faster:</p>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]937
938<ul>
Rafael Espindolabdef6fe2011-11-29 19:08:23 +0000[diff] [blame^]939<li>LLVM can now produce code that works with libgcc
940 to <a href="SegmentedStacks.html">dynamically allocate stack
941 segments</a>, as opposed to allocating a worst-case chunk of
942 virtual memory for each thread.</li>
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]943<li>LLVM generates substantially better code for indirect gotos due to a new
944 tail duplication pass, which can be a substantial performance win for
945 interpreter loops that use them.</li>
Rafael Espindola7ca7b532011-11-28 23:55:49 +0000[diff] [blame]946<li>Exception handling and debug frame information is now emitted with CFI
947 directives. This lets the assembler produce more compact info as it knows
948 the final offsets, yielding <a href="http://blog.mozilla.com/respindola/2011/05/12/cfi-directives/">much smaller executables</a> for some C++ applications.
949 If the system assembler doesn't support it, MC exands the directives when
950 the integrated assembler is not used.
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]951</li>
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]952
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]953<li>The code generator now supports vector "select" operations on vector
954 comparisons, turning them into various optimized code sequences (e.g.
955 using the SSE4/AVX "blend" instructions).</li>
Jakob Stoklund Olesen09e61ca2011-11-28 01:46:19 +0000[diff] [blame]956<li>The SSE execution domain fix pass and the ARM NEON move fix pass have been
Jakob Stoklund Olesen87f95dc2011-11-28 18:03:11 +0000[diff] [blame]957 merged to a target independent execution dependency fix pass. This pass is
958 used to select alternative equivalent opcodes in a way that minimizes
959 execution domain crossings. Closely connected instructions are moved to
960 the same execution domain when possible. Targets can override the
961 <code>getExecutionDomain</code> and <code>setExecutionDomain</code> hooks
962 to use the pass.</li>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]963</ul>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]964</div>
965
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]966<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]967<h3>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]968<a name="x86">X86-32 and X86-64 Target Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]969</h3>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]970
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]971<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]972
973<p>New features and major changes in the X86 target include:</p>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]974
975<ul>
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]976<li>The X86 backend, assembler and disassembler now have full support for AVX 1.
977 To enable it pass <code>-mavx</code> to the compiler. AVX2 implementation is
978 underway on mainline.</li>
979<li>The integrated assembler and disassembler now support a broad range of new
980 instructions including Atom, Ivy Bridge, <a
981 href="http://en.wikipedia.org/wiki/SSE4a">SSE4a/BMI</a> instructions, <a
982 href="http://en.wikipedia.org/wiki/RdRand">rdrand</a> and many others.</li>
983<li>The X86 backend now fully supports the <a href="http://llvm.org/PR879">X87
984 floating point stack inline assembly constraints</a>.</li>
985<li>The integrated assembler now supports the <tt>.code32</tt> and
986 <tt>.code64</tt> directives to switch between 32-bit and 64-bit
987 instructions.</li>
988<li>The X86 backend now synthesizes horizontal add/sub instructions from generic
989 vector code when the appropriate instructions are enabled.</li>
990<li>The X86-64 backend generates smaller and faster code at -O0 due to
991 improvements in fast instruction selection.</li>
992<li><a href="http://code.google.com/p/nativeclient/">Native Client</a>
993 subtarget support has been added.</li>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]994
Chris Lattner2f206022011-11-27 22:03:34 +0000[diff] [blame]995<li>The CRC32 intrinsics have been renamed. The intrinsics were previously
996 <code>@llvm.x86.sse42.crc32.[8|16|32]</code>
997 and <code>@llvm.x86.sse42.crc64.[8|64]</code>. They have been renamed to
998 <code>@llvm.x86.sse42.crc32.32.[8|16|32]</code> and
999 <code>@llvm.x86.sse42.crc32.64.[8|64]</code>.</li>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]1000</ul>
1001
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]1002</div>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]1003
1004<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1005<h3>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]1006<a name="ARM">ARM Target Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1007</h3>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]1008
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1009<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1010
1011<p>New features of the ARM target include:</p>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]1012
1013<ul>
Chris Lattner1cc489b2011-11-27 22:12:32 +0000[diff] [blame]1014<li>The ARM backend generates much faster code for Cortex-A9 chips.</li>
1015<li>The ARM backend has improved support for Cortex-M series processors.</li>
1016<li>The ARM inline assembly constraints have been implemented and are now fully
1017 supported.</li>
1018<li>NEON code produced by Clang often runs much faster due to improvements in
1019 the Scalar Replacement of Aggregates pass.</li>
1020<li>The old ARM disassembler is replaced with a new one based on autogenerated
1021 encoding information from ARM .td files.</li>
1022<li>The integrated assembler has made major leaps forward, but is still beta quality in LLVM 3.0.</li>
Bob Wilsone8472772010-09-13 17:39:35 +0000[diff] [blame]1023</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]1024</div>
Chris Lattner7b95c382011-11-15 22:23:46 +0000[diff] [blame]1025
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1026
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1027<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1028<h3>
Akira Hatanaka5381cbf2011-11-15 21:33:05 +0000[diff] [blame]1029<a name="MIPS">MIPS Target Improvements</a>
1030</h3>
1031
1032<div>
1033
Chris Lattner1cc489b2011-11-27 22:12:32 +0000[diff] [blame]1034<p>This release has seen major new work on just about every aspect of the MIPS
1035 backend. Some of the major new features include:</p>
Akira Hatanaka5381cbf2011-11-15 21:33:05 +0000[diff] [blame]1036
1037<ul>
1038 <li>Most MIPS32r1 and r2 instructions are now supported.</li>
1039 <li>LE/BE MIPS32r1/r2 has been tested extensively.</li>
1040 <li>O32 ABI has been fully tested.</li>
1041 <li>MIPS backend has migrated to using the MC infrastructure for assembly printing. Initial support for direct object code emission has been implemented too.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1042 <li>Delay slot filler has been updated. Now it tries to fill delay slots with useful instructions instead of always filling them with NOPs.</li>
Akira Hatanaka5381cbf2011-11-15 21:33:05 +0000[diff] [blame]1043 <li>Support for old-style JIT is complete.</li>
1044 <li>Support for old architectures (MIPS1 and MIPS2) has been removed.</li>
1045 <li>Initial support for MIPS64 has been added.</li>
1046</ul>
1047</div>
Chris Lattner7b95c382011-11-15 22:23:46 +0000[diff] [blame]1048
1049<!--=========================================================================-->
1050<h3>
1051 <a name="PTX">PTX Target Improvements</a>
1052</h3>
1053
1054<div>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1055
Chris Lattner7b95c382011-11-15 22:23:46 +0000[diff] [blame]1056 <p>
1057 The PTX back-end is still experimental, but is fairly usable for compute kernels
1058 in LLVM 3.0. Most scalar arithmetic is implemented, as well as intrinsics to
1059 access the special PTX registers and sync instructions. The major missing
1060 pieces are texture/sampler support and some vector operations.</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1061
Chris Lattner7b95c382011-11-15 22:23:46 +0000[diff] [blame]1062 <p>That said, the backend is already being used for domain-specific languages
Peter Collingbournee6e73622011-11-29 02:04:48 +0000[diff] [blame]1063 and can be used by Clang to
1064 <a href="http://clang.llvm.org/docs/ReleaseNotes.html#opencl">compile OpenCL
1065 C code</a> into PTX.</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1066
Chris Lattner7b95c382011-11-15 22:23:46 +0000[diff] [blame]1067</div>
1068
Akira Hatanaka5381cbf2011-11-15 21:33:05 +0000[diff] [blame]1069<!--=========================================================================-->
1070<h3>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1071<a name="OtherTS">Other Target Specific Improvements</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1072</h3>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]1073
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1074<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1075
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1076<ul>
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1077<li>Many PowerPC improvements have been implemented for ELF targets, including
1078 support for varargs and initial support for direct .o file emission.</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1079
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1080<li>MicroBlaze scheduling itineraries were added that model the
1081 3-stage and the 5-stage pipeline architectures. The 3-stage
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1082 pipeline model can be selected with <code>-mcpu=mblaze3</code>
1083 and the 5-stage pipeline model can be selected with
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1084 <code>-mcpu=mblaze5</code>.</li>
1085
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1086</ul>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1087
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1088</div>
Chris Lattner77d29b12008-06-05 08:02:49 +0000[diff] [blame]1089
1090<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1091<h3>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1092<a name="changes">Major Changes and Removed Features</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1093</h3>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1094
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1095<div>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1096
Bill Wendling2626dba2011-08-03 22:18:20 +0000[diff] [blame]1097<p>If you're already an LLVM user or developer with out-of-tree changes based on
1098 LLVM 2.9, this section lists some "gotchas" that you may run into upgrading
1099 from the previous release.</p>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1100
1101<ul>
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1102<li>LLVM 3.0 removes support for reading LLVM 2.8 and earlier files, and LLVM
1103 3.1 will eliminate support for reading LLVM 2.9 files. Going forward, we
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1104 aim for all future versions of LLVM to read bitcode files and .ll files
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1105 produced by LLVM 3.0.</li>
1106<li>Tablegen has been split into a library, allowing the clang tblgen pieces
Peter Collingbournef0a66052011-11-29 02:04:44 +0000[diff] [blame]1107 to now live in the clang tree. The llvm version has been renamed to
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1108 llvm-tblgen instead of tblgen.</li>
Chris Lattner5a1731d2011-11-27 08:32:32 +0000[diff] [blame]1109 <li>The <code>LLVMC</code> meta compiler driver was removed.</li>
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1110 <li>The unused PostOrder Dominator Frontiers and LowerSetJmp passes were removed.</li>
1111
1112
Rafael Espindolaf940a1a2011-08-30 23:03:45 +0000[diff] [blame]1113 <li>The old <code>TailDup</code> pass was not used in the standard pipeline
1114 and was unable to update ssa form, so it has been removed.
Eli Friedmanf03bb262011-08-12 22:50:01 +0000[diff] [blame]1115 <li>The syntax of volatile loads and stores in IR has been changed to
1116 "<code>load volatile</code>"/"<code>store volatile</code>". The old
1117 syntax ("<code>volatile load</code>"/"<code>volatile store</code>")
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1118 is still accepted, but is now considered deprecated and will be removed in
1119 3.1.</li>
1120 <li>llvm-gcc's frontend tests have been removed from llvm/test/Frontend*, sunk
1121 into the clang and dragonegg testsuites.</li>
Benjamin Kramer7c5025b2011-11-25 21:26:00 +0000[diff] [blame]1122 <li>The old atomic intrinsics (<code>llvm.memory.barrier</code> and
Eli Friedman526e1bb2011-10-26 00:55:23 +0000[diff] [blame]1123 <code>llvm.atomic.*</code>) are now gone. Please use the new atomic
1124 instructions, described in the <a href="Atomics.html">atomics guide</a>.
Chris Lattnerd6cc2c22011-11-27 22:36:22 +0000[diff] [blame]1125 <li>LLVM's configure script doesn't depend on llvm-gcc anymore, eliminating a
1126 strange circular dependence between projects.</li>
Devang Patelb34dd132008-10-14 20:03:43 +0000[diff] [blame]1127</ul>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1128
NAKAMURA Takumi2026de22011-08-22 23:22:05 +0000[diff] [blame]1129<h4>Windows (32-bit)</h4>
1130<div>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1131
NAKAMURA Takumi2026de22011-08-22 23:22:05 +0000[diff] [blame]1132<ul>
1133 <li>On Win32(MinGW32 and MSVC), Windows 2000 will not be supported.
1134 Windows XP or higher is required.</li>
1135</ul>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1136
NAKAMURA Takumi2026de22011-08-22 23:22:05 +0000[diff] [blame]1137</div>
1138
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1139</div>
1140
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1141<!--=========================================================================-->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1142<h3>
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1143<a name="api_changes">Internal API Changes</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1144</h3>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1145
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1146<div>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1147
Chris Lattner1efe27e2011-04-06 00:45:11 +0000[diff] [blame]1148<p>In addition, many APIs have changed in this release. Some of the major
Bill Wendling16005252011-08-02 06:20:17 +0000[diff] [blame]1149 LLVM API changes are:</p>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1150
1151<ul>
Joe Abbey54d3b832011-11-28 22:07:12 +0000[diff] [blame]1152 <li>The biggest and most pervasive change is that the type system has been
1153 rewritten: <code>PATypeHolder</code> and <code>OpaqueType</code> are gone,
1154 and all APIs deal with <code>Type*</code> instead of <code>const
1155 Type*</code>. If you need to create recursive structures, then create a
1156 named structure, and use <code>setBody()</code> when all its elements are
1157 built. Type merging and refining is gone too: named structures are not
1158 merged with other structures, even if their layout is identical. (of
1159 course anonymous structures are still uniqued by layout).</li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1160
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1161 <li><code>PHINode::reserveOperandSpace</code> has been removed. Instead, you
1162 must specify how many operands to reserve space for when you create the
1163 PHINode, by passing an extra argument
1164 into <code>PHINode::Create</code>.</li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1165
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1166 <li>PHINodes no longer store their incoming BasicBlocks as operands. Instead,
1167 the list of incoming BasicBlocks is stored separately, and can be accessed
1168 with new functions <code>PHINode::block_begin</code>
1169 and <code>PHINode::block_end</code>.</li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1170
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1171 <li>Various functions now take an <code>ArrayRef</code> instead of either a
1172 pair of pointers (or iterators) to the beginning and end of a range, or a
1173 pointer and a length. Others now return an <code>ArrayRef</code> instead
1174 of a reference to a <code>SmallVector</code>
1175 or <code>std::vector</code>. These include:
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1176<ul>
1177<!-- Please keep this list sorted. -->
Jay Foada3efbb12011-07-15 08:37:34 +0000[diff] [blame]1178<li><code>CallInst::Create</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1179<li><code>ComputeLinearIndex</code> (in <code>llvm/CodeGen/Analysis.h</code>)</li>
1180<li><code>ConstantArray::get</code></li>
1181<li><code>ConstantExpr::getExtractElement</code></li>
Jay Foaddab3d292011-07-21 14:31:17 +0000[diff] [blame]1182<li><code>ConstantExpr::getGetElementPtr</code></li>
1183<li><code>ConstantExpr::getInBoundsGetElementPtr</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1184<li><code>ConstantExpr::getIndices</code></li>
1185<li><code>ConstantExpr::getInsertElement</code></li>
1186<li><code>ConstantExpr::getWithOperands</code></li>
Jay Foad1d2f5692011-07-19 13:32:40 +0000[diff] [blame]1187<li><code>ConstantFoldCall</code> (in <code>llvm/Analysis/ConstantFolding.h</code>)</li>
1188<li><code>ConstantFoldInstOperands</code> (in <code>llvm/Analysis/ConstantFolding.h</code>)</li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1189<li><code>ConstantVector::get</code></li>
1190<li><code>DIBuilder::createComplexVariable</code></li>
1191<li><code>DIBuilder::getOrCreateArray</code></li>
1192<li><code>ExtractValueInst::Create</code></li>
1193<li><code>ExtractValueInst::getIndexedType</code></li>
1194<li><code>ExtractValueInst::getIndices</code></li>
1195<li><code>FindInsertedValue</code> (in <code>llvm/Analysis/ValueTracking.h</code>)</li>
Jay Foadca12a212011-07-19 14:42:50 +0000[diff] [blame]1196<li><code>gep_type_begin</code> (in <code>llvm/Support/GetElementPtrTypeIterator.h</code>)</li>
1197<li><code>gep_type_end</code> (in <code>llvm/Support/GetElementPtrTypeIterator.h</code>)</li>
Jay Foada9203102011-07-25 09:48:08 +0000[diff] [blame]1198<li><code>GetElementPtrInst::Create</code></li>
1199<li><code>GetElementPtrInst::CreateInBounds</code></li>
1200<li><code>GetElementPtrInst::getIndexedType</code></li>
Jay Foadb60e8512011-07-21 14:42:51 +0000[diff] [blame]1201<li><code>InsertValueInst::Create</code></li>
1202<li><code>InsertValueInst::getIndices</code></li>
1203<li><code>InvokeInst::Create</code></li>
Jay Foada3efbb12011-07-15 08:37:34 +0000[diff] [blame]1204<li><code>IRBuilder::CreateCall</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1205<li><code>IRBuilder::CreateExtractValue</code></li>
Jay Foad0a2a60a2011-07-22 08:16:57 +0000[diff] [blame]1206<li><code>IRBuilder::CreateGEP</code></li>
1207<li><code>IRBuilder::CreateInBoundsGEP</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1208<li><code>IRBuilder::CreateInsertValue</code></li>
Jay Foada3efbb12011-07-15 08:37:34 +0000[diff] [blame]1209<li><code>IRBuilder::CreateInvoke</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1210<li><code>MDNode::get</code></li>
1211<li><code>MDNode::getIfExists</code></li>
1212<li><code>MDNode::getTemporary</code></li>
1213<li><code>MDNode::getWhenValsUnresolved</code></li>
Jay Foadb9b54eb2011-07-19 15:07:52 +0000[diff] [blame]1214<li><code>SimplifyGEPInst</code> (in <code>llvm/Analysis/InstructionSimplify.h</code>)</li>
Jay Foad8fbbb392011-07-19 14:01:37 +0000[diff] [blame]1215<li><code>TargetData::getIndexedOffset</code></li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1216</ul></li>
1217
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1218 <li>All forms of <code>StringMap::getOrCreateValue</code> have been remove
1219 except for the one which takes a <code>StringRef</code>.</li>
Jay Foad558d3762011-07-14 09:19:05 +0000[diff] [blame]1220
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1221 <li>The <code>LLVMBuildUnwind</code> function from the C API was removed. The
1222 LLVM <code>unwind</code> instruction has been deprecated for a long time
1223 and isn't used by the current front-ends. So this was removed during the
1224 exception handling rewrite.</li>
Bill Wendling16005252011-08-02 06:20:17 +0000[diff] [blame]1225
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1226 <li>The <code>LLVMAddLowerSetJmpPass</code> function from the C API was
1227 removed because the <code>LowerSetJmp</code> pass was removed.</li>
Bill Wendling2626dba2011-08-03 22:18:20 +0000[diff] [blame]1228
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1229 <li>The <code>DIBuilder</code> interface used by front ends to encode
1230 debugging information in the LLVM IR now expects clients to
1231 use <code>DIBuilder::finalize()</code> at the end of translation unit to
1232 complete debugging information encoding.</li>
Devang Patel6326a422011-08-15 23:00:00 +0000[diff] [blame]1233
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1234 <li>TargetSelect.h moved to Support/ from Target/</li>
Torok Edwinf16e2d42011-09-30 13:07:52 +0000[diff] [blame]1235
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1236 <li>UpgradeIntrinsicCall no longer upgrades pre-2.9 intrinsic calls (for
1237 example <code>llvm.memset.i32</code>).</li>
Torok Edwinf16e2d42011-09-30 13:07:52 +0000[diff] [blame]1238
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1239 <li>It is mandatory to initialize all out-of-tree passes too and their dependencies now with
1240 <code>INITIALIZE_PASS{BEGIN,END,}</code>
1241 and <code>INITIALIZE_{PASS,AG}_DEPENDENCY</code>.</li>
Torok Edwinf16e2d42011-09-30 13:07:52 +0000[diff] [blame]1242
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1243 <li>The interface for MemDepResult in MemoryDependenceAnalysis has been
1244 enhanced with new return types Unknown and NonFuncLocal, in addition to
1245 the existing types Clobber, Def, and NonLocal.</li>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1246</ul>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1247
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]1248</div>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]1249
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1250</div>
1251
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1252<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1253<h2>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1254 <a name="knownproblems">Known Problems</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1255</h2>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1256<!-- *********************************************************************** -->
1257
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1258<div>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1259
Chris Lattner70e22012011-11-27 19:38:20 +0000[diff] [blame]1260<p>LLVM is generally a production quality compiler, and is used by a broad range
1261 of applications and shipping in many products. That said, not every
1262 subsystem is as mature as the aggregate, particularly the more obscure
1263 targets. If you run into a problem, please check the <a
1264 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
1265 there isn't already one or ask on the <a
1266 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev
1267 list</a>.</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1268
Chris Lattner70e22012011-11-27 19:38:20 +0000[diff] [blame]1269 <p>Known problem areas include:</p>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1270
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]1271<ul>
Chris Lattner70e22012011-11-27 19:38:20 +0000[diff] [blame]1272 <li>The Alpha, Blackfin, CellSPU, MSP430, PTX, SystemZ and
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]1273 XCore backends are experimental, and the Alpha, Blackfin and SystemZ
1274 targets have already been removed from mainline.</li>
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1275
Chris Lattner70e22012011-11-27 19:38:20 +0000[diff] [blame]1276 <li>The integrated assembler, disassembler, and JIT is not supported by
1277 several targets. If an integrated assembler is not supported, then a
1278 system assembler is required. For more details, see the <a
1279 href="CodeGenerator.html#targetfeatures">Target Features Matrix</a>.
1280 </li>
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1281
Chris Lattner70e22012011-11-27 19:38:20 +0000[diff] [blame]1282 <li>The C backend has numerous problems and is not being actively maintained.
1283 Depending on it for anything serious is not advised.</li>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]1284</ul>
1285
1286</div>
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]1287
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1288</div>
1289
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1290<!-- *********************************************************************** -->
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1291<h2>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1292 <a name="additionalinfo">Additional Information</a>
NAKAMURA Takumi06c6d9a2011-04-18 01:17:51 +0000[diff] [blame]1293</h2>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1294<!-- *********************************************************************** -->
1295
NAKAMURA Takumi074eeaa2011-04-21 01:52:00 +0000[diff] [blame]1296<div>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1297
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1298<p>A wide variety of additional information is available on
1299 the <a href="http://llvm.org/">LLVM web page</a>, in particular in
1300 the <a href="http://llvm.org/docs/">documentation</a> section. The web page
1301 also contains versions of the API documentation which is up-to-date with the
1302 Subversion version of the source code. You can access versions of these
1303 documents specific to this release by going into the "<tt>llvm/doc/</tt>"
1304 directory in the LLVM tree.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1305
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1306<p>If you have any questions or comments about LLVM, please feel free to contact
Bill Wendling7b7fa742011-10-26 18:46:16 +0000[diff] [blame]1307 us via the <a href="http://llvm.org/docs/#maillist"> mailing lists</a>.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1308
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1309</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1310
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]1311<!--=========================================================================-->
1312
1313<!-- EH details: to be moved to a blog post:
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]1314
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1315
1316
1317
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]1318<p>One of the biggest changes is that 3.0 has a new exception handling
1319 system. The old system used LLVM intrinsics to convey the exception handling
1320 information to the code generator. It worked in most cases, but not
1321 all. Inlining was especially difficult to get right. Also, the intrinsics
1322 could be moved away from the <code>invoke</code> instruction, making it hard
1323 to recover that information.</p>
1324
1325<p>The new EH system makes exception handling a first-class member of the IR. It
1326 adds two new instructions:</p>
1327
1328<ul>
1329 <li><a href="LangRef.html#i_landingpad"><code>landingpad</code></a> &mdash;
1330 this instruction defines a landing pad basic block. It contains all of the
1331 information that's needed by the code generator. It's also required to be
1332 the first non-PHI instruction in the landing pad. In addition, a landing
1333 pad may be jumped to only by the unwind edge of an <code>invoke</code>
1334 instruction.</li>
1335
1336 <li><a href="LangRef.html#i_resume"><code>resume</code></a> &mdash; this
1337 instruction causes the current exception to resume traveling up the
1338 stack. It replaces the <code>@llvm.eh.resume</code> intrinsic.</li>
1339</ul>
1340
1341<p>Converting from the old EH API to the new EH API is rather simple, because a
1342 lot of complexity has been removed. The two intrinsics,
1343 <code>@llvm.eh.exception</code> and <code>@llvm.eh.selector</code> have been
1344 superseded by the <code>landingpad</code> instruction. Instead of generating
1345 a call to <code>@llvm.eh.exception</code> and <code>@llvm.eh.selector</code>:
1346
1347<div class="doc_code">
1348<pre>
1349Function *ExcIntr = Intrinsic::getDeclaration(TheModule,
1350 Intrinsic::eh_exception);
1351Function *SlctrIntr = Intrinsic::getDeclaration(TheModule,
1352 Intrinsic::eh_selector);
1353
1354// The exception pointer.
1355Value *ExnPtr = Builder.CreateCall(ExcIntr, "exc_ptr");
1356
1357std::vector&lt;Value*&gt; Args;
1358Args.push_back(ExnPtr);
1359Args.push_back(Builder.CreateBitCast(Personality,
1360 Type::getInt8PtrTy(Context)));
1361
1362<i>// Add selector clauses to Args.</i>
1363
1364// The selector call.
1365Builder.CreateCall(SlctrIntr, Args, "exc_sel");
1366</pre>
1367</div>
1368
1369<p>You should instead generate a <code>landingpad</code> instruction, that
1370 returns an exception object and selector value:</p>
1371
1372<div class="doc_code">
1373<pre>
1374LandingPadInst *LPadInst =
1375 Builder.CreateLandingPad(StructType::get(Int8PtrTy, Int32Ty, NULL),
1376 Personality, 0);
1377
1378Value *LPadExn = Builder.CreateExtractValue(LPadInst, 0);
1379Builder.CreateStore(LPadExn, getExceptionSlot());
1380
1381Value *LPadSel = Builder.CreateExtractValue(LPadInst, 1);
1382Builder.CreateStore(LPadSel, getEHSelectorSlot());
1383</pre>
1384</div>
1385
1386<p>It's now trivial to add the individual clauses to the <code>landingpad</code>
1387 instruction.</p>
1388
1389<div class="doc_code">
1390<pre>
1391<i><b>// Adding a catch clause</b></i>
1392Constant *TypeInfo = getTypeInfo();
1393LPadInst-&gt;addClause(TypeInfo);
1394
1395<i><b>// Adding a C++ catch-all</b></i>
1396LPadInst-&gt;addClause(Constant::getNullValue(Builder.getInt8PtrTy()));
1397
1398<i><b>// Adding a cleanup</b></i>
1399LPadInst-&gt;setCleanup(true);
1400
1401<i><b>// Adding a filter clause</b></i>
1402std::vector&lt;Constant*&gt; TypeInfos;
1403Constant *TypeInfo = getFilterTypeInfo();
1404TypeInfos.push_back(Builder.CreateBitCast(TypeInfo, Builder.getInt8PtrTy()));
1405
1406ArrayType *FilterTy = ArrayType::get(Int8PtrTy, TypeInfos.size());
1407LPadInst-&gt;addClause(ConstantArray::get(FilterTy, TypeInfos));
1408</pre>
1409</div>
1410
1411<p>Converting from using the <code>@llvm.eh.resume</code> intrinsic to
1412 the <code>resume</code> instruction is trivial. It takes the exception
1413 pointer and exception selector values returned by
1414 the <code>landingpad</code> instruction:</p>
1415
1416<div class="doc_code">
1417<pre>
1418Type *UnwindDataTy = StructType::get(Builder.getInt8PtrTy(),
1419 Builder.getInt32Ty(), NULL);
1420Value *UnwindData = UndefValue::get(UnwindDataTy);
1421Value *ExcPtr = Builder.CreateLoad(getExceptionObjSlot());
1422Value *ExcSel = Builder.CreateLoad(getExceptionSelSlot());
1423UnwindData = Builder.CreateInsertValue(UnwindData, ExcPtr, 0, "exc_ptr");
1424UnwindData = Builder.CreateInsertValue(UnwindData, ExcSel, 1, "exc_sel");
1425Builder.CreateResume(UnwindData);
1426</pre>
1427</div>
1428
1429
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1430
1431
Chris Lattner1c80fbf2011-11-27 20:51:47 +0000[diff] [blame]1432 -->
1433
Michael J. Spencer60f790c2011-11-28 18:20:09 +0000[diff] [blame]1434
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1435<!-- *********************************************************************** -->
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1436
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1437<hr>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1438<address>
Misha Brukman38847d52003-12-21 22:53:21 +0000[diff] [blame]1439 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]1440 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1441 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]1442 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]1443
Chris Lattnerb4b0ce72007-05-18 00:44:29 +0000[diff] [blame]1444 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1445 Last modified: $Date$
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]1446</address>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]1447
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1448</body>
1449</html>