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="#portability">Portability and Supported Platforms</a></li>
23 <li><a href="#knownproblems">Known Problems</a></li>
24 <li><a href="#additionalinfo">Additional Information</a></li>
27 <div class="doc_author">
28 <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>
37 <!-- *********************************************************************** -->
38 <div class="doc_section">
39 <a name="intro">Introduction</a>
41 <!-- *********************************************************************** -->
43 <div class="doc_text">
45 <p>This document contains the release notes for the LLVM Compiler
46 Infrastructure, release 2.8. Here we describe the status of LLVM, including
47 major improvements from the previous release and significant known problems.
48 All LLVM releases may be downloaded from the <a
49 href="http://llvm.org/releases/">LLVM releases web site</a>.</p>
51 <p>For more information about LLVM, including information about the latest
52 release, please check out the <a href="http://llvm.org/">main LLVM
53 web site</a>. If you have questions or comments, the <a
54 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM Developer's
55 Mailing List</a> is a good place to send them.</p>
57 <p>Note that if you are reading this file from a Subversion checkout or the
58 main LLVM web page, this document applies to the <i>next</i> release, not the
59 current one. To see the release notes for a specific release, please see the
60 <a href="http://llvm.org/releases/">releases page</a>.</p>
67 include/llvm/Analysis/LiveValues.h => Dan
68 lib/Transforms/IPO/MergeFunctions.cpp => consider for 2.8.
69 llvm/Analysis/PointerTracking.h => Edwin wants this, consider for 2.8.
74 <!-- Features that need text if they're finished for 2.8:
77 llvm.dbg.value: variable debug info for optimized code
78 loop dependence analysis
82 <!-- for announcement email:
84 Many new papers added to /pubs/
87 <!-- *********************************************************************** -->
88 <div class="doc_section">
89 <a name="subproj">Sub-project Status Update</a>
91 <!-- *********************************************************************** -->
93 <div class="doc_text">
95 The LLVM 2.8 distribution currently consists of code from the core LLVM
96 repository (which roughly includes the LLVM optimizers, code generators
97 and supporting tools), the Clang repository and the llvm-gcc repository. In
98 addition to this code, the LLVM Project includes other sub-projects that are in
99 development. Here we include updates on these subprojects.
105 <!--=========================================================================-->
106 <div class="doc_subsection">
107 <a name="clang">Clang: C/C++/Objective-C Frontend Toolkit</a>
110 <div class="doc_text">
112 <p><a href="http://clang.llvm.org/">Clang</a> is an LLVM front end for the C,
113 C++, and Objective-C languages. Clang aims to provide a better user experience
114 through expressive diagnostics, a high level of conformance to language
115 standards, fast compilation, and low memory use. Like LLVM, Clang provides a
116 modular, library-based architecture that makes it suitable for creating or
117 integrating with other development tools. Clang is considered a
118 production-quality compiler for C and Objective-C on x86 (32- and 64-bit).</p>
120 <p>In the LLVM 2.8 time-frame, the Clang team has made many improvements:</p>
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>
244 <!-- *********************************************************************** -->
245 <div class="doc_section">
246 <a name="externalproj">External Open Source Projects Using LLVM 2.8</a>
248 <!-- *********************************************************************** -->
250 <div class="doc_text">
252 <p>An exciting aspect of LLVM is that it is used as an enabling technology for
253 a lot of other language and tools projects. This section lists some of the
254 projects that have already been updated to work with LLVM 2.8.</p>
258 <!-- *********************************************************************** -->
259 <div class="doc_section">
260 <a name="whatsnew">What's New in LLVM 2.8?</a>
262 <!-- *********************************************************************** -->
264 <div class="doc_text">
266 <p>This release includes a huge number of bug fixes, performance tweaks and
267 minor improvements. Some of the major improvements and new features are listed
273 <!--=========================================================================-->
274 <div class="doc_subsection">
275 <a name="orgchanges">LLVM Community Changes</a>
278 <div class="doc_text">
280 <p>In addition to changes to the code, between LLVM 2.7 and 2.8, a number of
281 organization changes have happened:
288 <!--=========================================================================-->
289 <div class="doc_subsection">
290 <a name="majorfeatures">Major New Features</a>
293 <div class="doc_text">
295 <p>LLVM 2.8 includes several major new capabilities:</p>
303 <!--=========================================================================-->
304 <div class="doc_subsection">
305 <a name="coreimprovements">LLVM IR and Core Improvements</a>
308 <div class="doc_text">
309 <p>LLVM IR has several new features for better support of new targets and that
310 expose new optimization opportunities:</p>
314 <li>LLVM 2.8 changes the internal order of operands in <a
315 href="http://llvm.org/doxygen/classllvm_1_1InvokeInst.html"><tt>InvokeInst</tt></a>
316 and <a href="http://llvm.org/doxygen/classllvm_1_1CallInst.html"><tt>CallInst</tt></a>.
317 To be portable across releases, resort to <tt>CallSite</tt> and the
318 high-level accessors, such as <tt>getCalledValue</tt> and <tt>setUnwindDest</tt>.
321 You can no longer pass use_iterators directly to cast<> (and similar), because
322 these routines tend to perform costly dereference operations more than once. You
323 have to dereference the iterators yourself and pass them in.
326 llvm.memcpy.*, llvm.memset.*, llvm.memmove.* (and possibly other?) intrinsics
327 take an extra parameter now (i1 isVolatile), totaling 5 parameters.
328 If you were creating these intrinsic calls and prototypes yourself (as opposed
329 to using Intrinsic::getDeclaration), you can use UpgradeIntrinsicFunction/UpgradeIntrinsicCall
330 to be portable accross releases.
331 Note that you cannot use Intrinsic::getDeclaration() in a backwards compatible
332 way (needs 2/3 types now, in 2.7 it needed just 1).
335 SetCurrentDebugLocation takes a DebugLoc now instead of a MDNode.
336 Change your code to use
337 SetCurrentDebugLocation(DebugLoc::getFromDILocation(...)).
340 VISIBILITY_HIDDEN is gone.
343 The <tt>RegisterPass</tt> and <tt>RegisterAnalysisGroup</tt> templates are
344 considered deprecated, but continue to function in LLVM 2.8. Clients are
345 strongly advised to use the upcoming <tt>INITIALIZE_PASS()</tt> and
346 <tt>INITIALIZE_AG_PASS()</tt> macros instead.
348 SMDiagnostic takes different parameters now. //FIXME: how to upgrade?
351 The constructor for the Triple class no longer tries to understand odd triple
352 specifications. Frontends should ensure that they only pass valid triples to
353 LLVM. The Triple::normalize utility method has been added to help front-ends
354 deal with funky triples.
356 Some APIs got renamed:
358 <li>llvm_report_error -> report_fatal_error</li>
359 <li>llvm_install_error_handler -> install_fatal_error_handler</li>
360 <li>llvm::DwarfExceptionHandling -> llvm::JITExceptionHandling</li>
367 <!--=========================================================================-->
368 <div class="doc_subsection">
369 <a name="optimizer">Optimizer Improvements</a>
372 <div class="doc_text">
374 <p>In addition to a large array of minor performance tweaks and bug fixes, this
375 release includes a few major enhancements and additions to the optimizers:</p>
386 <!--=========================================================================-->
387 <div class="doc_subsection">
388 <a name="executionengine">Interpreter and JIT Improvements</a>
391 <div class="doc_text">
400 <!--=========================================================================-->
401 <div class="doc_subsection">
402 <a name="codegen">Target Independent Code Generator Improvements</a>
405 <div class="doc_text">
407 <p>We have put a significant amount of work into the code generator
408 infrastructure, which allows us to implement more aggressive algorithms and make
412 <li>MachO writer works.</li>
416 <!--=========================================================================-->
417 <div class="doc_subsection">
418 <a name="x86">X86-32 and X86-64 Target Improvements</a>
421 <div class="doc_text">
422 <p>New features of the X86 target include:
426 <li>The X86 backend now supports holding X87 floating point stack values
427 in registers across basic blocks, dramatically improving performance of code
428 that uses long double, and when targetting CPUs that don't support SSE.</li>
434 <!--=========================================================================-->
435 <div class="doc_subsection">
436 <a name="ARM">ARM Target Improvements</a>
439 <div class="doc_text">
440 <p>New features of the ARM target include:
452 <!--=========================================================================-->
453 <div class="doc_subsection">
454 <a name="newapis">New Useful APIs</a>
457 <div class="doc_text">
459 <p>This release includes a number of new APIs that are used internally, which
460 may also be useful for external clients.
470 <!--=========================================================================-->
471 <div class="doc_subsection">
472 <a name="otherimprovements">Other Improvements and New Features</a>
475 <div class="doc_text">
476 <p>Other miscellaneous features include:</p>
485 <!--=========================================================================-->
486 <div class="doc_subsection">
487 <a name="changes">Major Changes and Removed Features</a>
490 <div class="doc_text">
492 <p>If you're already an LLVM user or developer with out-of-tree changes based
493 on LLVM 2.7, this section lists some "gotchas" that you may run into upgrading
494 from the previous release.</p>
497 <li>MSIL Backend removed.</li>
498 <li>ABCD and SSI passes removed.</li>
499 <li>'Union' LLVM IR feature removed.</li>
502 <p>In addition, many APIs have changed in this release. Some of the major LLVM
512 <!-- *********************************************************************** -->
513 <div class="doc_section">
514 <a name="portability">Portability and Supported Platforms</a>
516 <!-- *********************************************************************** -->
518 <div class="doc_text">
520 <p>LLVM is known to work on the following platforms:</p>
523 <li>Intel and AMD machines (IA32, X86-64, AMD64, EMT-64) running Red Hat
524 Linux, Fedora Core, FreeBSD and AuroraUX (and probably other unix-like
526 <li>PowerPC and X86-based Mac OS X systems, running 10.4 and above in 32-bit
527 and 64-bit modes.</li>
528 <li>Intel and AMD machines running on Win32 using MinGW libraries (native).</li>
529 <li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
530 support is available for native builds with Visual C++).</li>
531 <li>Sun x86 and AMD64 machines running Solaris 10, OpenSolaris 0906.</li>
532 <li>Alpha-based machines running Debian GNU/Linux.</li>
535 <p>The core LLVM infrastructure uses GNU autoconf to adapt itself
536 to the machine and operating system on which it is built. However, minor
537 porting may be required to get LLVM to work on new platforms. We welcome your
538 portability patches and reports of successful builds or error messages.</p>
542 <!-- *********************************************************************** -->
543 <div class="doc_section">
544 <a name="knownproblems">Known Problems</a>
546 <!-- *********************************************************************** -->
548 <div class="doc_text">
550 <p>This section contains significant known problems with the LLVM system,
551 listed by component. If you run into a problem, please check the <a
552 href="http://llvm.org/bugs/">LLVM bug database</a> and submit a bug if
553 there isn't already one.</p>
556 <li>LLVM will not correctly compile on Solaris and/or OpenSolaris
557 using the stock GCC 3.x.x series 'out the box',
558 See: <a href="GettingStarted.html#brokengcc">Broken versions of GCC and other tools</a>.
559 However, A <a href="http://pkg.auroraux.org/GCC">Modern GCC Build</a>
560 for x86/x86-64 has been made available from the third party AuroraUX Project
561 that has been meticulously tested for bootstrapping LLVM & Clang.</li>
562 <li>There have been reports of Solaris and/or OpenSolaris build failures due
563 to an incompatibility in the nm program as well. The nm from binutils does seem
569 <!-- ======================================================================= -->
570 <div class="doc_subsection">
571 <a name="experimental">Experimental features included with this release</a>
574 <div class="doc_text">
576 <p>The following components of this LLVM release are either untested, known to
577 be broken or unreliable, or are in early development. These components should
578 not be relied on, and bugs should not be filed against them, but they may be
579 useful to some people. In particular, if you would like to work on one of these
580 components, please contact us on the <a
581 href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVMdev list</a>.</p>
584 <li>The Alpha, SPU, MIPS, PIC16, Blackfin, MSP430, SystemZ and MicroBlaze
585 backends are experimental.</li>
586 <li><tt>llc</tt> "<tt>-filetype=asm</tt>" (the default) is the only
587 supported value for this option. XXX Update me</li>
592 <!-- ======================================================================= -->
593 <div class="doc_subsection">
594 <a name="x86-be">Known problems with the X86 back-end</a>
597 <div class="doc_text">
600 <li>The X86 backend does not yet support
601 all <a href="http://llvm.org/PR879">inline assembly that uses the X86
602 floating point stack</a>. It supports the 'f' and 't' constraints, but not
604 <li>Win64 code generation wasn't widely tested. Everything should work, but we
605 expect small issues to happen. Also, llvm-gcc cannot build the mingw64
606 runtime currently due to lack of support for the 'u' inline assembly
607 constraint and for X87 floating point inline assembly.</li>
608 <li>The X86-64 backend does not yet support the LLVM IR instruction
609 <tt>va_arg</tt>. Currently, front-ends support variadic
610 argument constructs on X86-64 by lowering them manually.</li>
615 <!-- ======================================================================= -->
616 <div class="doc_subsection">
617 <a name="ppc-be">Known problems with the PowerPC back-end</a>
620 <div class="doc_text">
623 <li>The Linux PPC32/ABI support needs testing for the interpreter and static
624 compilation, and lacks support for debug information.</li>
629 <!-- ======================================================================= -->
630 <div class="doc_subsection">
631 <a name="arm-be">Known problems with the ARM back-end</a>
634 <div class="doc_text">
637 <li>Thumb mode works only on ARMv6 or higher processors. On sub-ARMv6
638 processors, thumb programs can crash or produce wrong
639 results (<a href="http://llvm.org/PR1388">PR1388</a>).</li>
640 <li>Compilation for ARM Linux OABI (old ABI) is supported but not fully tested.
646 <!-- ======================================================================= -->
647 <div class="doc_subsection">
648 <a name="sparc-be">Known problems with the SPARC back-end</a>
651 <div class="doc_text">
654 <li>The SPARC backend only supports the 32-bit SPARC ABI (-m32); it does not
655 support the 64-bit SPARC ABI (-m64).</li>
660 <!-- ======================================================================= -->
661 <div class="doc_subsection">
662 <a name="mips-be">Known problems with the MIPS back-end</a>
665 <div class="doc_text">
668 <li>64-bit MIPS targets are not supported yet.</li>
673 <!-- ======================================================================= -->
674 <div class="doc_subsection">
675 <a name="alpha-be">Known problems with the Alpha back-end</a>
678 <div class="doc_text">
682 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
683 appropriate nops inserted to ensure restartability.</li>
688 <!-- ======================================================================= -->
689 <div class="doc_subsection">
690 <a name="c-be">Known problems with the C back-end</a>
693 <div class="doc_text">
696 <li><a href="http://llvm.org/PR802">The C backend has only basic support for
697 inline assembly code</a>.</li>
698 <li><a href="http://llvm.org/PR1658">The C backend violates the ABI of common
699 C++ programs</a>, preventing intermixing between C++ compiled by the CBE and
700 C++ code compiled with <tt>llc</tt> or native compilers.</li>
701 <li>The C backend does not support all exception handling constructs.</li>
702 <li>The C backend does not support arbitrary precision integers.</li>
708 <!-- ======================================================================= -->
709 <div class="doc_subsection">
710 <a name="c-fe">Known problems with the llvm-gcc C and C++ front-end</a>
713 <div class="doc_text">
715 <p>The only major language feature of GCC not supported by llvm-gcc is
716 the <tt>__builtin_apply</tt> family of builtins. However, some extensions
717 are only supported on some targets. For example, trampolines are only
718 supported on some targets (these are used when you take the address of a
719 nested function).</p>
723 <!-- ======================================================================= -->
724 <div class="doc_subsection">
725 <a name="fortran-fe">Known problems with the llvm-gcc Fortran front-end</a>
728 <div class="doc_text">
730 <li>Fortran support generally works, but there are still several unresolved bugs
731 in <a href="http://llvm.org/bugs/">Bugzilla</a>. Please see the
732 tools/gfortran component for details.</li>
736 <!-- ======================================================================= -->
737 <div class="doc_subsection">
738 <a name="ada-fe">Known problems with the llvm-gcc Ada front-end</a>
741 <div class="doc_text">
742 The llvm-gcc 4.2 Ada compiler works fairly well; however, this is not a mature
743 technology, and problems should be expected.
745 <li>The Ada front-end currently only builds on X86-32. This is mainly due
746 to lack of trampoline support (pointers to nested functions) on other platforms.
747 However, it <a href="http://llvm.org/PR2006">also fails to build on X86-64</a>
748 which does support trampolines.</li>
749 <li>The Ada front-end <a href="http://llvm.org/PR2007">fails to bootstrap</a>.
750 This is due to lack of LLVM support for <tt>setjmp</tt>/<tt>longjmp</tt> style
751 exception handling, which is used internally by the compiler.
752 Workaround: configure with <tt>--disable-bootstrap</tt>.</li>
753 <li>The c380004, <a href="http://llvm.org/PR2010">c393010</a>
754 and <a href="http://llvm.org/PR2421">cxg2021</a> ACATS tests fail
755 (c380004 also fails with gcc-4.2 mainline).
756 If the compiler is built with checks disabled then <a href="http://llvm.org/PR2010">c393010</a>
757 causes the compiler to go into an infinite loop, using up all system memory.</li>
758 <li>Some GCC specific Ada tests continue to crash the compiler.</li>
759 <li>The <tt>-E</tt> binder option (exception backtraces)
760 <a href="http://llvm.org/PR1982">does not work</a> and will result in programs
761 crashing if an exception is raised. Workaround: do not use <tt>-E</tt>.</li>
762 <li>Only discrete types <a href="http://llvm.org/PR1981">are allowed to start
763 or finish at a non-byte offset</a> in a record. Workaround: do not pack records
764 or use representation clauses that result in a field of a non-discrete type
765 starting or finishing in the middle of a byte.</li>
766 <li>The <tt>lli</tt> interpreter <a href="http://llvm.org/PR2009">considers
767 'main' as generated by the Ada binder to be invalid</a>.
768 Workaround: hand edit the file to use pointers for <tt>argv</tt> and
769 <tt>envp</tt> rather than integers.</li>
770 <li>The <tt>-fstack-check</tt> option <a href="http://llvm.org/PR2008">is
775 <!-- *********************************************************************** -->
776 <div class="doc_section">
777 <a name="additionalinfo">Additional Information</a>
779 <!-- *********************************************************************** -->
781 <div class="doc_text">
783 <p>A wide variety of additional information is available on the <a
784 href="http://llvm.org">LLVM web page</a>, in particular in the <a
785 href="http://llvm.org/docs/">documentation</a> section. The web page also
786 contains versions of the API documentation which is up-to-date with the
787 Subversion version of the source code.
788 You can access versions of these documents specific to this release by going
789 into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
791 <p>If you have any questions or comments about LLVM, please feel free to contact
792 us via the <a href="http://llvm.org/docs/#maillist"> mailing
797 <!-- *********************************************************************** -->
801 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
802 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
803 <a href="http://validator.w3.org/check/referer"><img
804 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
806 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
807 Last modified: $Date$