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