Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / 45c435a24a048c53714c2ebda74037befaf8725c / . / docs / ReleaseNotes.html
blob: d8d63c1e2d7d735ee589c65a559de0c93d720fb9 [file] [log] [blame]
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
Reid Spencer6454ed32004-11-18 18:38:58 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Chris Lattner2fb6e5c2010-10-03 23:09:03 +0000[diff] [blame]6 <meta encoding="utf8">
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]7 <link rel="stylesheet" href="llvm.css" type="text/css">
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]8 <title>LLVM 2.9 Release Notes</title>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]9</head>
10<body>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]11
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]12<div class="doc_title">LLVM 2.9 Release Notes</div>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]13
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]14<img align=right src="http://llvm.org/img/DragonSmall.png"
Gabor Greifee2187a2010-04-22 10:21:43 +0000[diff] [blame]15 width="136" height="136" alt="LLVM Dragon Logo">
Chris Lattner0e464a92010-03-17 04:02:39 +0000[diff] [blame]16
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]17<ol>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]18 <li><a href="#intro">Introduction</a></li>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]19 <li><a href="#subproj">Sub-project Status Update</a></li>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]20 <li><a href="#externalproj">External Projects Using LLVM 2.9</a></li>
21 <li><a href="#whatsnew">What's New in LLVM 2.9?</a></li>
Chris Lattner4b538b92004-04-30 22:17:12 +0000[diff] [blame]22 <li><a href="GettingStarted.html">Installation Instructions</a></li>
Dan Gohman44aa9212008-10-14 16:23:02 +0000[diff] [blame]23 <li><a href="#knownproblems">Known Problems</a></li>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]24 <li><a href="#additionalinfo">Additional Information</a></li>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]25</ol>
26
Chris Lattner7911ce22004-05-23 21:07:27 +0000[diff] [blame]27<div class="doc_author">
Dan Gohman44aa9212008-10-14 16:23:02 +0000[diff] [blame]28 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]29</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]30
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]31<h1 style="color:red">These are in-progress notes for the upcoming LLVM 2.9
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]32release.<br>
33You may prefer the
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]34<a href="http://llvm.org/releases/2.8/docs/ReleaseNotes.html">LLVM 2.8
Dan Gohmanb44f6c62010-05-03 23:51:05 +0000[diff] [blame]35Release Notes</a>.</h1>
Jeffrey Yasskinbec48772010-01-28 01:14:43 +0000[diff] [blame]36
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]37<!-- *********************************************************************** -->
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]38<div class="doc_section">
39 <a name="intro">Introduction</a>
40</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]41<!-- *********************************************************************** -->
42
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]43<div class="doc_text">
44
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]45<p>This document contains the release notes for the LLVM Compiler
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]46Infrastructure, release 2.9. Here we describe the status of LLVM, including
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]47major improvements from the previous release and significant known problems.
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]48All LLVM releases may be downloaded from the <a
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]49href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
Chris Lattner19092612003-10-02 16:38:05 +0000[diff] [blame]50
Chris Lattner7506b1d2004-12-07 08:04:13 +0000[diff] [blame]51<p>For more information about LLVM, including information about the latest
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]52release, please check out the <a href="http://llvm.org/">main LLVM
Chris Lattner47ad72c2003-10-07 21:38:31 +0000[diff] [blame]53web site</a>. If you have questions or comments, the <a
Chris Lattnerc66bfef2010-03-17 04:41:49 +0000[diff] [blame]54href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's
55Mailing List</a> is a good place to send them.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]56
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]57<p>Note that if you are reading this file from a Subversion checkout or the
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]58main LLVM web page, this document applies to the <i>next</i> release, not the
Gabor Greiffa933f82008-10-14 11:00:32 +0000[diff] [blame]59current one. To see the release notes for a specific release, please see the
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]60<a href="http://llvm.org/releases/">releases page</a>.</p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]61
62</div>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]63
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]64<!--
65Almost dead code.
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]66 lib/Transforms/IPO/MergeFunctions.cpp => consider for 3.0.
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]67-->
68
69
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]70<!-- Features that need text if they're finished for 3.0:
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]71 combiner-aa?
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]72 strong phi elim
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]73 loop dependence analysis
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]74 CorrelatedValuePropagation
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]75 -->
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]76
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]77<!-- *********************************************************************** -->
78<div class="doc_section">
79 <a name="subproj">Sub-project Status Update</a>
Chris Lattnerea34f642008-06-08 21:34:41 +0000[diff] [blame]80</div>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]81<!-- *********************************************************************** -->
Chris Lattnerea34f642008-06-08 21:34:41 +0000[diff] [blame]82
83<div class="doc_text">
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]84<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]85The LLVM 2.9 distribution currently consists of code from the core LLVM
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]86repository (which roughly includes the LLVM optimizers, code generators
87and supporting tools), the Clang repository and the llvm-gcc repository. In
88addition to this code, the LLVM Project includes other sub-projects that are in
89development. Here we include updates on these subprojects.
Bill Wendling63d8c552009-03-02 04:28:57 +0000[diff] [blame]90</p>
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]91
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]92</div>
93
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]94
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]95<!--=========================================================================-->
Chris Lattner96a445e2008-10-13 18:01:01 +0000[diff] [blame]96<div class="doc_subsection">
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]97<a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]98</div>
99
100<div class="doc_text">
101
Chris Lattner095539f2010-04-26 17:42:18 +0000[diff] [blame]102<p><a href="http://clang.llvm.org/">Clang</a> is an LLVM front end for the C,
103C++, and Objective-C languages. Clang aims to provide a better user experience
104through expressive diagnostics, a high level of conformance to language
105standards, fast compilation, and low memory use. Like LLVM, Clang provides a
106modular, library-based architecture that makes it suitable for creating or
107integrating with other development tools. Clang is considered a
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]108production-quality compiler for C, Objective-C, C++ and Objective-C++ on x86
109(32- and 64-bit), and for darwin-arm targets.</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]110
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]111<p>In the LLVM 2.9 time-frame, the Clang team has made many improvements in C,
112C++ and Objective-C support. C++ support is now generally rock solid, has
113been exercised on a broad variety of code, and has several new C++'0x features
114implemented (such as rvalue references and variadic templates). LLVM 2.9 has
115also brought in a large range of bug fixes and minor features (e.g. __label__
116support), and is much more compatible with the Linux Kernel.</p>
117
118<p>If Clang rejects your code that is built with another compiler, please take a
119look at the <a href="http://clang.llvm.org/compatibility.html">language
120compatibility</a> guide to make sure the issue isn't intentional or a known
121issue.
122</p>
Bill Wendling741748a2008-10-27 09:27:33 +0000[diff] [blame]123
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]124<ul>
125</ul>
Chris Lattnerfb97b2d2008-10-13 18:11:54 +0000[diff] [blame]126</div>
127
128<!--=========================================================================-->
129<div class="doc_subsection">
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]130<a name="dragonegg">DragonEgg: GCC front-ends, LLVM back-end</a>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]131</div>
132
133<div class="doc_text">
134<p>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]135<a href="http://dragonegg.llvm.org/">DragonEgg</a> is a
136<a href="http://gcc.gnu.org/wiki/plugins">gcc plugin</a> that replaces GCC's
137optimizers and code generators with LLVM's.
138Currently it requires a patched version of gcc-4.5.
139The plugin can target the x86-32 and x86-64 processor families and has been
140used successfully on the Darwin, FreeBSD and Linux platforms.
141The Ada, C, C++ and Fortran languages work well.
142The plugin is capable of compiling plenty of Obj-C, Obj-C++ and Java but it is
143not known whether the compiled code actually works or not!
Duncan Sands749fd832010-04-02 09:23:15 +0000[diff] [blame]144</p>
145
146<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]147The 2.9 release has the following notable changes:
Duncan Sands4b1da2b2010-09-30 17:37:34 +0000[diff] [blame]148<ul>
Duncan Sands528a5102011-04-04 11:09:08 +0000[diff] [blame]149<li>The plugin is much more stable when compiling Fortran.</li>
150<li>Inline asm where an asm output is tied to an input of a different size is
151now supported in many more cases.</li>
152<li>Basic support for the __float128 type was added. It is now possible to
153generate LLVM IR from programs using __float128 but code generation does not
154work yet.</li>
155<li>Compiling Java programs no longer systematically crashes the plugin.</li>
Duncan Sands4b1da2b2010-09-30 17:37:34 +0000[diff] [blame]156</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]157
158</div>
159
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]160<!--=========================================================================-->
161<div class="doc_subsection">
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]162<a name="compiler-rt">compiler-rt: Compiler Runtime Library</a>
163</div>
164
165<div class="doc_text">
166<p>
167The new LLVM <a href="http://compiler-rt.llvm.org/">compiler-rt project</a>
168is a simple library that provides an implementation of the low-level
169target-specific hooks required by code generation and other runtime components.
170For example, when compiling for a 32-bit target, converting a double to a 64-bit
171unsigned integer is compiled into a runtime call to the "__fixunsdfdi"
172function. The compiler-rt library provides highly optimized implementations of
173this and other low-level routines (some are 3x faster than the equivalent
174libgcc routines).</p>
175
176<p>
177All of the code in the compiler-rt project is available under the standard LLVM
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]178License, a "BSD-style" license.
179
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]180compiler_rt is now dual licensed under MIT and UIUC license
181
182Several minor changes for better ARM support.
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]183
184New in LLVM 2.9, UPDATE</p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]185
186</div>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]187
188<!--=========================================================================-->
189<div class="doc_subsection">
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]190<a name="lldb">LLDB: Low Level Debugger</a>
191</div>
192
193<div class="doc_text">
194<p>
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]195<a href="http://lldb.llvm.org/">LLDB</a> is a brand new member of the LLVM
196umbrella of projects. LLDB is a next generation, high-performance debugger. It
197is built as a set of reusable components which highly leverage existing
198libraries in the larger LLVM Project, such as the Clang expression parser, the
199LLVM disassembler and the LLVM JIT.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]200
201<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]202LLDB is in early development and not included as part of the LLVM 2.9 release,
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]203
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]204
205
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]206<!--
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]207but is mature enough to support basic debugging scenarios on Mac OS X in C,
208Objective-C and C++. We'd really like help extending and expanding LLDB to
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]209support new platforms, new languages, new architectures, and new features.-->
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]210</p>
211
212</div>
213
214<!--=========================================================================-->
215<div class="doc_subsection">
216<a name="libc++">libc++: C++ Standard Library</a>
217</div>
218
219<div class="doc_text">
220<p>
Tobias Grossercdce44b2010-10-06 21:07:30 +0000[diff] [blame]221<a href="http://libcxx.llvm.org/">libc++</a> is another new member of the LLVM
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]222family. It is an implementation of the C++ standard library, written from the
223ground up to specifically target the forthcoming C++'0X standard and focus on
224delivering great performance.</p>
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]225
226<p>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]227As of the LLVM 2.9 release, UPDATE!
228
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]229libc++ is now dual licensed under MIT and UIUC license
230
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]231<!--libc++ is virtually feature complete, but would
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]232benefit from more testing and better integration with Clang++. It is also
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]233looking forward to the C++ committee finalizing the C++'0x standard.-->
Chris Lattnere07043c2010-09-29 05:30:03 +0000[diff] [blame]234</p>
235
236</div>
237
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]238
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]239
240<!--=========================================================================-->
241<div class="doc_subsection">
242<a name="klee">KLEE: A Symbolic Execution Virtual Machine</a>
243</div>
244
245<div class="doc_text">
246<p>
247<a href="http://klee.llvm.org/">KLEE</a> is a symbolic execution framework for
248programs in LLVM bitcode form. KLEE tries to symbolically evaluate "all" paths
249through the application and records state transitions that lead to fault
250states. This allows it to construct testcases that lead to faults and can even
251be used to verify some algorithms.
252</p>
253
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]254<p>UPDATE!</p>
Daniel Dunbar97b01a82010-10-04 17:39:47 +0000[diff] [blame]255
256</div>
257
258
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]259<!-- *********************************************************************** -->
260<div class="doc_section">
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]261 <a name="externalproj">External Open Source Projects Using LLVM 2.9</a>
Chris Lattnerab68e9e2009-02-26 22:33:38 +0000[diff] [blame]262</div>
263<!-- *********************************************************************** -->
264
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]265<div class="doc_text">
266
267<p>An exciting aspect of LLVM is that it is used as an enabling technology for
268 a lot of other language and tools projects. This section lists some of the
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]269 projects that have already been updated to work with LLVM 2.9.</p>
Chris Lattner7c8e7962010-04-26 17:38:10 +0000[diff] [blame]270</div>
271
Chris Lattner75547712010-10-03 23:49:06 +0000[diff] [blame]272
273
Chris Lattnere0518442010-10-01 06:34:49 +0000[diff] [blame]274
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]275<!-- *********************************************************************** -->
276<div class="doc_section">
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]277 <a name="whatsnew">What's New in LLVM 2.9?</a>
Chris Lattner8348b472008-06-08 21:58:17 +0000[diff] [blame]278</div>
279<!-- *********************************************************************** -->
280
Chris Lattnerf8e0b4e2008-06-08 22:59:35 +0000[diff] [blame]281<div class="doc_text">
282
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]283<p>This release includes a huge number of bug fixes, performance tweaks and
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]284minor improvements. Some of the major improvements and new features are listed
285in this section.
Chris Lattnerf8e0b4e2008-06-08 22:59:35 +0000[diff] [blame]286</p>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]287
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]288</div>
289
290<!--=========================================================================-->
291<div class="doc_subsection">
Chris Lattner252b83d2008-02-06 18:00:06 +0000[diff] [blame]292<a name="majorfeatures">Major New Features</a>
293</div>
294
295<div class="doc_text">
296
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]297<p>LLVM 2.9 includes several major new capabilities:</p>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]298
299<ul>
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]300<li><pre>
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]301 last release for llvm-gcc
302TBAA
303Triple::normalize is new, llvm triples are always stored in normalized form internally.
304
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]305Triple x86_64--mingw64 is obsoleted. Use x86_64--mingw32 instead.
306
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]307MC Assembler: X86 now generates much better diagnostics for common errors,
308 is much faster at matching instructions, is much more bug-compatible with
309 the GAS assembler, and is now generally useful for a broad range of X86
310 assembly.
311
312New Nvidia PTX backend, not generally useful in 2.9 though.
313
314Much better debug info generated, particularly in optimized code situations.
315
316ARM Fast ISel
317
318ELF MC support
319
320X86: Reimplemented all of MMX to introduce a new LLVM IR x86_mmx type. Now
321 random types like &lt;2 x i32&gt; are not iseld to mmx without emms.
322
323Some basic <a href="CodeGenerator.html#mc">internals documentation</a> for MC.
324
325MC Assembler support for .file and .loc.
326
327
328inline asm multiple alternative constraint support.
329
330LoopIdiom: memset/memcpy formation
331
332
333X86 support for FS/GS relative loads and stores using address space 256/257 are
334 reliable now.
335
336ARM: New code placement pass.
337
338
339PointerTracking has been removed from mainline, moved to ClamAV.
340
341EarlyCSE pass.
342
343
344ARM: Improved code generation for Cortex-A8 and Cortex-A9 CPUs.
345
346Scheduler now models operand latency and pipeline forwarding.
347
348Major regalloc rewrite, not on by default for 2.9.
349MC assembler support for 3dNow! and 3DNowA instructions.
350
351LoopIndexSplit pass was removed, unmaintained.
352
353
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]354Win32 PE-COFF support in the MC assembler has made a lot of progress in the 2.9
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]355 timeframe, but is still not generally useful. Please see
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]356 "http://llvm.org/bugs/showdependencytree.cgi?id=9100&amp;hide_resolved=1" for open bugs?
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]357
358New <a href="WritingAnLLVMPass.html#RegionPass">RegionPass</a> infrastructure
359 for region-based optimizations.
360
361MicroBlaze: major updates for aggressive delay slot filler, MC-based assembly
362 printing, assembly instruction parsing, ELF .o file emission, and MC
363 instruction disassembler.
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]364</pre></li>
Chris Lattner8170c102008-02-10 08:18:42 +0000[diff] [blame]365</ul>
Chris Lattner0a6f6d52011-04-05 07:19:28 +0000[diff] [blame]366
367Still todo: [101025-110228]
Chris Lattnerdc910082010-03-17 06:41:58 +0000[diff] [blame]368
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]369</div>
370
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]371<!--=========================================================================-->
372<div class="doc_subsection">
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]373<a name="coreimprovements">LLVM IR and Core Improvements</a>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]374</div>
375
376<div class="doc_text">
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]377<p>LLVM IR has several new features for better support of new targets and that
378expose new optimization opportunities:</p>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]379
Chris Lattner791f77b2008-06-05 06:25:56 +0000[diff] [blame]380<ul>
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]381</ul>
Mikhail Glushenkovea65d7d2008-10-13 02:08:34 +0000[diff] [blame]382
Chris Lattnerf304ffc2008-02-10 08:17:19 +0000[diff] [blame]383</div>
384
385<!--=========================================================================-->
386<div class="doc_subsection">
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]387<a name="optimizer">Optimizer Improvements</a>
388</div>
389
390<div class="doc_text">
391
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]392<p>In addition to a large array of minor performance tweaks and bug fixes, this
Chris Lattnerf3013872008-10-13 21:50:36 +0000[diff] [blame]393release includes a few major enhancements and additions to the optimizers:</p>
Chris Lattneracce85d2008-02-10 07:46:44 +0000[diff] [blame]394
395<ul>
Rafael Espindolaa26f36c2011-03-18 04:07:44 +0000[diff] [blame]396 <li>TBAA.</li>
397 <li>LTO has been improved to use MC for parsing inline asm and now
398 can build large programs like Firefox 4 on both OS X and Linux.</li>
Chris Lattner11b66112010-10-04 02:42:39 +0000[diff] [blame]399</ul>
400
401<!--
402<p>In addition to these features that are done in 2.8, there is preliminary
403 support in the release for Type Based Alias Analysis
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]404 Preliminary work on TBAA but not usable in 2.8.
405 New CorrelatedValuePropagation pass, not on by default in 2.8 yet.
Chris Lattner11b66112010-10-04 02:42:39 +0000[diff] [blame]406-->
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]407
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]408</div>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]409
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]410<!--=========================================================================-->
411<div class="doc_subsection">
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]412<a name="mc">MC Level Improvements</a>
413</div>
414
415<div class="doc_text">
416<p>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]417The LLVM Machine Code (aka MC) subsystem was created to solve a number
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]418of problems in the realm of assembly, disassembly, object file format handling,
419and a number of other related areas that CPU instruction-set level tools work
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]420in.</p>
421
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]422<ul>
Rafael Espindolaa26f36c2011-03-18 04:07:44 +0000[diff] [blame]423 <li>MC is now used by default for ELF systems on x86 and
424 x86-64.</li>
425 <li>MC supports and CodeGen uses the <tt>.loc</tt> directives for
426 producing line number debug info. This produces more compact line
427 tables.</li>
428 <li>MC supports the <tt>.cfi_*</tt> directives for producing DWARF
429 frame information, but it is still not used by CodeGen by default.</li>
430 <li>COFF support?</li>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]431</ul>
432
433<p>For more information, please see the <a
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]434href="http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html">Intro to the
435LLVM MC Project Blog Post</a>.
436</p>
437
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]438</div>
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]439
Chris Lattner4ba2b652010-09-30 16:31:33 +0000[diff] [blame]440<!--=========================================================================-->
441<div class="doc_subsection">
Chris Lattner511433e2009-03-02 03:24:11 +0000[diff] [blame]442<a name="codegen">Target Independent Code Generator Improvements</a>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]443</div>
444
445<div class="doc_text">
446
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]447<p>We have put a significant amount of work into the code generator
448infrastructure, which allows us to implement more aggressive algorithms and make
449it run faster:</p>
Chris Lattner0b832202008-06-08 02:45:07 +0000[diff] [blame]450
451<ul>
Chris Lattner3bdcda12010-10-04 03:58:12 +0000[diff] [blame]452<!-- SplitKit -->
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]453FastISel for ARM.
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]454</ul>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]455</div>
456
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]457<!--=========================================================================-->
458<div class="doc_subsection">
459<a name="x86">X86-32 and X86-64 Target Improvements</a>
460</div>
461
462<div class="doc_text">
Chris Lattner7714c912010-10-04 04:39:25 +0000[diff] [blame]463<p>New features and major changes in the X86 target include:
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]464</p>
465
466<ul>
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]467 <li>Several bugs have been fixed for Windows x64 code generator.</li>
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]468</ul>
469
Chris Lattner917cc712009-03-02 02:37:32 +0000[diff] [blame]470</div>
Chris Lattner84977642007-09-21 03:54:09 +0000[diff] [blame]471
472<!--=========================================================================-->
473<div class="doc_subsection">
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]474<a name="ARM">ARM Target Improvements</a>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]475</div>
476
477<div class="doc_text">
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]478<p>New features of the ARM target include:
479</p>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]480
481<ul>
Bob Wilsone8472772010-09-13 17:39:35 +0000[diff] [blame]482</ul>
Chris Lattner61358ab2009-10-13 17:48:04 +0000[diff] [blame]483</div>
Chris Lattnerc441fb82009-03-01 02:30:21 +0000[diff] [blame]484
Chris Lattner77d29b12008-06-05 08:02:49 +0000[diff] [blame]485
486<!--=========================================================================-->
487<div class="doc_subsection">
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]488<a name="changes">Major Changes and Removed Features</a>
489</div>
490
491<div class="doc_text">
492
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]493<p>If you're already an LLVM user or developer with out-of-tree changes based
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]494on LLVM 2.8, this section lists some "gotchas" that you may run into upgrading
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]495from the previous release.</p>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]496
497<ul>
Chris Lattnerb7c85b42010-04-21 05:17:40 +0000[diff] [blame]498</ul>
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]499
Chris Lattnerbb117712010-10-04 01:29:06 +0000[diff] [blame]500
501
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]502<p>In addition, many APIs have changed in this release. Some of the major LLVM
503API changes are:</p>
Chris Lattnereeb4da02008-10-13 22:06:31 +0000[diff] [blame]504<ul>
Devang Patelb34dd132008-10-14 20:03:43 +0000[diff] [blame]505</ul>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]506
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]507</div>
508
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]509<!--=========================================================================-->
510<div class="doc_subsection">
511<a name="devtree_changes">Development Infrastructure Changes</a>
512</div>
513
514<div class="doc_text">
515
516<p>This section lists changes to the LLVM development infrastructure. This
517mostly impacts users who actively work on LLVM or follow development on
518mainline, but may also impact users who leverage the LLVM build infrastructure
519or are interested in LLVM qualification.</p>
520
521<ul>
Daniel Dunbarf0233c62010-10-04 20:11:41 +0000[diff] [blame]522</ul>
523</div>
Chris Lattnerf6662f92008-10-13 17:57:36 +0000[diff] [blame]524
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]525<!-- *********************************************************************** -->
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]526<div class="doc_section">
527 <a name="knownproblems">Known Problems</a>
528</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]529<!-- *********************************************************************** -->
530
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]531<div class="doc_text">
532
Mikhail Glushenkovf795ef02009-03-01 18:09:47 +0000[diff] [blame]533<p>This section contains significant known problems with the LLVM system,
Chris Lattnere18b32e2008-11-10 05:40:34 +0000[diff] [blame]534listed by component. If you run into a problem, please check the <a
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]535href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
Chris Lattner5eccca42003-12-12 21:22:16 +0000[diff] [blame]536there isn't already one.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]537
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]538</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]539
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]540<!-- ======================================================================= -->
541<div class="doc_subsection">
542 <a name="experimental">Experimental features included with this release</a>
543</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]544
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]545<div class="doc_text">
546
Misha Brukman6df9e2c2004-05-12 21:46:05 +0000[diff] [blame]547<p>The following components of this LLVM release are either untested, known to
548be broken or unreliable, or are in early development. These components should
549not be relied on, and bugs should not be filed against them, but they may be
550useful to some people. In particular, if you would like to work on one of these
Chris Lattner2b659ef2008-02-12 06:29:45 +0000[diff] [blame]551components, please contact us on the <a
552href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]553
554<ul>
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]555<li>The Alpha, Blackfin, CellSPU, MicroBlaze, MSP430, MIPS, PTX, SystemZ
Chris Lattnerbb117712010-10-04 01:29:06 +0000[diff] [blame]556 and XCore backends are experimental.</li>
Chris Lattner7d9b6b42010-10-02 21:59:30 +0000[diff] [blame]557<li><tt>llc</tt> "<tt>-filetype=obj</tt>" is experimental on all targets
Chris Lattnerbe2e1b52011-03-10 07:43:44 +0000[diff] [blame]558 other than darwin-i386 and darwin-x86_64. FIXME: Not true on ELF anymore?</li>
559
Chris Lattnerf5ee1702004-03-14 02:03:02 +0000[diff] [blame]560</ul>
561
562</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]563
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]564<!-- ======================================================================= -->
565<div class="doc_subsection">
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]566 <a name="x86-be">Known problems with the X86 back-end</a>
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]567</div>
568
569<div class="doc_text">
570
571<ul>
Anton Korobeynikova6094be2008-06-08 10:24:13 +0000[diff] [blame]572 <li>The X86 backend does not yet support
573 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
574 floating point stack</a>. It supports the 'f' and 't' constraints, but not
575 'u'.</li>
Dan Gohman8207ba92008-06-08 23:05:11 +0000[diff] [blame]576 <li>The X86-64 backend does not yet support the LLVM IR instruction
Chris Lattner914ce462010-04-22 06:28:20 +0000[diff] [blame]577 <tt>va_arg</tt>. Currently, front-ends support variadic
Dan Gohman8207ba92008-06-08 23:05:11 +0000[diff] [blame]578 argument constructs on X86-64 by lowering them manually.</li>
NAKAMURA Takumi45c435a2011-04-05 08:24:22 +0000[diff] [blame^]579 <li>Windows x64 (aka Win64) code generator has a few issues.
580 <ul>
581 <li>llvm-gcc cannot build the mingw-w64 runtime currently
582 due to lack of support for the 'u' inline assembly
583 constraint and for X87 floating point inline assembly.</li>
584 <li>On mingw-w64, you will see unresolved symbol <tt>__chkstk</tt>
585 due to <a href="http://llvm.org/bugs/show_bug.cgi?id=8919">Bug 8919</a>.
586 It is fixed in <a href="http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110321/118499.html">r128206</a>.</li>
587 <li>Miss-aligned MOVDQA might crash your program. It is due to
588 <a href="http://llvm.org/bugs/show_bug.cgi?id=9483">Bug 9483</a>,
589 lack of handling aligned internal globals.</li>
590 </ul>
591 </li>
592
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]593</ul>
594
595</div>
596
597<!-- ======================================================================= -->
598<div class="doc_subsection">
599 <a name="ppc-be">Known problems with the PowerPC back-end</a>
600</div>
601
602<div class="doc_text">
603
604<ul>
Nicolas Geoffraye4285dc2007-05-15 09:21:28 +0000[diff] [blame]605<li>The Linux PPC32/ABI support needs testing for the interpreter and static
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]606compilation, and lacks support for debug information.</li>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]607</ul>
608
609</div>
610
611<!-- ======================================================================= -->
612<div class="doc_subsection">
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]613 <a name="arm-be">Known problems with the ARM back-end</a>
614</div>
615
616<div class="doc_text">
617
618<ul>
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]619<li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
Duncan Sandsc90d68b2007-09-26 15:59:54 +0000[diff] [blame]620processors, thumb programs can crash or produce wrong
Chris Lattner57a460e2007-05-23 04:39:32 +0000[diff] [blame]621results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
John Criswell524a5dd2009-03-02 15:28:15 +0000[diff] [blame]622<li>Compilation for ARM Linux OABI (old ABI) is supported but not fully tested.
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]623</li>
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]624</ul>
625
626</div>
627
628<!-- ======================================================================= -->
629<div class="doc_subsection">
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]630 <a name="sparc-be">Known problems with the SPARC back-end</a>
631</div>
632
633<div class="doc_text">
634
635<ul>
John Criswell524a5dd2009-03-02 15:28:15 +0000[diff] [blame]636<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]637 support the 64-bit SPARC ABI (-m64).</li>
638</ul>
639
640</div>
641
642<!-- ======================================================================= -->
643<div class="doc_subsection">
Bruno Cardoso Lopesb7e1a4f2008-10-25 14:56:26 +0000[diff] [blame]644 <a name="mips-be">Known problems with the MIPS back-end</a>
645</div>
646
647<div class="doc_text">
648
649<ul>
Bruno Cardoso Lopesb7e1a4f2008-10-25 14:56:26 +0000[diff] [blame]650<li>64-bit MIPS targets are not supported yet.</li>
651</ul>
652
653</div>
654
655<!-- ======================================================================= -->
656<div class="doc_subsection">
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]657 <a name="alpha-be">Known problems with the Alpha back-end</a>
658</div>
659
660<div class="doc_text">
661
662<ul>
663
664<li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
665appropriate nops inserted to ensure restartability.</li>
666
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]667</ul>
668</div>
669
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]670<!-- ======================================================================= -->
671<div class="doc_subsection">
Chris Lattnerf3e5bc62007-05-14 06:56:09 +0000[diff] [blame]672 <a name="c-be">Known problems with the C back-end</a>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]673</div>
674
675<div class="doc_text">
676
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]677<p>The C backend has numerous problems and is not being actively maintained.
678Depending on it for anything serious is not advised.</p>
679
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]680<ul>
Chris Lattner5733b272008-06-05 06:35:40 +0000[diff] [blame]681<li><a href="http://llvm.org/PR802">The C backend has only basic support for
682 inline assembly code</a>.</li>
Chris Lattner725a0d82007-09-26 06:01:35 +0000[diff] [blame]683<li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
684 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
Gabor Greif4906abe2009-03-02 12:02:51 +0000[diff] [blame]685 C++ code compiled with <tt>llc</tt> or native compilers.</li>
Duncan Sandsf74c0cc2008-02-10 13:40:55 +0000[diff] [blame]686<li>The C backend does not support all exception handling constructs.</li>
Duncan Sands50723a92009-02-25 11:51:54 +0000[diff] [blame]687<li>The C backend does not support arbitrary precision integers.</li>
Chris Lattner26299222006-11-18 07:51:14 +0000[diff] [blame]688</ul>
689
690</div>
John Criswellc0c186d2005-11-08 21:11:33 +0000[diff] [blame]691
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]692
693<!-- ======================================================================= -->
694<div class="doc_subsection">
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]695 <a name="llvm-gcc">Known problems with the llvm-gcc front-end</a>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]696</div>
Chris Lattner47588f92003-10-02 05:07:23 +0000[diff] [blame]697
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]698<div class="doc_text">
Chris Lattnerc5d658a2006-03-03 00:34:26 +0000[diff] [blame]699
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]700<p>llvm-gcc is generally very stable for the C family of languages. The only
701 major language feature of GCC not supported by llvm-gcc is the
702 <tt>__builtin_apply</tt> family of builtins. However, some extensions
703 are only supported on some targets. For example, trampolines are only
704 supported on some targets (these are used when you take the address of a
705 nested function).</p>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]706
Chris Lattner3016ee92010-09-29 05:34:42 +0000[diff] [blame]707<p>Fortran support generally works, but there are still several unresolved bugs
708 in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the
709 tools/gfortran component for details. Note that llvm-gcc is missing major
710 Fortran performance work in the frontend and library that went into GCC after
711 4.2. If you are interested in Fortran, we recommend that you consider using
712 <a href="#dragonegg">dragonegg</a> instead.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]713
Duncan Sands3af96332010-10-04 10:06:56 +0000[diff] [blame]714<p>The llvm-gcc 4.2 Ada compiler has basic functionality, but is no longer being
715actively maintained. If you are interested in Ada, we recommend that you
716consider using <a href="#dragonegg">dragonegg</a> instead.</p>
Chris Lattner2b659ef2008-02-12 06:29:45 +0000[diff] [blame]717</div>
718
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]719<!-- *********************************************************************** -->
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]720<div class="doc_section">
721 <a name="additionalinfo">Additional Information</a>
722</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]723<!-- *********************************************************************** -->
724
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]725<div class="doc_text">
726
Chris Lattner416db102005-05-16 17:13:10 +0000[diff] [blame]727<p>A wide variety of additional information is available on the <a
Chris Lattnerb4b0ce72007-05-18 00:44:29 +0000[diff] [blame]728href="http://llvm.org">LLVM web page</a>, in particular in the <a
729href="http://llvm.org/docs/">documentation</a> section. The web page also
Reid Spencer669ed452007-07-09 08:04:31 +0000[diff] [blame]730contains versions of the API documentation which is up-to-date with the
731Subversion version of the source code.
Misha Brukman109d9e82005-03-30 19:14:24 +0000[diff] [blame]732You can access versions of these documents specific to this release by going
733into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]734
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]735<p>If you have any questions or comments about LLVM, please feel free to contact
Chris Lattnerc463b272005-10-29 07:07:09 +0000[diff] [blame]736us via the <a href="http://llvm.org/docs/#maillist"> mailing
Chris Lattner5eccca42003-12-12 21:22:16 +0000[diff] [blame]737lists</a>.</p>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]738
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]739</div>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]740
741<!-- *********************************************************************** -->
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]742
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]743<hr>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]744<address>
Misha Brukman38847d52003-12-21 22:53:21 +0000[diff] [blame]745 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]746 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]747 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +0000[diff] [blame]748 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]749
Chris Lattnerb4b0ce72007-05-18 00:44:29 +0000[diff] [blame]750 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]751 Last modified: $Date$
Misha Brukman2061e892003-11-22 01:23:39 +0000[diff] [blame]752</address>
Chris Lattner79c3fe12003-10-02 04:57:28 +0000[diff] [blame]753
Misha Brukman500bc302003-11-22 00:38:41 +0000[diff] [blame]754</body>
755</html>