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.8 Release Notes</title>
11 <div class="doc_title">LLVM 2.8 Release Notes</div>
13 <img align=right src="http://llvm.org/img/DragonSmall.png"
14 width="136" height="136" alt="LLVM Dragon Logo">
17 <li><a href="#intro">Introduction</a></li>
18 <li><a href="#subproj">Sub-project Status Update</a></li>
19 <li><a href="#externalproj">External Projects Using LLVM 2.8</a></li>
20 <li><a href="#whatsnew">What's New in LLVM 2.8?</a></li>
21 <li><a href="GettingStarted.html">Installation Instructions</a></li>
22 <li><a href="#knownproblems">Known Problems</a></li>
23 <li><a href="#additionalinfo">Additional Information</a></li>
26 <div class="doc_author">
27 <p>Written by the <a href="http://llvm.org">LLVM Team</a></p>
31 <h1 style="color:red">These are in-progress notes for the upcoming LLVM 2.8
34 <a href="http://llvm.org/releases/2.7/docs/ReleaseNotes.html">LLVM 2.7
35 Release Notes</a>.</h1>
38 <!-- *********************************************************************** -->
39 <div class="doc_section">
40 <a name="intro">Introduction</a>
42 <!-- *********************************************************************** -->
44 <div class="doc_text">
46 <p>This document contains the release notes for the LLVM Compiler
47 Infrastructure, release 2.8. Here we describe the status of LLVM, including
48 major improvements from the previous release and significant known problems.
49 All LLVM releases may be downloaded from the <a
50 href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
52 <p>For more information about LLVM, including information about the latest
53 release, please check out the <a href="http://llvm.org/">main LLVM
54 web site</a>. If you have questions or comments, the <a
55 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's
56 Mailing List</a> is a good place to send them.</p>
58 <p>Note that if you are reading this file from a Subversion checkout or the
59 main LLVM web page, this document applies to the <i>next</i> release, not the
60 current one. To see the release notes for a specific release, please see the
61 <a href="http://llvm.org/releases/">releases page</a>.</p>
68 include/llvm/Analysis/LiveValues.h => Dan
69 lib/Transforms/IPO/MergeFunctions.cpp => consider for 2.8.
70 llvm/Analysis/PointerTracking.h => Edwin wants this, consider for 2.8.
75 <!-- Features that need text if they're finished for 2.9:
78 llvm.dbg.value: variable debug info for optimized code
79 loop dependence analysis
81 CorrelatedValuePropagation
84 <!-- Announcement, lldb, libc++ -->
86 <!-- *********************************************************************** -->
87 <div class="doc_section">
88 <a name="subproj">Sub-project Status Update</a>
90 <!-- *********************************************************************** -->
92 <div class="doc_text">
94 The LLVM 2.8 distribution currently consists of code from the core LLVM
95 repository (which roughly includes the LLVM optimizers, code generators
96 and supporting tools), the Clang repository and the llvm-gcc repository. In
97 addition to this code, the LLVM Project includes other sub-projects that are in
98 development. Here we include updates on these subprojects.
104 <!--=========================================================================-->
105 <div class="doc_subsection">
106 <a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
109 <div class="doc_text">
111 <p><a href="http://clang.llvm.org/">Clang</a> is an LLVM front end for the C,
112 C++, and Objective-C languages. Clang aims to provide a better user experience
113 through expressive diagnostics, a high level of conformance to language
114 standards, fast compilation, and low memory use. Like LLVM, Clang provides a
115 modular, library-based architecture that makes it suitable for creating or
116 integrating with other development tools. Clang is considered a
117 production-quality compiler for C, Objective-C, C++ and Objective-C++ on x86
118 (32- and 64-bit), and for darwin-arm targets.</p>
120 <p>In the LLVM 2.8 time-frame, the Clang team has made many improvements:</p>
123 <li>Surely these guys have done something</li>
127 <!--=========================================================================-->
128 <div class="doc_subsection">
129 <a name="clangsa">Clang Static Analyzer</a>
132 <div class="doc_text">
134 <p>The <a href="http://clang-analyzer.llvm.org/">Clang Static Analyzer</a>
135 project is an effort to use static source code analysis techniques to
136 automatically find bugs in C and Objective-C programs (and hopefully <a
137 href="http://clang-analyzer.llvm.org/dev_cxx.html">C++ in the
138 future</a>!). The tool is very good at finding bugs that occur on specific
139 paths through code, such as on error conditions.</p>
141 <p>In the LLVM 2.8 time-frame,
146 <!--=========================================================================-->
147 <div class="doc_subsection">
148 <a name="vmkit">VMKit: JVM/CLI Virtual Machine Implementation</a>
151 <div class="doc_text">
153 The <a href="http://vmkit.llvm.org/">VMKit project</a> is an implementation of
154 a JVM and a CLI Virtual Machine (Microsoft .NET is an
155 implementation of the CLI) using LLVM for static and just-in-time
158 <p>With the release of LLVM 2.8, ...</p>
163 <!--=========================================================================-->
164 <div class="doc_subsection">
165 <a name="compiler-rt">compiler-rt: Compiler Runtime Library</a>
168 <div class="doc_text">
170 The new LLVM <a href="http://compiler-rt.llvm.org/">compiler-rt project</a>
171 is a simple library that provides an implementation of the low-level
172 target-specific hooks required by code generation and other runtime components.
173 For example, when compiling for a 32-bit target, converting a double to a 64-bit
174 unsigned integer is compiled into a runtime call to the "__fixunsdfdi"
175 function. The compiler-rt library provides highly optimized implementations of
176 this and other low-level routines (some are 3x faster than the equivalent
177 libgcc routines).</p>
180 All of the code in the compiler-rt project is available under the standard LLVM
181 License, a "BSD-style" license. New in LLVM 2.8:
188 <!--=========================================================================-->
189 <div class="doc_subsection">
190 <a name="dragonegg">DragonEgg: llvm-gcc ported to gcc-4.5</a>
193 <div class="doc_text">
195 <a href="http://dragonegg.llvm.org/">DragonEgg</a> is a port of llvm-gcc to
196 gcc-4.5. Unlike llvm-gcc, which makes many intrusive changes to the underlying
197 gcc-4.2 code, dragonegg in theory does not require any gcc-4.5 modifications
198 whatsoever (currently one small patch is needed). This is thanks to the new
199 <a href="http://gcc.gnu.org/wiki/plugins">gcc plugin architecture</a>, which
200 makes it possible to modify the behaviour of gcc at runtime by loading a plugin,
201 which is nothing more than a dynamic library which conforms to the gcc plugin
202 interface. DragonEgg is a gcc plugin that causes the LLVM optimizers to be run
203 instead of the gcc optimizers, and the LLVM code generators instead of the gcc
204 code generators, just like llvm-gcc. To use it, you add
205 "-fplugin=path/dragonegg.so" to the gcc-4.5 command line, and gcc-4.5 magically
206 becomes llvm-gcc-4.5!
210 DragonEgg is still a work in progress. Currently C works very well, while C++,
211 Ada and Fortran work fairly well. All other languages either don't work at all,
212 or only work poorly. For the moment only the x86-32 and x86-64 targets are
213 supported, and only on linux and darwin (darwin needs an additional gcc patch).
223 <!--=========================================================================-->
224 <div class="doc_subsection">
225 <a name="mc">llvm-mc: Machine Code Toolkit</a>
228 <div class="doc_text">
230 The LLVM Machine Code (aka MC) sub-project of LLVM was created to solve a number
231 of problems in the realm of assembly, disassembly, object file format handling,
232 and a number of other related areas that CPU instruction-set level tools work
233 in. It is a sub-project of LLVM which provides it with a number of advantages
234 over other compilers that do not have tightly integrated assembly-level tools.
235 For a gentle introduction, please see the <a
236 href="http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html">Intro to the
237 LLVM MC Project Blog Post</a>.
240 <p>2.8 status here</p>
243 <!--=========================================================================-->
244 <div class="doc_subsection">
245 <a name="lldb">LLDB: Low Level Debugger</a>
248 <div class="doc_text">
250 <a href="http://lldb.llvm.org/">LLDB</a> is</p>
261 <!--=========================================================================-->
262 <div class="doc_subsection">
263 <a name="libc++">libc++: C++ Standard Library</a>
266 <div class="doc_text">
268 <a href="http://libc++.llvm.org/">libc++</a> is</p>
280 <!-- *********************************************************************** -->
281 <div class="doc_section">
282 <a name="externalproj">External Open Source Projects Using LLVM 2.8</a>
284 <!-- *********************************************************************** -->
286 <div class="doc_text">
288 <p>An exciting aspect of LLVM is that it is used as an enabling technology for
289 a lot of other language and tools projects. This section lists some of the
290 projects that have already been updated to work with LLVM 2.8.</p>
294 <!-- *********************************************************************** -->
295 <div class="doc_section">
296 <a name="whatsnew">What's New in LLVM 2.8?</a>
298 <!-- *********************************************************************** -->
300 <div class="doc_text">
302 <p>This release includes a huge number of bug fixes, performance tweaks and
303 minor improvements. Some of the major improvements and new features are listed
309 <!--=========================================================================-->
310 <div class="doc_subsection">
311 <a name="orgchanges">LLVM Community Changes</a>
314 <div class="doc_text">
316 <p>In addition to changes to the code, between LLVM 2.7 and 2.8, a number of
317 organization changes have happened:
321 <li>libc++ and lldb are new</li>
325 <!--=========================================================================-->
326 <div class="doc_subsection">
327 <a name="majorfeatures">Major New Features</a>
330 <div class="doc_text">
332 <p>LLVM 2.8 includes several major new capabilities:</p>
335 <li>atomic lowering pass.</li>
336 <li>RegionInfo pass: opt -regions analyze" or "opt -view-regions".
337 <!-- Tobias Grosser --></li>
338 <li>ARMGlobalMerge: <!-- Anton --> </li>
344 <!--=========================================================================-->
345 <div class="doc_subsection">
346 <a name="coreimprovements">LLVM IR and Core Improvements</a>
349 <div class="doc_text">
350 <p>LLVM IR has several new features for better support of new targets and that
351 expose new optimization opportunities:</p>
355 <li>LLVM 2.8 changes the internal order of operands in <a
356 href="http://llvm.org/doxygen/classllvm_1_1InvokeInst.html"><tt>InvokeInst</tt></a>
357 and <a href="http://llvm.org/doxygen/classllvm_1_1CallInst.html"><tt>CallInst</tt></a>.
358 To be portable across releases, resort to <tt>CallSite</tt> and the
359 high-level accessors, such as <tt>getCalledValue</tt> and <tt>setUnwindDest</tt>.
362 You can no longer pass use_iterators directly to cast<> (and similar), because
363 these routines tend to perform costly dereference operations more than once. You
364 have to dereference the iterators yourself and pass them in.
367 llvm.memcpy.*, llvm.memset.*, llvm.memmove.* (and possibly other?) intrinsics
368 take an extra parameter now (i1 isVolatile), totaling 5 parameters.
369 If you were creating these intrinsic calls and prototypes yourself (as opposed
370 to using Intrinsic::getDeclaration), you can use UpgradeIntrinsicFunction/UpgradeIntrinsicCall
371 to be portable accross releases.
372 Note that you cannot use Intrinsic::getDeclaration() in a backwards compatible
373 way (needs 2/3 types now, in 2.7 it needed just 1).
376 SetCurrentDebugLocation takes a DebugLoc now instead of a MDNode.
377 Change your code to use
378 SetCurrentDebugLocation(DebugLoc::getFromDILocation(...)).
381 VISIBILITY_HIDDEN is gone.
384 The <tt>RegisterPass</tt> and <tt>RegisterAnalysisGroup</tt> templates are
385 considered deprecated, but continue to function in LLVM 2.8. Clients are
386 strongly advised to use the upcoming <tt>INITIALIZE_PASS()</tt> and
387 <tt>INITIALIZE_AG_PASS()</tt> macros instead.
389 SMDiagnostic takes different parameters now. //FIXME: how to upgrade?
392 The constructor for the Triple class no longer tries to understand odd triple
393 specifications. Frontends should ensure that they only pass valid triples to
394 LLVM. The Triple::normalize utility method has been added to help front-ends
395 deal with funky triples.
397 Some APIs got renamed:
399 <li>llvm_report_error -> report_fatal_error</li>
400 <li>llvm_install_error_handler -> install_fatal_error_handler</li>
401 <li>llvm::DwarfExceptionHandling -> llvm::JITExceptionHandling</li>
408 <!--=========================================================================-->
409 <div class="doc_subsection">
410 <a name="optimizer">Optimizer Improvements</a>
413 <div class="doc_text">
415 <p>In addition to a large array of minor performance tweaks and bug fixes, this
416 release includes a few major enhancements and additions to the optimizers:</p>
427 <!--=========================================================================-->
428 <div class="doc_subsection">
429 <a name="executionengine">Interpreter and JIT Improvements</a>
432 <div class="doc_text">
441 <!--=========================================================================-->
442 <div class="doc_subsection">
443 <a name="codegen">Target Independent Code Generator Improvements</a>
446 <div class="doc_text">
448 <p>We have put a significant amount of work into the code generator
449 infrastructure, which allows us to implement more aggressive algorithms and make
453 <li>MachO writer works.</li>
457 <!--=========================================================================-->
458 <div class="doc_subsection">
459 <a name="x86">X86-32 and X86-64 Target Improvements</a>
462 <div class="doc_text">
463 <p>New features of the X86 target include:
467 <li>The X86 backend now supports holding X87 floating point stack values
468 in registers across basic blocks, dramatically improving performance of code
469 that uses long double, and when targetting CPUs that don't support SSE.</li>
475 <!--=========================================================================-->
476 <div class="doc_subsection">
477 <a name="ARM">ARM Target Improvements</a>
480 <div class="doc_text">
481 <p>New features of the ARM target include:
487 All of the NEON load and store intrinsics (llvm.arm.neon.vld* and
488 llvm.arm.neon.vst*) take an extra parameter to specify the alignment in bytes
489 of the memory being accessed.
492 The llvm.arm.neon.vaba intrinsic (vector absolute difference and
493 accumulate) has been removed. This operation is now represented using
494 the llvm.arm.neon.vabd intrinsic (vector absolute difference) followed by a
498 The llvm.arm.neon.vabdl and llvm.arm.neon.vabal intrinsics (lengthening
499 vector absolute difference with and without accumlation) have been removed.
500 They are represented using the llvm.arm.neon.vabd intrinsic (vector absolute
501 difference) followed by a vector zero-extend operation, and for vabal,
505 The llvm.arm.neon.vmovn intrinsic has been removed. Calls of this intrinsic
506 are now replaced by vector truncate operations.
509 The llvm.arm.neon.vmovls and llvm.arm.neon.vmovlu intrinsics have been
510 removed. They are now represented as vector sign-extend (vmovls) and
511 zero-extend (vmovlu) operations.
514 The llvm.arm.neon.vaddl*, llvm.arm.neon.vaddw*, llvm.arm.neon.vsubl*, and
515 llvm.arm.neon.vsubw* intrinsics (lengthening vector add and subtract) have
516 been removed. They are replaced by vector add and vector subtract operations
517 where one (vaddw, vsubw) or both (vaddl, vsubl) of the operands are either
518 sign-extended or zero-extended.
521 The llvm.arm.neon.vmulls, llvm.arm.neon.vmullu, llvm.arm.neon.vmlal*, and
522 llvm.arm.neon.vmlsl* intrinsics (lengthening vector multiply with and without
523 accumulation and subtraction) have been removed. These operations are now
524 represented as vector multiplications where the operands are either
525 sign-extended or zero-extended, followed by a vector add for vmlal or a
526 vector subtract for vmlsl. Note that the polynomial vector multiply
527 intrinsic, llvm.arm.neon.vmullp, remains unchanged.
533 <!--=========================================================================-->
534 <div class="doc_subsection">
535 <a name="newapis">New Useful APIs</a>
538 <div class="doc_text">
540 <p>This release includes a number of new APIs that are used internally, which
541 may also be useful for external clients.
551 <!--=========================================================================-->
552 <div class="doc_subsection">
553 <a name="otherimprovements">Other Improvements and New Features</a>
556 <div class="doc_text">
557 <p>Other miscellaneous features include:</p>
566 <!--=========================================================================-->
567 <div class="doc_subsection">
568 <a name="changes">Major Changes and Removed Features</a>
571 <div class="doc_text">
573 <p>If you're already an LLVM user or developer with out-of-tree changes based
574 on LLVM 2.7, this section lists some "gotchas" that you may run into upgrading
575 from the previous release.</p>
578 <li>.ll file doesn't produce #uses comments anymore, to get them, run a .bc file
579 through "llvm-dis --show-annotations".</li>
580 <li>MSIL Backend removed.</li>
581 <li>ABCD and SSI passes removed.</li>
582 <li>'Union' LLVM IR feature removed.</li>
585 <p>In addition, many APIs have changed in this release. Some of the major LLVM
594 <!-- *********************************************************************** -->
595 <div class="doc_section">
596 <a name="knownproblems">Known Problems</a>
598 <!-- *********************************************************************** -->
600 <div class="doc_text">
602 <p>This section contains significant known problems with the LLVM system,
603 listed by component. If you run into a problem, please check the <a
604 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
605 there isn't already one.</p>
609 <!-- ======================================================================= -->
610 <div class="doc_subsection">
611 <a name="experimental">Experimental features included with this release</a>
614 <div class="doc_text">
616 <p>The following components of this LLVM release are either untested, known to
617 be broken or unreliable, or are in early development. These components should
618 not be relied on, and bugs should not be filed against them, but they may be
619 useful to some people. In particular, if you would like to work on one of these
620 components, please contact us on the <a
621 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
624 <li>The Alpha, SPU, MIPS, PIC16, Blackfin, MSP430, SystemZ and MicroBlaze
625 backends are experimental.</li>
626 <li><tt>llc</tt> "<tt>-filetype=asm</tt>" (the default) is the only
627 supported value for this option. XXX Update me</li>
632 <!-- ======================================================================= -->
633 <div class="doc_subsection">
634 <a name="x86-be">Known problems with the X86 back-end</a>
637 <div class="doc_text">
640 <li>The X86 backend does not yet support
641 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
642 floating point stack</a>. It supports the 'f' and 't' constraints, but not
644 <li>Win64 code generation wasn't widely tested. Everything should work, but we
645 expect small issues to happen. Also, llvm-gcc cannot build the mingw64
646 runtime currently due to lack of support for the 'u' inline assembly
647 constraint and for X87 floating point inline assembly.</li>
648 <li>The X86-64 backend does not yet support the LLVM IR instruction
649 <tt>va_arg</tt>. Currently, front-ends support variadic
650 argument constructs on X86-64 by lowering them manually.</li>
655 <!-- ======================================================================= -->
656 <div class="doc_subsection">
657 <a name="ppc-be">Known problems with the PowerPC back-end</a>
660 <div class="doc_text">
663 <li>The Linux PPC32/ABI support needs testing for the interpreter and static
664 compilation, and lacks support for debug information.</li>
669 <!-- ======================================================================= -->
670 <div class="doc_subsection">
671 <a name="arm-be">Known problems with the ARM back-end</a>
674 <div class="doc_text">
677 <li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
678 processors, thumb programs can crash or produce wrong
679 results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
680 <li>Compilation for ARM Linux OABI (old ABI) is supported but not fully tested.
686 <!-- ======================================================================= -->
687 <div class="doc_subsection">
688 <a name="sparc-be">Known problems with the SPARC back-end</a>
691 <div class="doc_text">
694 <li>The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not
695 support the 64-bit SPARC ABI (-m64).</li>
700 <!-- ======================================================================= -->
701 <div class="doc_subsection">
702 <a name="mips-be">Known problems with the MIPS back-end</a>
705 <div class="doc_text">
708 <li>64-bit MIPS targets are not supported yet.</li>
713 <!-- ======================================================================= -->
714 <div class="doc_subsection">
715 <a name="alpha-be">Known problems with the Alpha back-end</a>
718 <div class="doc_text">
722 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
723 appropriate nops inserted to ensure restartability.</li>
728 <!-- ======================================================================= -->
729 <div class="doc_subsection">
730 <a name="c-be">Known problems with the C back-end</a>
733 <div class="doc_text">
735 <p>The C backend has numerous problems and is not being actively maintained.
736 Depending on it for anything serious is not advised.</p>
739 <li><a href="http://llvm.org/PR802">The C backend has only basic support for
740 inline assembly code</a>.</li>
741 <li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
742 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
743 C++ code compiled with <tt>llc</tt> or native compilers.</li>
744 <li>The C backend does not support all exception handling constructs.</li>
745 <li>The C backend does not support arbitrary precision integers.</li>
751 <!-- ======================================================================= -->
752 <div class="doc_subsection">
753 <a name="llvm-gcc">Known problems with the llvm-gcc front-end</a>
756 <div class="doc_text">
758 <p>llvm-gcc is generally very stable for the C family of languages. The only
759 major language feature of GCC not supported by llvm-gcc is the
760 <tt>__builtin_apply</tt> family of builtins. However, some extensions
761 are only supported on some targets. For example, trampolines are only
762 supported on some targets (these are used when you take the address of a
763 nested function).</p>
765 <p>Fortran support generally works, but there are still several unresolved bugs
766 in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the
767 tools/gfortran component for details. Note that llvm-gcc is missing major
768 Fortran performance work in the frontend and library that went into GCC after
769 4.2. If you are interested in Fortran, we recommend that you consider using
770 <a href="#dragonegg">dragonegg</a> instead.</p>
772 <p>The llvm-gcc 4.2 Ada compiler has basic functionality. However, this is not a
773 mature technology, and problems should be expected. For example:</p>
775 <li>The Ada front-end currently only builds on X86-32. This is mainly due
776 to lack of trampoline support (pointers to nested functions) on other platforms.
777 However, it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
778 which does support trampolines.</li>
779 <li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
780 This is due to lack of LLVM support for <tt>setjmp</tt>/<tt>longjmp</tt> style
781 exception handling, which is used internally by the compiler.
782 Workaround: configure with <tt>--disable-bootstrap</tt>.</li>
783 <li>The c380004, <a href="http://llvm.org/PR2010">c393010</a>
784 and <a href="http://llvm.org/PR2421">cxg2021</a> ACATS tests fail
785 (c380004 also fails with gcc-4.2 mainline).
786 If the compiler is built with checks disabled then <a href="http://llvm.org/PR2010">c393010</a>
787 causes the compiler to go into an infinite loop, using up all system memory.</li>
788 <li>Some GCC specific Ada tests continue to crash the compiler.</li>
789 <li>The <tt>-E</tt> binder option (exception backtraces)
790 <a href="http://llvm.org/PR1982">does not work</a> and will result in programs
791 crashing if an exception is raised. Workaround: do not use <tt>-E</tt>.</li>
792 <li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
793 or finish at a non-byte offset</a> in a record. Workaround: do not pack records
794 or use representation clauses that result in a field of a non-discrete type
795 starting or finishing in the middle of a byte.</li>
796 <li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
797 'main' as generated by the Ada binder to be invalid</a>.
798 Workaround: hand edit the file to use pointers for <tt>argv</tt> and
799 <tt>envp</tt> rather than integers.</li>
800 <li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
805 <!-- *********************************************************************** -->
806 <div class="doc_section">
807 <a name="additionalinfo">Additional Information</a>
809 <!-- *********************************************************************** -->
811 <div class="doc_text">
813 <p>A wide variety of additional information is available on the <a
814 href="http://llvm.org">LLVM web page</a>, in particular in the <a
815 href="http://llvm.org/docs/">documentation</a> section. The web page also
816 contains versions of the API documentation which is up-to-date with the
817 Subversion version of the source code.
818 You can access versions of these documents specific to this release by going
819 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
821 <p>If you have any questions or comments about LLVM, please feel free to contact
822 us via the <a href="http://llvm.org/docs/#maillist"> mailing
827 <!-- *********************************************************************** -->
831 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
832 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
833 <a href="http://validator.w3.org/check/referer"><img
834 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
836 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
837 Last modified: $Date$