blob: 402aa614c9845d6d1f550cd9b16f06bd7fa3ccb0 [file] [log] [blame]
Anton Korobeynikovf7c5a6e2008-06-08 10:23:46 +00001
Misha Brukman80731b92003-11-22 00:38:41 +00002<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 "http://www.w3.org/TR/html4/strict.dtd">
4<html>
5<head>
Reid Spencere4190fa2004-11-18 18:38:58 +00006 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Misha Brukman80731b92003-11-22 00:38:41 +00007 <link rel="stylesheet" href="llvm.css" type="text/css">
Chris Lattnere38ac152008-02-12 06:29:45 +00008 <title>LLVM 2.3 Release Notes</title>
Misha Brukman80731b92003-11-22 00:38:41 +00009</head>
10<body>
Chris Lattner3d482502003-10-02 04:57:28 +000011
Chris Lattnere38ac152008-02-12 06:29:45 +000012<div class="doc_title">LLVM 2.3 Release Notes</div>
Chris Lattner3d482502003-10-02 04:57:28 +000013
14<ol>
Misha Brukman80731b92003-11-22 00:38:41 +000015 <li><a href="#intro">Introduction</a></li>
Chris Lattnerc75fd522008-06-08 21:58:17 +000016 <li><a href="#changes">Major Changes and Sub-project Status</a></li>
Misha Brukman80731b92003-11-22 00:38:41 +000017 <li><a href="#whatsnew">What's New?</a></li>
Chris Lattner77a51732004-04-30 22:17:12 +000018 <li><a href="GettingStarted.html">Installation Instructions</a></li>
Misha Brukman80731b92003-11-22 00:38:41 +000019 <li><a href="#portability">Portability and Supported Platforms</a></li>
Chris Lattner3d482502003-10-02 04:57:28 +000020 <li><a href="#knownproblems">Known Problems</a>
Misha Brukman80731b92003-11-22 00:38:41 +000021 <li><a href="#additionalinfo">Additional Information</a></li>
Chris Lattner3d482502003-10-02 04:57:28 +000022</ol>
23
Chris Lattner020e1fc2004-05-23 21:07:27 +000024<div class="doc_author">
Chris Lattnera69595e2005-10-29 07:07:09 +000025 <p>Written by the <a href="http://llvm.org">LLVM Team</a><p>
Misha Brukman80731b92003-11-22 00:38:41 +000026</div>
Chris Lattner3d482502003-10-02 04:57:28 +000027
Chris Lattner6cb64032008-06-05 08:02:49 +000028<!-- Done through Week-of-Mon-20080324.txt -->
29
Chris Lattner3d482502003-10-02 04:57:28 +000030<!-- *********************************************************************** -->
Misha Brukman80731b92003-11-22 00:38:41 +000031<div class="doc_section">
32 <a name="intro">Introduction</a>
33</div>
Chris Lattner3d482502003-10-02 04:57:28 +000034<!-- *********************************************************************** -->
35
Misha Brukman80731b92003-11-22 00:38:41 +000036<div class="doc_text">
37
38<p>This document contains the release notes for the LLVM compiler
Chris Lattnere38ac152008-02-12 06:29:45 +000039infrastructure, release 2.3. Here we describe the status of LLVM, including
Chris Lattnerbee7b322007-05-23 04:39:32 +000040major improvements from the previous release and any known problems. All LLVM
Chris Lattner98a33492007-05-09 04:58:11 +000041releases may be downloaded from the <a href="http://llvm.org/releases/">LLVM
Chris Lattnerbee7b322007-05-23 04:39:32 +000042releases web site</a>.</p>
Chris Lattner62495762003-10-02 16:38:05 +000043
Chris Lattnerb5bb5972004-12-07 08:04:13 +000044<p>For more information about LLVM, including information about the latest
Chris Lattnera69595e2005-10-29 07:07:09 +000045release, please check out the <a href="http://llvm.org/">main LLVM
Chris Lattnere7525b52003-10-07 21:38:31 +000046web site</a>. If you have questions or comments, the <a
47href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
Misha Brukman80731b92003-11-22 00:38:41 +000048list</a> is a good place to send them.</p>
Chris Lattner3d482502003-10-02 04:57:28 +000049
Reid Spencerc7f87f22007-07-09 08:04:31 +000050<p>Note that if you are reading this file from a Subversion checkout or the
Chris Lattner0a1fd102007-09-21 03:54:09 +000051main LLVM web page, this document applies to the <i>next</i> release, not the
52current one. To see the release notes for a specific releases, please see the
53<a href="http://llvm.org/releases/">releases page</a>.</p>
Misha Brukman80731b92003-11-22 00:38:41 +000054
55</div>
Chris Lattner3d482502003-10-02 04:57:28 +000056
57<!-- *********************************************************************** -->
Misha Brukman80731b92003-11-22 00:38:41 +000058<div class="doc_section">
Chris Lattnerc75fd522008-06-08 21:58:17 +000059 <a name="changes">Major Changes and Sub-project Status</a>
Misha Brukman80731b92003-11-22 00:38:41 +000060</div>
Chris Lattner3d482502003-10-02 04:57:28 +000061<!-- *********************************************************************** -->
62
Misha Brukman80731b92003-11-22 00:38:41 +000063<div class="doc_text">
64
Chris Lattnere38ac152008-02-12 06:29:45 +000065<p>This is the fourteenth public release of the LLVM Compiler Infrastructure.
Chris Lattnerb7112222008-06-05 06:25:56 +000066It includes a large number of features and refinements from LLVM 2.2.</p>
Chris Lattnerba7bd472003-12-06 20:22:41 +000067
Chris Lattner21a90402004-05-24 04:50:25 +000068</div>
69
Chris Lattnere38ac152008-02-12 06:29:45 +000070<!-- Unfinished features in 2.3:
Chris Lattner2b8a52e2008-02-10 07:46:44 +000071 Machine LICM
72 Machine Sinking
73 LegalizeDAGTypes
74 -->
75
Chris Lattnerba7bd472003-12-06 20:22:41 +000076<!--=========================================================================-->
Chris Lattner406bddf2005-05-15 05:44:51 +000077<div class="doc_subsection">
Chris Lattner6cb64032008-06-05 08:02:49 +000078<a name="changes">Major Changes in LLVM 2.3</a>
Chris Lattnera2735862008-02-10 07:04:35 +000079</div>
80
81<div class="doc_text">
82
Chris Lattner625a3d82008-06-08 21:34:41 +000083<p>LLVM 2.3 no longer supports llvm-gcc 4.0, it has been replaced with
84 llvm-gcc 4.2.</p>
Chris Lattnercdc44ed2008-02-06 18:00:06 +000085
Chris Lattner625a3d82008-06-08 21:34:41 +000086<p>LLVM 2.3 no longer includes the <tt>llvm-upgrade</tt> tool. It was useful
87 for upgrading LLVM 1.9 files to LLVM 2.x syntax, but you can always use a
88 previous LLVM release to do this. One nice impact of this is that the LLVM
89 regression test suite no longer depends on llvm-upgrade, which makes it run
90 faster.</p>
91
92<p>The <tt>llvm2cpp</tt> tool has been folded into llc, use
Chris Lattnerb076b002008-06-08 21:19:07 +000093 <tt>llc -march=cpp</tt> instead of <tt>llvm2cpp</tt>.</p>
94
Chris Lattner7795ea92008-06-08 02:45:07 +000095<p>LLVM API Changes:</p>
Chris Lattner6cb64032008-06-05 08:02:49 +000096
Chris Lattner7795ea92008-06-08 02:45:07 +000097<ul>
Chris Lattner625a3d82008-06-08 21:34:41 +000098<li>Several core LLVM IR classes have migrated to use the
99 '<tt>FOOCLASS::Create(...)</tt>' pattern instead of '<tt>new
100 FOOCLASS(...)</tt>' (e.g. where FOOCLASS=<tt>BasicBlock</tt>). We hope to
101 standardize on <tt>FOOCLASS::Create</tt> for all IR classes in the future,
102 but not all of them have been moved over yet.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000103<li>LLVM 2.3 renames the LLVMBuilder and LLVMFoldingBuilder classes to
Dan Gohmanaa4a9462008-06-08 22:57:59 +0000104 <a href="http://llvm.org/doxygen/classllvm_1_1IRBuilder.html">IRBuilder</a>.
105 </li>
106<li>MRegisterInfo was renamed to
107 <a href="http://llvm.org/doxygen/classllvm_1_1TargetRegisterInfo.html">
108 TargetRegisterInfo</a>.</li>
109<li>The MappedFile class is gone, please use
110 <a href="http://llvm.org/doxygen/classllvm_1_1MemoryBuffer.html">
111 MemoryBuffer</a> instead.</li>
Chris Lattner625a3d82008-06-08 21:34:41 +0000112<li>The '<tt>-enable-eh</tt>' flag to llc has been removed. Now code should
113 encode whether it is safe to omit unwind information for a function by
114 tagging the Function object with the '<tt>nounwind</tt>' attribute.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000115
116</ul>
Chris Lattnercdc44ed2008-02-06 18:00:06 +0000117</div>
118
119<!--=========================================================================-->
120<div class="doc_subsection">
Chris Lattner625a3d82008-06-08 21:34:41 +0000121<a name="otherprojects">Other LLVM Sub-Projects</a>
122</div>
123
124<div class="doc_text">
Chris Lattnerc75fd522008-06-08 21:58:17 +0000125<p>
126The core LLVM 2.3 distribution currently consists of code from the core LLVM
127repository (which roughly contains the LLVM optimizer, code generators and
128supporting tools) and the llvm-gcc repository. In addition to this code, the
129LLVM Project includes other sub-projects that are in development. The two which
130are the most actively developed are the new <a href="#vmkit">vmkit Project</a>
131and the <a href="#clang">Clang Project</a>.
132</p>
133</div>
134
135<!--=========================================================================-->
136<div class="doc_subsubsection">
137<a name="vmkit">vmkit</a>
138</div>
139
140<div class="doc_text">
141<p>
142The "vmkit" project is a new addition to the LLVM family. It is an
143implementation of a JVM and a CLI Virtual Machines (Microsoft .NET is an
144implementation of the CLI) using the Just-In-Time compiler of LLVM.</p>
145
146<p>The JVM, called JnJVM, executes real-world applications such as Apache
147projects (e.g. Felix and Tomcat) and the SpecJVM98 benchmark. It uses the GNU
148Classpath project for the base classes. The CLI implementation, called N3, is
149its in early stages but can execute simple applications and the "pnetmark"
150benchmark. It uses the pnetlib project as its core library.</p>
151
152<p>The 'vmkit' VMs compare in performance with industrial and top open-source
153VMs on scientific applications. Besides the JIT, the VMs use many features of
154the LLVM framework, including the standard set of optimizations, atomic
155operations, custom function provider and memory manager for JITed methods, and
156specific virtual machine optimizations. vmkit is not an official part of LLVM
1572.3 release. It is publicly available under the LLVM license and can be
158downloaded from:
159</p>
Chris Lattner625a3d82008-06-08 21:34:41 +0000160
161<p>
Chris Lattnerc75fd522008-06-08 21:58:17 +0000162<tt>svn co http://llvm.org/svn/llvm-project/vmkit/trunk vmkit</tt>
Chris Lattner625a3d82008-06-08 21:34:41 +0000163</p>
164
165</div>
166
167<!--=========================================================================-->
Chris Lattnerc75fd522008-06-08 21:58:17 +0000168<div class="doc_subsubsection">
169<a name="clang">Clang</a>
170</div>
171
172<div class="doc_text">
173
174<p>The <a href="http://clang.llvm.org/">Clang project</a> is an effort to build
175a set of new 'LLVM native' front-end technologies for the LLVM optimizer
176and code generator. Clang is continuing to make major strides forward in all
177areas. Its C and Objective-C parsing support is very solid, and the code
178generation support is far enough along to build many C applications. While not
179yet production quality, it is progressing very nicely. In addition, C++
180front-end work has started to make significant progress.</p>
181
182<p>At this point, Clang is most useful if you are interested in source-to-source
183transformations (such as refactoring) and other source-level tools for C and
184Objective-C. Clang now also includes tools for turning C code into pretty HTML,
185and includes a new <a href="http://clang.llvm.org/StaticAnalysis.html">static
186analysis tool</a> in development. This tool is automatically focused on finding
187bugs in C and Objective-C code.</p>
188
189</div>
190
191
192<!-- *********************************************************************** -->
193<div class="doc_section">
194 <a name="whatsnew">What's New?</a>
195</div>
196<!-- *********************************************************************** -->
197
198<!--=========================================================================-->
Chris Lattner625a3d82008-06-08 21:34:41 +0000199<div class="doc_subsection">
Chris Lattnercdc44ed2008-02-06 18:00:06 +0000200<a name="majorfeatures">Major New Features</a>
201</div>
202
203<div class="doc_text">
204
Chris Lattnere38ac152008-02-12 06:29:45 +0000205<p>LLVM 2.3 includes several major new capabilities:</p>
Chris Lattner97beb512007-05-14 06:56:09 +0000206
207<ul>
Chris Lattner625a3d82008-06-08 21:34:41 +0000208<li><p>The biggest change in LLVM 2.3 is Multiple Return Value (MRV) support.
209 MRVs allow LLVM IR to directly represent functions that return multiple
210 values without having to pass them "by reference" in the LLVM IR. This
211 allows a front-end to generate more efficient code, as MRVs are generally
212 returned in registers if a target supports them. See the <a
213 href="LangRef.html#i_getresult">LLVM IR Reference</a> for more details.</p>
214
215 <p>MRVs are fully supported in the LLVM IR, but are not yet fully supported in
216 on all targets. However, it is generally safe to return up to 2 values from
217 a function: most targets should be able to handle at least that. MRV
218 support is a critical requirement for X86-64 ABI support, as X86-64 requires
219 the ability to return multiple registers from functions, and we use MRVs to
220 accomplish this in a direct way.</p></li>
Chris Lattner618a99f2008-06-05 06:57:39 +0000221
Chris Lattner625a3d82008-06-08 21:34:41 +0000222<li><p>LLVM 2.3 includes a complete reimplementation of the "<tt>llvmc</tt>"
223 tool. It is designed to overcome several problems with the original
224 <tt>llvmc</tt> and to provide a superset of the features of the
225 '<tt>gcc</tt>' driver.</p>
Chris Lattner618a99f2008-06-05 06:57:39 +0000226
Chris Lattner625a3d82008-06-08 21:34:41 +0000227<p>The main features of <tt>llvmc2</tt> are:
228 <ul>
229 <li>Extended handling of command line options and smart rules for
230 dispatching them to different tools.</li>
231 <li>Flexible (and extensible) rules for defining different tools.</li>
232 <li>The different intermediate steps performed by tools are represented
233 as edges in the abstract graph.</li>
234 <li>The 'language' for driver behavior definition is tablegen and thus
235 it's relatively easy to add new features.</li>
236 <li>The definition of driver is transformed into set of C++ classes, thus
237 no runtime interpretation is needed.</li>
238 </ul></p>
239 </li>
Chris Lattner618a99f2008-06-05 06:57:39 +0000240
Chris Lattner625a3d82008-06-08 21:34:41 +0000241<li><p>LLVM 2.3 includes a completely rewritten interface for <a
242 href="LinkTimeOptimization.html">Link Time Optimization</a>. This interface
243 is written in C, which allows for easier integration with C code bases, and
244 incorporates improvements we learned about from the first incarnation of the
245 interface.</p></li>
Chris Lattner618a99f2008-06-05 06:57:39 +0000246
Chris Lattner625a3d82008-06-08 21:34:41 +0000247<li><p>The <a href="tutorial/LangImpl1.html">Kaleidoscope tutorial</a> now
248 includes a "port" of the tutorial that <a
249 href="tutorial/OCamlLangImpl1.html">uses the Ocaml bindings</a> to implement
250 the Kaleidoscope language.</p></li>
Chris Lattner618a99f2008-06-05 06:57:39 +0000251
Chris Lattner458e79f2008-02-10 08:18:42 +0000252</ul>
253
Chris Lattner97beb512007-05-14 06:56:09 +0000254</div>
255
Chris Lattnerb7112222008-06-05 06:25:56 +0000256
257<!--=========================================================================-->
258<div class="doc_subsection">
Chris Lattner625a3d82008-06-08 21:34:41 +0000259<a name="llvm-gcc">llvm-gcc 4.2 Improvements</a>
Chris Lattnerb7112222008-06-05 06:25:56 +0000260</div>
261
262<div class="doc_text">
263
Duncan Sands56448462008-06-08 20:18:35 +0000264<p>LLVM 2.3 fully supports the llvm-gcc 4.2 front-end.</p>
Chris Lattnerb7112222008-06-05 06:25:56 +0000265
266<p>llvm-gcc 4.2 includes numerous fixes to better support the Objective-C
267front-end. Objective-C now works very well on Mac OS/X.</p>
268
Chris Lattnerc75fd522008-06-08 21:58:17 +0000269<p>Fortran EQUIVALENCEs are now supported by the gfortran front-end.</p>
270
Chris Lattnerb7112222008-06-05 06:25:56 +0000271<p>llvm-gcc 4.2 includes many other fixes which improve conformance with the
272relevant parts of the GCC testsuite.</p>
273
Chris Lattnerb7112222008-06-05 06:25:56 +0000274</div>
275
276
Chris Lattner0a1fd102007-09-21 03:54:09 +0000277<!--=========================================================================-->
278<div class="doc_subsection">
Chris Lattnerdd6acc02008-02-10 08:17:19 +0000279<a name="coreimprovements">LLVM Core Improvements</a>
280</div>
281
282<div class="doc_text">
283<p>New features include:
284</p>
285
Chris Lattnerdd6acc02008-02-10 08:17:19 +0000286
Chris Lattnerb7112222008-06-05 06:25:56 +0000287Common linkage?
288
Chris Lattner7795ea92008-06-08 02:45:07 +0000289Atomic operation support, Alpha, X86, X86-64, PowerPC. "__sync_synchronize",
Anton Korobeynikovf7c5a6e2008-06-08 10:23:46 +0000290"__sync_val_compare_and_swap", etc
Chris Lattnerb7112222008-06-05 06:25:56 +0000291
292<ul>
Gordon Henriksen03a4ad42008-06-05 12:51:50 +0000293<li>The C and Ocaml bindings have received additional improvements. The
294bindings now cover pass managers, several transformation passes, iteration
295over the LLVM IR, target data, and parameter attribute lists.</li>
Chris Lattnerdd6acc02008-02-10 08:17:19 +0000296</ul>
297
298</div>
299
300<!--=========================================================================-->
301<div class="doc_subsection">
Chris Lattner2b8a52e2008-02-10 07:46:44 +0000302<a name="optimizer">Optimizer Improvements</a>
303</div>
304
305<div class="doc_text">
306
Chris Lattnerdd6acc02008-02-10 08:17:19 +0000307<p>In addition to a huge array of bug fixes and minor performance tweaks, the
Chris Lattnere38ac152008-02-12 06:29:45 +0000308LLVM 2.3 optimizers support a few major enhancements:</p>
Chris Lattner2b8a52e2008-02-10 07:46:44 +0000309
310<ul>
311
Devang Patel33aac002008-06-05 21:44:00 +0000312<li>Loop index set splitting on by default.<p>
313This transformation hoists conditions from loop bodies and reduces loop's
314iteration space to improve performance. For example, <p>
315<pre>
Chris Lattner94fd4472008-06-08 20:25:30 +0000316for (i = LB; i &lt; UB; ++i)
317 if (i &lt;= NV)
Devang Patel33aac002008-06-05 21:44:00 +0000318 LOOP_BODY
319</pre>
320is transformed into
321<pre>
322NUB = min(NV+1, UB)
Chris Lattner94fd4472008-06-08 20:25:30 +0000323for (i = LB; i &lt; NUB; ++i)
Devang Patel33aac002008-06-05 21:44:00 +0000324 LOOP_BODY
325</pre>
326</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000327
Gordon Henriksenf78a57b2008-06-08 22:05:11 +0000328<li>LLVM includes a new <tt>memcpy</tt> optimization pass which removes
Duncan Sands56448462008-06-08 20:18:35 +0000329dead <tt>memcpy</tt> calls, unneeded copies of aggregates, and performs
Chris Lattner7795ea92008-06-08 02:45:07 +0000330return slot optimization. The LLVM optimizer now notices long sequences of
Duncan Sands56448462008-06-08 20:18:35 +0000331consecutive stores and merges them into <tt>memcpy</tt>'s where profitable.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000332
Gabor Greif80ae8a72008-06-05 18:39:01 +0000333<li>Alignment detection for vector memory references and for <tt>memcpy</tt> and
334<tt>memset</tt> is now more aggressive.</li>
Owen Andersonf7647e42008-06-06 16:23:15 +0000335
Chris Lattner7795ea92008-06-08 02:45:07 +0000336<li>The aggressive dead code elimination (ADCE) optimization has been rewritten
337to make it both faster and safer in the presence of code containing infinite
338loops. Some of its prior functionality has been factored out into the loop
339deletion pass, which <em>is</em> safe for infinite loops.</li>
340
341<li>Several optimizations have been sped up, leading to faster code generation
342 with the same code quality.</li>
343
344<li>The 'SimplifyLibCalls' pass, which optimizes calls to libc and libm
345 functions for C-based languages, has been rewritten to be a FunctionPass
346 instead a ModulePass. This allows it to be run more often and to be
347 included at -O1 in llvm-gcc. It was also extended to include more
Duncan Sands56448462008-06-08 20:18:35 +0000348 optimizations and several corner case bugs were fixed.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000349
Duncan Sands0bc15262008-06-08 19:38:43 +0000350<li>LLVM now includes a simple 'Jump Threading' pass, which attempts to simplify
Duncan Sands56448462008-06-08 20:18:35 +0000351 conditional branches using information about predecessor blocks, simplifying
Chris Lattnerb076b002008-06-08 21:19:07 +0000352 the control flow graph. This pass is pretty basic at this point, but
353 catches some important cases and provides a foundation to build on.</li>
354
355<li>Several corner case bugs which could lead to deleting volatile memory
356 accesses have been fixed.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000357</ul>
358
359</div>
360
361<!--=========================================================================-->
362<div class="doc_subsection">
363<a name="codegen">Code Generator Improvements</a>
364</div>
365
366<div class="doc_text">
367
368<p>We put a significant amount of work into the code generator infrastructure,
369which allows us to implement more aggressive algorithms and make it run
370faster:</p>
371
372<ul>
Dan Gohman8709a8062008-06-08 22:49:27 +0000373<li>The code generator now has support for carrying information about memory
374 references throughout the entire code generation process, via the
375 <a href="http://llvm.org/doxygen/classllvm_1_1MachineMemOperand.html">
376 MachineMemOperand</a> class. In the future this will be used to improve
377 both pre-pass and post-pass scheduling, and to improve compiler-debugging
378 output.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000379
Dan Gohmanaa4a9462008-06-08 22:57:59 +0000380<li>The target-independent code generator infrastructure now uses LLVM's
381 <a href="http://llvm.org/doxygen/classllvm_1_1APInt.html">APInt</a>
Chris Lattner7795ea92008-06-08 02:45:07 +0000382 class to handle integer values, which allows it to support integer types
383 larger than 64 bits. Note that support for such types is also dependent on
384 target-specific support. Use of APInt is also a step toward support for
385 non-power-of-2 integer sizes.</li>
386
Chris Lattnerb076b002008-06-08 21:19:07 +0000387<li>LLVM 2.3 includes several compile time speedups for code with large basic
Dan Gohmane7067242008-06-08 22:44:43 +0000388 blocks, particularly in the instruction selection phase, register
389 allocation, scheduling, and tail merging/jump threading.</li>
Chris Lattner7795ea92008-06-08 02:45:07 +0000390
391<li>Several improvements which make llc's <tt>--view-sunit-dags</tt>
392 visualization of scheduling dependency graphs easier to understand.</li>
393
394<li>The code generator allows targets to write patterns that generate subreg
395 references directly in .td files now.</li>
396
397<li><tt>memcpy</tt> lowering in the backend is more aggressive, particularly for
398 <tt>memcpy</tt> calls introduced by the code generator when handling
399 pass-by-value structure argument copies.</li>
Chris Lattnerb076b002008-06-08 21:19:07 +0000400
401<li>Inline assembly with multiple register results now returns those results
402 directly in the appropriate registers, rather than going through memory.
403 Inline assembly that uses constraints like "ir" with immediates now use the
404 'i' form when possible instead of always loading the value in a register.
405 This saves an instruction and reduces register use.</li>
406
407<li>Added support for PIC/GOT style tail calls on x86/32 and initial support
408 for tail calls on PowerPC 32 (it may also work on ppc64 but not
409 thoroughly tested).</li>
Chris Lattner0a1fd102007-09-21 03:54:09 +0000410</ul>
411
412</div>
413
414
415<!--=========================================================================-->
416<div class="doc_subsection">
Chris Lattner6cb64032008-06-05 08:02:49 +0000417<a name="x86specific">X86/X86-64 Specific Improvements</a>
Chris Lattner0a1fd102007-09-21 03:54:09 +0000418</div>
Chris Lattner727c3742007-05-18 06:33:02 +0000419
Chris Lattner89e761c2006-04-18 06:32:08 +0000420<div class="doc_text">
Chris Lattnerdd6acc02008-02-10 08:17:19 +0000421<p>New target-specific features include:
Chris Lattner97beb512007-05-14 06:56:09 +0000422</p>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000423
424<ul>
Chris Lattnerb7112222008-06-05 06:25:56 +0000425<li>llvm-gcc's X86-64 ABI conformance is far improved, particularly in the
Gabor Greif80ae8a72008-06-05 18:39:01 +0000426 area of passing and returning structures by value. llvm-gcc compiled code
Chris Lattnerb7112222008-06-05 06:25:56 +0000427 now interoperates very well on X86-64 systems with other compilers.</li>
428
Duncan Sands0bc15262008-06-08 19:38:43 +0000429<li>Support for Win64 was added. This includes code generation itself, JIT
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000430 support and necessary changes to llvm-gcc.</li>
431
Chris Lattnerb7112222008-06-05 06:25:56 +0000432<li>The LLVM X86 backend now supports the support SSE 4.1 instruction set, and
Chris Lattner7795ea92008-06-08 02:45:07 +0000433 the llvm-gcc 4.2 front-end supports the SSE 4.1 compiler builtins. Various
434 generic vector operations (insert/extract/shuffle) are much more efficient
435 when SSE 4.1 is enabled. The JIT automatically takes advantage of these
436 instructions, but llvm-gcc must be explicitly told to use them, e.g. with
437 <tt>-march=penryn</tt>.</li>
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000438
Chris Lattnerb7112222008-06-05 06:25:56 +0000439<li>The X86 backend now does a number of optimizations that aim to avoid
440 converting numbers back and forth from SSE registers to the X87 floating
441 point stack.</li>
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000442
Chris Lattner618a99f2008-06-05 06:57:39 +0000443<li>The X86 backend supports stack realignment, which is particularly useful for
444 vector code on OS's without 16-byte aligned stacks.</li>
Chris Lattnerb7112222008-06-05 06:25:56 +0000445
446<li>The X86 backend now supports the "sseregparm" options in GCC, which allow
447 functions to be tagged as passing floating point values in SSE
448 registers.</li>
449
450<li>Trampolines (taking the address of a nested function) now work on
Duncan Sands56448462008-06-08 20:18:35 +0000451 Linux/X86-64.</li>
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000452
Chris Lattner6cb64032008-06-05 08:02:49 +0000453<li><tt>__builtin_prefetch</tt> is now compiled into the appropriate prefetch
454 instructions instead of being ignored.</li>
Chris Lattnerb7112222008-06-05 06:25:56 +0000455
Duncan Sands56448462008-06-08 20:18:35 +0000456<li>128-bit integers are now supported on X86-64 targets.</li>
Dan Gohmanb0ec18b2008-06-05 16:15:39 +0000457
Chris Lattner7795ea92008-06-08 02:45:07 +0000458<li>The register allocator can now rematerialize PIC-base computations.</li>
459
Chris Lattnerb076b002008-06-08 21:19:07 +0000460<li>The "t" and "f" inline assembly constraints for the X87 floating point stack
461 now work. However, the "u" constraint is still not fully supported.</li>
462
Chris Lattner8ce1ba42007-05-17 21:41:31 +0000463</ul>
Chris Lattner0a1fd102007-09-21 03:54:09 +0000464
Chris Lattner8ce1ba42007-05-17 21:41:31 +0000465</div>
Chris Lattner72a269f2006-03-03 00:34:26 +0000466
Chris Lattner0a1fd102007-09-21 03:54:09 +0000467<!--=========================================================================-->
468<div class="doc_subsection">
Chris Lattner6cb64032008-06-05 08:02:49 +0000469<a name="targetspecific">Other Target Specific Improvements</a>
470</div>
471
472<div class="doc_text">
473<p>New target-specific features include:
474</p>
475
476<ul>
Gabor Greif80ae8a72008-06-05 18:39:01 +0000477<li>The LLVM C backend now supports vector code.</li>
Chris Lattner6cb64032008-06-05 08:02:49 +0000478</ul>
479
480</div>
481
482
483
484<!--=========================================================================-->
485<div class="doc_subsection">
Chris Lattner0a1fd102007-09-21 03:54:09 +0000486<a name="otherimprovements">Other Improvements</a>
487</div>
488
489<div class="doc_text">
490<p>New features include:
491</p>
492
493<ul>
Chris Lattner618a99f2008-06-05 06:57:39 +0000494<li>LLVM now builds with GCC 4.3.</li>
Chris Lattnerb076b002008-06-08 21:19:07 +0000495<li>Bugpoint now supports running custom scripts (with the <tt>-run-custom</tt>
496 option) to determine how to execute the command and whether it is making
497 forward process.</li>
Chris Lattner0a1fd102007-09-21 03:54:09 +0000498</ul>
499
500</div>
Chris Lattner72a269f2006-03-03 00:34:26 +0000501
Chris Lattner62495762003-10-02 16:38:05 +0000502<!-- *********************************************************************** -->
Misha Brukman80731b92003-11-22 00:38:41 +0000503<div class="doc_section">
504 <a name="portability">Portability and Supported Platforms</a>
505</div>
Chris Lattner62495762003-10-02 16:38:05 +0000506<!-- *********************************************************************** -->
507
Misha Brukman80731b92003-11-22 00:38:41 +0000508<div class="doc_text">
509
John Criswell64307722004-12-08 20:35:47 +0000510<p>LLVM is known to work on the following platforms:</p>
Chris Lattner2c7b0872004-06-01 18:22:41 +0000511
512<ul>
Gabor Greif80ae8a72008-06-05 18:39:01 +0000513<li>Intel and AMD machines (IA32) running Red Hat Linux, Fedora Core and FreeBSD
Reid Spencer9803b402005-05-17 02:47:27 +0000514 (and probably other unix-like systems).</li>
Chris Lattner7422bce2008-02-06 06:30:34 +0000515<li>PowerPC and X86-based Mac OS X systems, running 10.3 and above in 32-bit and
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000516 64-bit modes.</li>
Chris Lattnercdc44ed2008-02-06 18:00:06 +0000517<li>Intel and AMD machines running on Win32 using MinGW libraries (native).</li>
Chris Lattnerbee7b322007-05-23 04:39:32 +0000518<li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
519 support is available for native builds with Visual C++).</li>
Gabor Greif80ae8a72008-06-05 18:39:01 +0000520<li>Sun UltraSPARC workstations running Solaris 10.</li>
John Criswelld5234922005-05-13 20:28:15 +0000521<li>Alpha-based machines running Debian GNU/Linux.</li>
Gabor Greif80ae8a72008-06-05 18:39:01 +0000522<li>Itanium-based (IA64) machines running Linux and HP-UX.</li>
Chris Lattner2c7b0872004-06-01 18:22:41 +0000523</ul>
524
Chris Lattner618a99f2008-06-05 06:57:39 +0000525<p>The core LLVM infrastructure uses GNU autoconf to adapt itself
Brian Gaekee3e557e2004-05-09 05:28:35 +0000526to the machine and operating system on which it is built. However, minor
527porting may be required to get LLVM to work on new platforms. We welcome your
528portability patches and reports of successful builds or error messages.</p>
Chris Lattner3d482502003-10-02 04:57:28 +0000529
Misha Brukman80731b92003-11-22 00:38:41 +0000530</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000531
532<!-- *********************************************************************** -->
Misha Brukman80731b92003-11-22 00:38:41 +0000533<div class="doc_section">
534 <a name="knownproblems">Known Problems</a>
535</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000536<!-- *********************************************************************** -->
537
Misha Brukman80731b92003-11-22 00:38:41 +0000538<div class="doc_text">
539
540<p>This section contains all known problems with the LLVM system, listed by
Chris Lattner3d482502003-10-02 04:57:28 +0000541component. As new problems are discovered, they will be added to these
Chris Lattnerb84f3322003-12-12 21:22:16 +0000542sections. If you run into a problem, please check the <a
Chris Lattnera69595e2005-10-29 07:07:09 +0000543href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
Chris Lattnerb84f3322003-12-12 21:22:16 +0000544there isn't already one.</p>
Chris Lattner3d482502003-10-02 04:57:28 +0000545
Misha Brukman80731b92003-11-22 00:38:41 +0000546</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000547
Chris Lattnerb911de42004-03-14 02:03:02 +0000548<!-- ======================================================================= -->
549<div class="doc_subsection">
550 <a name="experimental">Experimental features included with this release</a>
551</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000552
Chris Lattnerb911de42004-03-14 02:03:02 +0000553<div class="doc_text">
554
Misha Brukmanfa50a222004-05-12 21:46:05 +0000555<p>The following components of this LLVM release are either untested, known to
556be broken or unreliable, or are in early development. These components should
557not be relied on, and bugs should not be filed against them, but they may be
558useful to some people. In particular, if you would like to work on one of these
Chris Lattnere38ac152008-02-12 06:29:45 +0000559components, please contact us on the <a
560href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
Chris Lattnerb911de42004-03-14 02:03:02 +0000561
562<ul>
Chris Lattnere38ac152008-02-12 06:29:45 +0000563<li>The MSIL, IA64, Alpha, SPU, and MIPS backends are experimental.</li>
Duncan Sands56448462008-06-08 20:18:35 +0000564<li>The llc "<tt>-filetype=asm</tt>" (the default) is the only supported
Chris Lattner7422bce2008-02-06 06:30:34 +0000565 value for this option.</li>
Chris Lattnerb911de42004-03-14 02:03:02 +0000566</ul>
567
568</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000569
Misha Brukman80731b92003-11-22 00:38:41 +0000570<!-- ======================================================================= -->
571<div class="doc_subsection">
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000572 <a name="x86-be">Known problems with the X86 back-end</a>
John Criswell3bdbd302005-11-08 21:11:33 +0000573</div>
574
575<div class="doc_text">
576
577<ul>
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000578 <li>The X86 backend does not yet support
579 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
580 floating point stack</a>. It supports the 'f' and 't' constraints, but not
581 'u'.</li>
Chris Lattnerb076b002008-06-08 21:19:07 +0000582 <li>The X86 backend generates inefficient floating point code when configured
583 to generate code for systems that don't have SSE2.</li>
Duncan Sands0bc15262008-06-08 19:38:43 +0000584 <li>Win64 code generation wasn't widely tested. Everything should work, but we
Anton Korobeynikov486c7d32008-06-08 10:24:13 +0000585 expect small issues to happen. Also, llvm-gcc cannot build mingw64 runtime
586 currently due
587 to <a href="http://llvm.org/PR2255">several</a>
588 <a href="http://llvm.org/PR2257">bugs</a> in FP stackifier
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000589</ul>
590
591</div>
592
593<!-- ======================================================================= -->
594<div class="doc_subsection">
595 <a name="ppc-be">Known problems with the PowerPC back-end</a>
596</div>
597
598<div class="doc_text">
599
600<ul>
Nicolas Geoffray77d99502007-05-15 09:21:28 +0000601<li>The Linux PPC32/ABI support needs testing for the interpreter and static
Chris Lattnerbee7b322007-05-23 04:39:32 +0000602compilation, and lacks support for debug information.</li>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000603</ul>
604
605</div>
606
607<!-- ======================================================================= -->
608<div class="doc_subsection">
Chris Lattner97beb512007-05-14 06:56:09 +0000609 <a name="arm-be">Known problems with the ARM back-end</a>
610</div>
611
612<div class="doc_text">
613
614<ul>
Chris Lattnerbee7b322007-05-23 04:39:32 +0000615<li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
Duncan Sands47fc0a22007-09-26 15:59:54 +0000616processors, thumb programs can crash or produce wrong
Chris Lattnerbee7b322007-05-23 04:39:32 +0000617results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
Chris Lattner97beb512007-05-14 06:56:09 +0000618<li>Compilation for ARM Linux OABI (old ABI) is supported, but not fully tested.
619</li>
Chris Lattnerb076b002008-06-08 21:19:07 +0000620<li>There is a bug in QEMU-ARM (&lt;= 0.9.0) which causes it to incorrectly
621 execute
Chris Lattnerbee7b322007-05-23 04:39:32 +0000622programs compiled with LLVM. Please use more recent versions of QEMU.</li>
Chris Lattner97beb512007-05-14 06:56:09 +0000623</ul>
624
625</div>
626
627<!-- ======================================================================= -->
628<div class="doc_subsection">
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000629 <a name="sparc-be">Known problems with the SPARC back-end</a>
630</div>
631
632<div class="doc_text">
633
634<ul>
635<li>The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not
636 support the 64-bit SPARC ABI (-m64).</li>
637</ul>
638
639</div>
640
641<!-- ======================================================================= -->
642<div class="doc_subsection">
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000643 <a name="alpha-be">Known problems with the Alpha back-end</a>
644</div>
645
646<div class="doc_text">
647
648<ul>
649
650<li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
651appropriate nops inserted to ensure restartability.</li>
652
John Criswell3bdbd302005-11-08 21:11:33 +0000653</ul>
654</div>
655
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000656<!-- ======================================================================= -->
657<div class="doc_subsection">
658 <a name="ia64-be">Known problems with the IA64 back-end</a>
659</div>
660
661<div class="doc_text">
662
663<ul>
664
665<li>C++ programs are likely to fail on IA64, as calls to <tt>setjmp</tt> are
666made where the argument is not 16-byte aligned, as required on IA64. (Strictly
667speaking this is not a bug in the IA64 back-end; it will also be encountered
668when building C++ programs using the C back-end.)</li>
669
670<li>The C++ front-end does not use <a href="http://llvm.org/PR406">IA64
671ABI compliant layout of v-tables</a>. In particular, it just stores function
672pointers instead of function descriptors in the vtable. This bug prevents
673mixing C++ code compiled with LLVM with C++ objects compiled by other C++
674compilers.</li>
675
676<li>There are a few ABI violations which will lead to problems when mixing LLVM
677output with code built with other compilers, particularly for floating-point
678programs.</li>
679
Duncan Sands0bc15262008-06-08 19:38:43 +0000680<li>Defining vararg functions is not supported (but calling them is OK).</li>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000681
Chris Lattner98a33492007-05-09 04:58:11 +0000682<li>The Itanium backend has bitrotted somewhat.</li>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000683</ul>
684
685</div>
686
687<!-- ======================================================================= -->
688<div class="doc_subsection">
Chris Lattner97beb512007-05-14 06:56:09 +0000689 <a name="c-be">Known problems with the C back-end</a>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000690</div>
691
692<div class="doc_text">
693
694<ul>
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000695<li><a href="http://llvm.org/PR802">The C backend has only basic support for
696 inline assembly code</a>.</li>
Chris Lattner8e061162007-09-26 06:01:35 +0000697<li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
698 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
Duncan Sands56448462008-06-08 20:18:35 +0000699 C++ code compiled with llc or native compilers.</li>
Duncan Sandse09506a2008-02-10 13:40:55 +0000700<li>The C backend does not support all exception handling constructs.</li>
Chris Lattnerb81f10e2006-11-18 07:51:14 +0000701</ul>
702
703</div>
John Criswell3bdbd302005-11-08 21:11:33 +0000704
Misha Brukman80731b92003-11-22 00:38:41 +0000705
706<!-- ======================================================================= -->
707<div class="doc_subsection">
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000708 <a name="c-fe">Known problems with the llvm-gcc C front-end</a>
Misha Brukman80731b92003-11-22 00:38:41 +0000709</div>
Chris Lattner178f3db2003-10-02 05:07:23 +0000710
Chris Lattner3d482502003-10-02 04:57:28 +0000711<!-- _______________________________________________________________________ -->
Chris Lattner5a8a7282003-12-14 05:03:43 +0000712<div class="doc_subsubsection">Bugs</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000713
Misha Brukman80731b92003-11-22 00:38:41 +0000714<div class="doc_text">
Chris Lattner72a269f2006-03-03 00:34:26 +0000715
Chris Lattnercdc44ed2008-02-06 18:00:06 +0000716<p>llvm-gcc does not currently support <a href="http://llvm.org/PR869">Link-Time
717Optimization</a> on most platforms "out-of-the-box". Please inquire on the
Chris Lattner97beb512007-05-14 06:56:09 +0000718llvmdev mailing list if you are interested.</p>
Chris Lattner44124232006-08-08 17:27:28 +0000719
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000720<p>The only major language feature of GCC not supported by llvm-gcc is
721 the <tt>__builtin_apply</tt> family of builtins. However, some extensions
722 are only supported on some targets. For example, trampolines are only
Duncan Sands56448462008-06-08 20:18:35 +0000723 supported on some targets (these are used when you take the address of a
724 nested function).</p>
Misha Brukman80731b92003-11-22 00:38:41 +0000725
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000726<p>If you run into GCC extensions which are not supported, please let us know.
727</p>
Chris Lattner3d482502003-10-02 04:57:28 +0000728
Misha Brukman80731b92003-11-22 00:38:41 +0000729</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000730
Misha Brukman80731b92003-11-22 00:38:41 +0000731<!-- ======================================================================= -->
732<div class="doc_subsection">
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000733 <a name="c++-fe">Known problems with the llvm-gcc C++ front-end</a>
Misha Brukman80731b92003-11-22 00:38:41 +0000734</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000735
Misha Brukman80731b92003-11-22 00:38:41 +0000736<div class="doc_text">
737
Chris Lattner97beb512007-05-14 06:56:09 +0000738<p>The C++ front-end is considered to be fully
Chris Lattnerb5bb5972004-12-07 08:04:13 +0000739tested and works for a number of non-trivial programs, including LLVM
Chris Lattner97beb512007-05-14 06:56:09 +0000740itself, Qt, Mozilla, etc.</p>
Misha Brukman80731b92003-11-22 00:38:41 +0000741
Misha Brukman80731b92003-11-22 00:38:41 +0000742<ul>
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000743<li>Exception handling works well on the X86 and PowerPC targets, including
Duncan Sands56448462008-06-08 20:18:35 +0000744X86-64 darwin. This works when linking to a libstdc++ compiled by GCC. It is
745supported on X86-64 linux, but that is disabled by default in this release.</li>
Misha Brukman80731b92003-11-22 00:38:41 +0000746</ul>
Chris Lattner46ecf612003-10-07 22:14:37 +0000747
Misha Brukman80731b92003-11-22 00:38:41 +0000748</div>
749
Misha Brukman80731b92003-11-22 00:38:41 +0000750
Chris Lattnere38ac152008-02-12 06:29:45 +0000751<!-- ======================================================================= -->
752<div class="doc_subsection">
Chris Lattnera1a4c9a2008-06-05 06:35:40 +0000753 <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a>
Chris Lattnere38ac152008-02-12 06:29:45 +0000754</div>
755
756<div class="doc_text">
757The llvm-gcc 4.2 Ada compiler works fairly well, however this is not a mature
758technology and problems should be expected.
759<ul>
Duncan Sands56448462008-06-08 20:18:35 +0000760<li>The Ada front-end currently only builds on X86-32. This is mainly due
Chris Lattnere38ac152008-02-12 06:29:45 +0000761to lack of trampoline support (pointers to nested functions) on other platforms,
Duncan Sands56448462008-06-08 20:18:35 +0000762however it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
Chris Lattnere38ac152008-02-12 06:29:45 +0000763which does support trampolines.</li>
764<li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
765Workaround: configure with --disable-bootstrap.</li>
766<li>The c380004 and <a href="http://llvm.org/PR2010">c393010</a> ACATS tests
Duncan Sands56448462008-06-08 20:18:35 +0000767fail (c380004 also fails with gcc-4.2 mainline). When built at -O3, the
768<a href="http://llvm.org/PR2421">cxg2021</a> ACATS test also fails.</li>
769<li>Some gcc specific Ada tests continue to crash the compiler. The testsuite
770reports most tests as having failed even though they pass.</li>
Chris Lattnere38ac152008-02-12 06:29:45 +0000771<li>The -E binder option (exception backtraces)
772<a href="http://llvm.org/PR1982">does not work</a> and will result in programs
773crashing if an exception is raised. Workaround: do not use -E.</li>
774<li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
775or finish at a non-byte offset</a> in a record. Workaround: do not pack records
776or use representation clauses that result in a field of a non-discrete type
777starting or finishing in the middle of a byte.</li>
Chris Lattnerb076b002008-06-08 21:19:07 +0000778<li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
779'main' as generated by the Ada binder to be invalid</a>.
780Workaround: hand edit the file to use pointers for <tt>argv</tt> and
781<tt>envp</tt> rather than integers.</li>
782<li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
783ignored</a>.</li>
Chris Lattnere38ac152008-02-12 06:29:45 +0000784</ul>
785</div>
786
Chris Lattner3d482502003-10-02 04:57:28 +0000787<!-- *********************************************************************** -->
Misha Brukman80731b92003-11-22 00:38:41 +0000788<div class="doc_section">
789 <a name="additionalinfo">Additional Information</a>
790</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000791<!-- *********************************************************************** -->
792
Misha Brukman80731b92003-11-22 00:38:41 +0000793<div class="doc_text">
794
Chris Lattnercb5596d2005-05-16 17:13:10 +0000795<p>A wide variety of additional information is available on the <a
Chris Lattnere0c1df42007-05-18 00:44:29 +0000796href="http://llvm.org">LLVM web page</a>, in particular in the <a
797href="http://llvm.org/docs/">documentation</a> section. The web page also
Reid Spencerc7f87f22007-07-09 08:04:31 +0000798contains versions of the API documentation which is up-to-date with the
799Subversion version of the source code.
Misha Brukman96158092005-03-30 19:14:24 +0000800You can access versions of these documents specific to this release by going
801into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
Chris Lattner3d482502003-10-02 04:57:28 +0000802
Misha Brukman80731b92003-11-22 00:38:41 +0000803<p>If you have any questions or comments about LLVM, please feel free to contact
Chris Lattnera69595e2005-10-29 07:07:09 +0000804us via the <a href="http://llvm.org/docs/#maillist"> mailing
Chris Lattnerb84f3322003-12-12 21:22:16 +0000805lists</a>.</p>
Chris Lattner3d482502003-10-02 04:57:28 +0000806
Misha Brukman80731b92003-11-22 00:38:41 +0000807</div>
Chris Lattner3d482502003-10-02 04:57:28 +0000808
809<!-- *********************************************************************** -->
Chris Lattner3d482502003-10-02 04:57:28 +0000810
Misha Brukman80731b92003-11-22 00:38:41 +0000811<hr>
Misha Brukman68aab3b2003-11-22 01:23:39 +0000812<address>
Misha Brukman8834af92003-12-21 22:53:21 +0000813 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman68aab3b2003-11-22 01:23:39 +0000814 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
815 <a href="http://validator.w3.org/check/referer"><img
Chris Lattner458e79f2008-02-10 08:18:42 +0000816 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
Misha Brukman68aab3b2003-11-22 01:23:39 +0000817
Chris Lattnere0c1df42007-05-18 00:44:29 +0000818 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
Misha Brukman80731b92003-11-22 00:38:41 +0000819 Last modified: $Date$
Misha Brukman68aab3b2003-11-22 01:23:39 +0000820</address>
Chris Lattner3d482502003-10-02 04:57:28 +0000821
Misha Brukman80731b92003-11-22 00:38:41 +0000822</body>
823</html>