1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <link rel="stylesheet" href="llvm.css" type="text/css">
7 <title>LLVM 2.0 Release Notes</title>
11 <div class="doc_title">LLVM 2.0 Release Notes</div>
14 <li><a href="#intro">Introduction</a></li>
15 <li><a href="#whatsnew">What's New?</a></li>
16 <li><a href="GettingStarted.html">Installation Instructions</a></li>
17 <li><a href="#portability">Portability and Supported Platforms</a></li>
18 <li><a href="#knownproblems">Known Problems</a>
19 <li><a href="#additionalinfo">Additional Information</a></li>
22 <div class="doc_author">
23 <p>Written by the <a href="http://llvm.org">LLVM Team</a><p>
26 <!-- *********************************************************************** -->
27 <div class="doc_section">
28 <a name="intro">Introduction</a>
30 <!-- *********************************************************************** -->
32 <div class="doc_text">
34 <p>This document contains the release notes for the LLVM compiler
35 infrastructure, release 2.0. Here we describe the status of LLVM, including any
36 known problems and major improvements from the previous release. All LLVM
37 releases may be downloaded from the <a href="http://llvm.org/releases/">LLVM
38 releases web site</a>.
40 <p>For more information about LLVM, including information about the latest
41 release, please check out the <a href="http://llvm.org/">main LLVM
42 web site</a>. If you have questions or comments, the <a
43 href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
44 list</a> is a good place to send them.</p>
46 <p>Note that if you are reading this file from CVS or the main LLVM web page,
47 this document applies to the <i>next</i> release, not the current one. To see
48 the release notes for the current or previous releases, see the <a
49 href="http://llvm.org/releases/">releases page</a>.</p>
53 <!-- *********************************************************************** -->
54 <div class="doc_section">
55 <a name="whatsnew">What's New?</a>
57 <!-- *********************************************************************** -->
59 <div class="doc_text">
61 <p>This is the eleventh public release of the LLVM Compiler Infrastructure.
62 Being the first major release since 1.0, we took this as an opportunity to
63 break backwards compatibility with the LLVM 1.x bytecode and .ll file format.
64 If you have LLVM 1.9 .ll files that you would like to upgrade to LLVM 2.x, we
65 recommend the use of the stand alone <a href=#llvm-upgrade">llvm-upgrade</a>
66 tool. We intend to keep compatibility with .ll and .bc formats within the 2.x
72 incorporates a large number of enhancements, new features, and bug
73 fixes. We recommend that all users of previous LLVM versions upgrade.
78 <!--=========================================================================-->
79 <div class="doc_subsection">
80 <a name="newfeatures">New Features in LLVM 2.0</a>
83 <!--_________________________________________________________________________-->
84 <div class="doc_subsubsection"><a name="optimizer">Optimizer
85 Improvements</a></div>
86 <div class="doc_text">
87 <p>The mid-level optimizer is now faster and produces better code in many cases.
88 Significant changes include:</p>
96 <!--_________________________________________________________________________-->
97 <div class="doc_subsubsection"><a name="codegen">Code
98 Generator Enhancements</a></div>
100 <div class="doc_text">
102 The LLVM Target-Independent code generator now supports more target features and
103 optimizes many cases more aggressively. New features include:
110 <p>In addition, the LLVM target description format has itself been extended in
117 <p>Further, several significant target-specific enhancements are included in
126 <!--_________________________________________________________________________-->
127 <div class="doc_subsubsection"><a name="other">Other Improvements</a></div>
128 <div class="doc_text">
131 <p>More specific changes include:</p>
140 <!-- *********************************************************************** -->
141 <div class="doc_section">
142 <a name="portability">Portability and Supported Platforms</a>
144 <!-- *********************************************************************** -->
146 <div class="doc_text">
148 <p>LLVM is known to work on the following platforms:</p>
151 <li>Intel and AMD machines running Red Hat Linux, Fedora Core and FreeBSD
152 (and probably other unix-like systems).</li>
153 <li>Intel and AMD machines running on Win32 using MinGW libraries (native)</li>
154 <li>Sun UltraSPARC workstations running Solaris 8.</li>
155 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
156 support is available for native builds with Visual C++).</li>
157 <li>PowerPC and X86-based Mac OS X systems, running 10.2 and above in 32-bit and
159 <li>Alpha-based machines running Debian GNU/Linux.</li>
160 <li>Itanium-based machines running Linux and HP-UX.</li>
163 <p>The core LLVM infrastructure uses
164 <a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
165 to the machine and operating system on which it is built. However, minor
166 porting may be required to get LLVM to work on new platforms. We welcome your
167 portability patches and reports of successful builds or error messages.</p>
171 <!-- *********************************************************************** -->
172 <div class="doc_section">
173 <a name="knownproblems">Known Problems</a>
175 <!-- *********************************************************************** -->
177 <div class="doc_text">
179 <p>This section contains all known problems with the LLVM system, listed by
180 component. As new problems are discovered, they will be added to these
181 sections. If you run into a problem, please check the <a
182 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
183 there isn't already one.</p>
187 <!-- ======================================================================= -->
188 <div class="doc_subsection">
189 <a name="experimental">Experimental features included with this release</a>
192 <div class="doc_text">
194 <p>The following components of this LLVM release are either untested, known to
195 be broken or unreliable, or are in early development. These components should
196 not be relied on, and bugs should not be filed against them, but they may be
197 useful to some people. In particular, if you would like to work on one of these
198 components, please contact us on the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
201 <li>The <tt>-cee</tt> pass is known to be buggy, and may be removed in in a
203 <li>The IA64 code generator is experimental.</li>
204 <li>The ARM code generator is experimental.</li>
205 <li>The Alpha JIT is experimental.</li>
206 <li>"<tt>-filetype=asm</tt>" (the default) is the only supported value for the
207 <tt>-filetype</tt> llc option.</li>
212 <!-- ======================================================================= -->
213 <div class="doc_subsection">
214 <a name="x86-be">Known problems with the X86 back-end</a>
217 <div class="doc_text">
220 <li>The X86 backend does not yet support <a href="http://llvm.org/PR879">inline
221 assembly that uses the X86 floating point stack</a>.</li>
226 <!-- ======================================================================= -->
227 <div class="doc_subsection">
228 <a name="ppc-be">Known problems with the PowerPC back-end</a>
231 <div class="doc_text">
234 <li><a href="http://llvm.org/PR642">PowerPC backend does not correctly
235 implement ordered FP comparisons</a>.</li>
240 <!-- ======================================================================= -->
241 <div class="doc_subsection">
242 <a name="sparc-be">Known problems with the SPARC back-end</a>
245 <div class="doc_text">
248 <li>The SPARC backend only supports the 32-bit SPARC ABI (-m32), it does not
249 support the 64-bit SPARC ABI (-m64).</li>
254 <!-- ======================================================================= -->
255 <div class="doc_subsection">
256 <a name="c-be">Known problems with the C back-end</a>
259 <div class="doc_text">
263 <li>The C back-end produces code that violates the ANSI C Type-Based Alias
264 Analysis rules. As such, special options may be necessary to compile the code
265 (for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
266 problem probably cannot be fixed.</li>
268 <li><a href="http://llvm.org/PR56">Zero arg vararg functions are not
269 supported</a>. This should not affect LLVM produced by the C or C++
272 <li>The C backend does not correctly implement the <a
273 href="LangRef.html#int_stacksave"><tt>llvm.stacksave</tt></a> or
274 <a href="LangRef.html#int_stackrestore"><tt>llvm.stackrestore</tt></a>
275 intrinsics. This means that some code compiled by it can run out of stack
276 space if they depend on these (e.g. C99 varargs).</li>
278 <li><a href="http://llvm.org/PR802">The C backend does not support inline
279 assembly code</a>.</li>
284 <!-- ======================================================================= -->
285 <div class="doc_subsection">
286 <a name="alpha-be">Known problems with the Alpha back-end</a>
289 <div class="doc_text">
293 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
294 appropriate nops inserted to ensure restartability.</li>
299 <!-- ======================================================================= -->
300 <div class="doc_subsection">
301 <a name="ia64-be">Known problems with the IA64 back-end</a>
304 <div class="doc_text">
308 <li>C++ programs are likely to fail on IA64, as calls to <tt>setjmp</tt> are
309 made where the argument is not 16-byte aligned, as required on IA64. (Strictly
310 speaking this is not a bug in the IA64 back-end; it will also be encountered
311 when building C++ programs using the C back-end.)</li>
313 <li>The C++ front-end does not use <a href="http://llvm.org/PR406">IA64
314 ABI compliant layout of v-tables</a>. In particular, it just stores function
315 pointers instead of function descriptors in the vtable. This bug prevents
316 mixing C++ code compiled with LLVM with C++ objects compiled by other C++
319 <li>There are a few ABI violations which will lead to problems when mixing LLVM
320 output with code built with other compilers, particularly for floating-point
323 <li>Defining vararg functions is not supported (but calling them is ok).</li>
325 <li>The Itanium backend has bitrotted somewhat.</li>
330 <!-- ======================================================================= -->
331 <div class="doc_subsection">
332 <a name="arm-be">Known problems with the ARM back-end</a>
335 <div class="doc_text">
338 <li>The ARM backend is currently in early development stages, it is not
339 ready for production use.</li>
344 <!-- ======================================================================= -->
345 <div class="doc_subsection">
346 <a name="core">Known problems with the LLVM Core</a>
349 <div class="doc_text">
352 <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not
357 <!-- ======================================================================= -->
358 <div class="doc_subsection">
359 <a name="c-fe">Known problems with the C front-end</a>
362 <!-- _______________________________________________________________________ -->
363 <div class="doc_subsubsection">Bugs</div>
365 <div class="doc_text">
369 <p>llvm-gcc4 is far more stable and produces better code than llvm-gcc3, but
370 does not currently support <a href="http://llvm.org/PR869">Link-Time
371 Optimization</a> or <a href="http://llvm.org/PR870">C++ Exception Handling</a>,
372 which llvm-gcc3 does.</p>
374 <p>llvm-gcc4 does not support the <a href="http://llvm.org/PR947">GCC indirect
375 goto extension</a>, but llvm-gcc3 does.</p>
379 <!-- _______________________________________________________________________ -->
380 <div class="doc_subsubsection">
384 <div class="doc_text">
388 <li>"long double" is transformed by the front-end into "double". There is no
389 support for floating point data types of any size other than 32 and 64
392 <li>Although many GCC extensions are supported, some are not. In particular,
393 the following extensions are known to <b>not be</b> supported:
395 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
396 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html#Nested%20Functions">Nested Functions</a>: As in Algol and Pascal, lexical scoping of functions.</li>
397 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
398 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
399 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
402 <p>The following GCC extensions are <b>partially</b> supported. An ignored
403 attribute means that the LLVM compiler ignores the presence of the attribute,
404 but the code should still work. An unsupported attribute is one which is
405 ignored by the LLVM compiler and will cause a different interpretation of
409 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html#Variable%20Length">Variable Length</a>:
410 Arrays whose length is computed at run time.<br>
411 Supported, but allocated stack space is not freed until the function returns (noted above).</li>
413 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
415 Declaring that functions have no side effects or that they can never
418 <b>Supported:</b> <tt>constructor</tt>, <tt>destructor</tt>,
419 <tt>deprecated</tt>, <tt>fastcall</tt>, <tt>format</tt>,
420 <tt>format_arg</tt>, <tt>non_null</tt>, <tt>noreturn</tt>,
421 <tt>section</tt>, <tt>stdcall</tt>, <tt>unused</tt>, <tt>used</tt>,
422 <tt>visibility</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
424 <b>Ignored:</b> <tt>noinline</tt>,
425 <tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
426 <tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
428 <b>Unsupported:</b> <tt>alias</tt>, <tt>regparm</tt>, all other target specific
431 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html#Variable%20Attributes">Variable Attributes</a>:
432 Specifying attributes of variables.<br>
433 <b>Supported:</b> <tt>cleanup</tt>, <tt>common</tt>, <tt>nocommon</tt>,
434 <tt>deprecated</tt>, <tt>dllimport</tt>, <tt>dllexport</tt>,
435 <tt>section</tt>, <tt>transparent_union</tt>, <tt>unused</tt>,
436 <tt>used</tt>, <tt>weak</tt><br>
438 <b>Unsupported:</b> <tt>aligned</tt>, <tt>mode</tt>, <tt>packed</tt>,
439 <tt>shared</tt>, <tt>tls_model</tt>,
440 <tt>vector_size</tt>, all target specific attributes.
443 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
444 <b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
445 <tt>deprecated</tt>, <tt>may_alias</tt><br>
447 <b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
448 all target specific attributes.</li>
450 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other%20Builtins">Other Builtins</a>:
451 Other built-in functions.<br>
452 We support all builtins which have a C language equivalent (e.g.,
453 <tt>__builtin_cos</tt>), <tt>__builtin_alloca</tt>,
454 <tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
455 <tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
456 (currently ignored). We also support builtins for ISO C99 floating
457 point comparison macros (e.g., <tt>__builtin_islessequal</tt>),
458 <tt>__builtin_prefetch</tt>, <tt>__builtin_popcount[ll]</tt>,
459 <tt>__builtin_clz[ll]</tt>, and <tt>__builtin_ctz[ll]</tt>.</li>
462 <p>The following extensions <b>are</b> known to be supported:</p>
465 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels and computed gotos.</li>
466 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
467 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression.</li>
468 <li><a href="http://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</li>
469 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#Conditionals">Conditionals</a>: Omitting the middle operand of a <code>?:</code> expression.</li>
470 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html#Long%20Long">Long Long</a>: Double-word integers.</li>
471 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Complex.html#Complex">Complex</a>: Data types for complex numbers.</li>
472 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Hex-Floats.html#Hex%20Floats">Hex Floats</a>:Hexadecimal floating-point constants.</li>
473 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html#Zero%20Length">Zero Length</a>: Zero-length arrays.</li>
474 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Empty-Structures.html#Empty%20Structures">Empty Structures</a>: Structures with no members.</li>
475 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments.</li>
476 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
477 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands.</li>
478 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
479 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Asm-Labels.html#Asm%20Labels">Asm Labels</a>: Specifying the assembler name to use for a C symbol.</li>
480 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Explicit-Reg-Vars.html#Explicit%20Reg%20Vars">Explicit Reg Vars</a>: Defining variables residing in specified registers.</li>
481 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html#Vector%20Extensions">Vector Extensions</a>: Using vector instructions through built-in functions.</li>
482 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Target-Builtins.html#Target%20Builtins">Target Builtins</a>: Built-in functions specific to particular targets.</li>
483 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue.</li>
484 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>: Arithmetic on <code>void</code>-pointers and function pointers.</li>
485 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
486 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
487 or arrays as values.</li>
488 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
489 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>: Casting to union type from any member of the union.</li>
490 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
491 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
492 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
493 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Comments.html#C_002b_002b-Comments">C++ Comments</a>: C++ comments are recognized.</li>
494 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
495 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Character-Escapes.html#Character%20Escapes">Character Escapes</a>: <code>\e</code> stands for the character <ESC>.</li>
496 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
497 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Inline.html#Inline">Inline</a>: Defining inline functions (as fast as macros).</li>
498 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alternate-Keywords.html#Alternate%20Keywords">Alternate Keywords</a>:<code>__const__</code>, <code>__asm__</code>, etc., for header files.</li>
499 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Incomplete-Enums.html#Incomplete%20Enums">Incomplete Enums</a>: <code>enum foo;</code>, with details to follow.</li>
500 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html#Function%20Names">Function Names</a>: Printable strings which are the name of the current function.</li>
501 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Return-Address.html#Return%20Address">Return Address</a>: Getting the return or frame address of a function.</li>
502 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.</li>
503 <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
508 <p>If you run into GCC extensions which have not been included in any of these
509 lists, please let us know (also including whether or not they work).</p>
513 <!-- ======================================================================= -->
514 <div class="doc_subsection">
515 <a name="c++-fe">Known problems with the C++ front-end</a>
518 <div class="doc_text">
520 <p>For this release, the C++ front-end is considered to be fully
521 tested and works for a number of non-trivial programs, including LLVM
526 <!-- _______________________________________________________________________ -->
527 <div class="doc_subsubsection">
531 <div class="doc_text">
533 <li>llvm-gcc4 does not support C++ exception handling at all yet.</li>
535 <li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
536 performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
537 function and in the <tt>setjmp</tt> receiver function may not be run.
538 Objects in intervening stack frames will be destroyed, however (which is
539 better than most compilers).</li>
541 <li>The LLVM C++ front-end follows the <a
542 href="http://www.codesourcery.com/cxx-abi">Itanium C++ ABI</a>.
543 This document, which is not Itanium specific, specifies a standard for name
544 mangling, class layout, v-table layout, RTTI formats, and other C++
545 representation issues. Because we use this API, code generated by the LLVM
546 compilers should be binary compatible with machine code generated by other
547 Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
548 <i>However</i>, the exception handling mechanism used by llvm-gcc3 is very
549 different from the model used in the Itanium ABI, so <b>exceptions will not
550 interact correctly</b>. </li>
558 <!-- *********************************************************************** -->
559 <div class="doc_section">
560 <a name="additionalinfo">Additional Information</a>
562 <!-- *********************************************************************** -->
564 <div class="doc_text">
566 <p>A wide variety of additional information is available on the <a
567 href="http://llvm.org">LLVM web page</a>, including <a
568 href="http://llvm.org/docs/">documentation</a> and <a
569 href="http://llvm.org/pubs/">publications describing algorithms and
570 components implemented in LLVM</a>. The web page also contains versions of the
571 API documentation which is up-to-date with the CVS version of the source code.
572 You can access versions of these documents specific to this release by going
573 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
575 <p>If you have any questions or comments about LLVM, please feel free to contact
576 us via the <a href="http://llvm.org/docs/#maillist"> mailing
581 <!-- *********************************************************************** -->
585 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
586 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
587 <a href="http://validator.w3.org/check/referer"><img
588 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
590 <a href="http://llvm.org/">The LLVM Compiler Infrastructure</a><br>
591 Last modified: $Date$