<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="llvm.css" type="text/css">
- <title>LLVM 1.4 Release Notes</title>
+ <title>LLVM 1.5 Release Notes</title>
</head>
<body>
-<div class="doc_title">LLVM 1.4 Release Notes</div>
+<div class="doc_title">LLVM 1.5 Release Notes</div>
<ol>
<li><a href="#intro">Introduction</a></li>
<li><a href="GettingStarted.html">Installation Instructions</a></li>
<li><a href="#portability">Portability and Supported Platforms</a></li>
<li><a href="#knownproblems">Known Problems</a>
- <ul>
- <li><a href="#experimental">Experimental features included in this
- release</a>
- <li><a href="#core">Known problems with the LLVM Core</a>
- <li><a href="#c-fe">Known problems with the C Front-end</a>
- <li><a href="#c++-fe">Known problems with the C++ Front-end</a>
- <li><a href="#x86-be">Known problems with the X86 Back-end</a>
- <li><a href="#sparcv9-be">Known problems with the SparcV9 Back-end</a>
- <li><a href="#ppc-be">Known problems with the PowerPC Back-end</a>
- <li><a href="#c-be">Known problems with the C back-end</a>
- </ul></li>
<li><a href="#additionalinfo">Additional Information</a></li>
</ol>
<div class="doc_author">
- <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM
team</a><p>
+ <p>Written by the <a href="http://llvm.cs.uiuc.edu">LLVM
Team</a><p>
</div>
<!-- *********************************************************************** -->
<div class="doc_text">
<p>This document contains the release notes for the LLVM compiler
-infrastructure, release 1.4. Here we describe the status of LLVM, including any
-known problems and bug fixes from the previous release. The most up-to-date
+infrastructure, release 1.5. Here we describe the status of LLVM, including any
+known problems and improvements from the previous release. The most up-to-date
version of this document can be found on the <a
-href="http://llvm.cs.uiuc.edu/releases/1.4/">LLVM 1.4 web site</a>. If you are
+href="http://llvm.cs.uiuc.edu/releases/1.5/">LLVM 1.5 web site</a>. If you are
not reading this on the LLVM web pages, you should probably go there because
this document may be updated after the release.</p>
-<p>For more information about LLVM, including information about potentially more
-current releases, please check out the <a href="http://llvm.cs.uiuc.edu">main
+<p>For more information about LLVM, including information about the latest
+release, please check out the <a href="http://llvm.cs.uiuc.edu">main LLVM
web site</a>. If you have questions or comments, the <a
href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM developer's mailing
list</a> is a good place to send them.</p>
-<p>Note that if you are reading this file from CVS, this document applies
-to the <i>next</i> release, not the current one. To see the release notes for
-the current or previous releases, see the <a
+<p>Note that if you are reading this file from CVS or the main LLVM web page,
+this document applies to the <i>next</i> release, not the current one. To see
+the
release notes for the current or previous releases, see the <a
href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
</div>
<div class="doc_text">
-<p>This is the fifth public release of the LLVM compiler infrastructure.</p>
+<p>This is the sixth public release of the LLVM compiler infrastructure.</p>
-<p> At this time, LLVM is known to correctly compile and run all C & C++
-SPEC CPU95 & 2000 benchmarks, the Olden benchmarks, and the Ptrdist
-benchmarks, and <b>many</b> other C and C++ programs.</p>
+<p> At this time, LLVM is known to correctly compile a broad range of C and
+C++ programs, including the SPEC CPU95 & 2000 suite. TODO. It also includes
+bug fixes for those problems found since the 1.4 release.</p>
</div>
<div class="doc_text">
<ol>
- <li>LLVM now includes a JIT for the PowerPC target.</li>
- <li>LLVM now optimizes global variables significantly more than it did
- before.
- </li>
- <li>LLVM now includes the new '<tt>undef</tt>' value and
- <a href="LangRef.html#i_unreachable"><tt>unreachable</tt></a> instruction,
- which give the optimizer more information about the behavior of the
- program.
- </li>
- <li>llvmgcc and llvmg++ now emit source line number information when '-g' is
- passed in. This information can be used with llvm-db or other tools and
- passes.
- </li>
- <li>The test/Programs hierarchy <a href="http://llvm.cs.uiuc.edu/PR257">has
- been moved out of the main LLVM tree</a> into a separate CVS repository and
- tarball. This shrinks the distribution size of LLVM itself significantly.
- </li>
- <li>Bytecode compression with bzip2 has been implemented. All bytecode files
- generated by LLVM will now be compressed by default. Compression can be
- disabled with the <tt>-disable-compression</tt> option to the tools that can
- generate bytecode files.
- </li>
- <li>A generic <a href="http://llvm.cs.uiuc.edu/PR353">compiler driver</a> and
- an associated <a href="CommandGuide/html/llvm-ld.html">generic linker</a> have
- been implemented. The compiler driver is generic because it can be configured
- to pre-process, translate, optimize, assemble, and link code from any source
- language. This aids compiler writers because all that is needed is a
- source-to-bytecode or source-to-assembly translator and a configuration file.
- The linker is generic because it allows dynamically loadable optimization
- modules to be executed for link-time optimization. Language specific
- link-time optimization modules can be created and executed automatically.
- </li>
- <li>The <a href="http://llvm.cs.uiuc.edu/PR263">dependent libraries</a>
- feature has been implemented. This allows front end compilers to indicate in
- the bytecode which libraries the bytecode needs to be linked with. Both the
- C/C++ front end and Stacker support generating the required libraries. The
- Linker now supports using this information to ensure required libaries are
- linked into the module. This minimizes the need to use the <tt>-l</tt> option
- when using <a href="CommandGuide/html/llvmc.html"><tt>llvmc</tt></a>
- </li>
- <li>The LLVM makefiles have been improved to build LLVM faster (2x) and
- includes new targets (like dist-check, uninstall). One important change is
- associated with <a href="http://llvm.cs.uiuc.edu/PR456">PR456</a>. The
- libraries and tools will now be built into <tt>$builddir/Debug/{bin,lib}</tt>
- instead of <tt>$builddir/tools/Debug</tt> and <tt>$builddir/lib/Debug</tt>.
- Similarly for <tt>Release</tt> and <tt>Profile</tt> builds.
- </li>
- <li>The LLVM source code is much more compatible with Microsoft Visual C++,
- including the JIT and runtime-code generation, though the entire system
- may not work with it.
- </li>
- <li>The target-to-JIT interfaces <a href="http://llvm.cs.uiuc.edu/PR283">are
- now much simpler</a> and more powerful.
- </li>
- <li>zlib and libpng are <a href="http://llvm.cs.uiuc.edu/PR417">no longer
- included in the main LLVM tarball</a>.</li>
- <li>The LLVM code generator now generates asm writers for the target from
- an abstract target description, instead of requiring them to be hand
- written.</li>
- <li>LLVM regression and feature tests can now be run with DejaGNU.</li>
- <li>llvmgcc and llvmg++ now emit source-level line number information, making
- it possible to map from LLVM code back to source. This is currently used
- by llvm-db.</li>
+ <li>LLVM now includes an <a href="http://llvm.cs.uiuc.edu/PR415">
+ Interprocedural Sparse Conditional Constant Propagation</a> pass, named
+ -ipsccp, which is run by default at link-time.</li>
+ <li>LLVM 1.5 is now about 15% faster than LLVM 1.4 and its core data structures
+ use about 30% less memory.</li>
+ <li>LLVM includes new experimental native code generators for SparcV8,
+ Alpha, and IA64.</li>
+ <li>Support for Microsoft Visual Studio is improved, and <a
+ href="GettingStartedVS.html">now documented</a>.</li>
</ol>
</div>
<div class="doc_text">
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR419">JIT interface should support
- arbitrary calls</a>
- </li>
- <li>The <tt>llvm-ar</tt> tool was previously incomplete and didn't properly
- support other ar(1) implementations. This has been corrected. <tt>llvm-ar</tt>
- now fully supports all archive editing functions, table of contents listing,
- extraction, and printing. It can also read BSD4.4/MacOSX and SVR4 style
- archives. See <a href="CommandGuide/html/llvm-ar.html">llvm-ar</a> for
- details.
- </li>
+ <li>LLVM can now create native shared libraries with '<tt>llvm-gcc ...
+ -shared -Wl,-native</tt>' (or with <tt>-Wl,-native-cbe</tt>).</li>
+ <li>LLVM now supports a new "<a href="LangRef.html#i_prefetch">llvm.prefetch
+ </a>" intrinsic, and llvm-gcc now supports __builtin_prefetch.
</ol>
</div>
<div class="doc_text">
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR426">[llvmg++] Tons of warnings
- are spewed when linking to libstdc++</a>
- </li>
- <li><a href="http://llvm.cs.uiuc.edu/PR352">include/{Support,Config} ->
- include/llvm/{Support,Config}</a>
- </li>
- <li>The names of the libraries generated by compiling LLVM source have been
- changed to ensure they do not conflict with other packages upon installation.
- Each LLVM library is now prefixed with LLVM and uses mixed clase. For example,
- the library <tt>libasmparser.a</tt> in 1.3 has become
- <tt>libLLVMAsmParser.a</tt> in release 1.4.
- </li>
- <li><a href="http://llvm.cs.uiuc.edu/PR459">[llvmg++] C++ frontend is expanding
- lots of unused inline functions</a></li>
-</ol>
-
-</div>
-
-<!--=========================================================================-->
-<div class="doc_subsubsection">
-In this release, the following build problems were fixed:
-</div>
-
-<div class="doc_text">
-<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR256">[autoconf] further standardizing
- autoconf usage</a>. Various improvements in the configure.ac script were
- made as well as the makefile system.
- </li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR448">Building LLVM in optimized mode
+ should no longer cause GCC to hit swap in the PowerPC backend.</a></li>
</ol>
</div>
<div class="doc_text">
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR362">Ugly code generated for
- std::min/std::max</a>
- </li>
+ <li></li>
</ol>
</div>
<div class="doc_text">
-<p>Bugs fixed in the LLVM Core:</p>
+<p>Bugs fixed in the LLVM Core:</p>
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR420">[licm] LICM invalidates alias
- analysis info and uses broken information</a> (optimizer crash)</li>
- <li><a href="http://llvm.cs.uiuc.edu/PR422">[asmwriter] Asmwriter is really
- slow for functions with lots of values</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR423">[anders-aa] Andersen's AA is
- completely broken in LLVM 1.3</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR430">[bcwriter] Empty compaction
- tables defined</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR227">[X86] llc output for functions
- w/certain names tickles GNU 'as' bugs</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR491">[dse] DSE deletes stores that
+ are partially overwritten by smaller stores</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR548">[instcombine] miscompilation of
+ setcc or setcc in one case</a></li>
</ol>
-<p>Bugs in the C/C++ front-end:</p>
-
+<p>Code Generator Bugs:</p>
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR445">[llvmg++] not enough templates are
- instantiated</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR450">[llvmg++] Extern const globals
- cannot be marked 'constant' if they have nontrivial ctors or dtors</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR461">[llvmgcc] Crash compiling unnamed
- bitfield which does not increase struct size</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR424">[llvmgcc] llvmgcc emits invalid
- constant exprs</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR421">[llvmg++] Crash in initializing
- array with constructors in hard EH situations</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR397">[llvm-gcc] Inline function
- redefinitions error due to 'asm' function rename</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an
- implicitly external function is re-declared as static</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR360">[llvmgcc] Structure field with
- non-constant offset crashes llvmgcc</a></li>
- <li><a href="http://llvm.cs.uiuc.edu/PR447">[llvmg++] Crash compiling
- friend with default argument</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR490">[cbackend] Logical constant
+ expressions (and/or/xor) not implemented</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR511">[cbackend] C backend does not
+ respect 'volatile'</a></li>
</ol>
-<p>Bugs fixed in the Sparc V9 back-end:</p>
-
+<p>Bugs in the C/C++ front-end:</p>
<ol>
- <li><a href="http://llvm.cs.uiuc.edu/PR428">[sparcv9] regalloc assertion
- failure with certain indirect calls</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR487">[llvmgcc] llvm-gcc incorrectly
+ rejects some constant initializers involving the addresses of array
+ elements</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR501">[llvm-g++] Crash compiling
+ anonymous union</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR509">[llvm-g++] Do not use dynamic
+ initialization where static init will do</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR510">[llvmgcc] Field offset
+ miscalculated for some structure fields following bit fields</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR513">[llvm-g++] Temporary lifetimes
+ incorrect for short circuit logical operations</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR517">[llvm-gcc] Crash compiling
+ bitfield <-> aggregate assignment</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR520">[llvm-g++] Error compiling
+ virtual function thunk with an unnamed argument</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR522">[llvm-gcc] Crash on certain
+ C99 complex number routines</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR529">[llvm-g++] Crash using placement
+ new on an array type</a></li>
</ol>
</div>
<div class="doc_text">
-<p>LLVM is known to work in the following platforms:</p>
+<p>LLVM is known to work on the following platforms:</p>
<ul>
<li>Intel and AMD machines running Red Hat Linux and FreeBSD (and probably
other unix-like systems).</li>
<li>Sun UltraSPARC workstations running Solaris 8.</li>
-<li>Intel and AMD machines running on Win32 with the Cygwin libraries.</li>
-<li>PowerPC-based Mac OS X boxes, running 10.2 and above.</li>
+<li>Intel and AMD machines running on Win32 with the Cygwin libraries (limited
+ support is available for native builds with Visual C++).</li>
+<li>PowerPC-based Mac OS X systems, running 10.2 and above.</li>
</ul>
<p>The core LLVM infrastructure uses
porting may be required to get LLVM to work on new platforms. We welcome your
portability patches and reports of successful builds or error messages.</p>
-<p>Note that the LLVM build system does not currently support directories with
-spaces on them when running on Win32/cygwin. We strongly recommend running
-LLVM and the C frontend out of a top-level directory without spaces (e.g.,
-<tt>/cygdrive/c/llvm</tt>). Also, make sure to install <b>all</b> of the
-cygwin packages. By default, many important tools are not installed that
-are needed by the LLVM build process or test suite (e.g., /bin/time). Finally,
-please make sure that there are no directories with spaces in them in your
-PATH environment variable.</p>
-
</div>
<!-- *********************************************************************** -->
components, please contact us on the llvmdev list.</p>
<ul>
-<li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
- -ipmodref, -cee, -branch-combine, -instloops, -paths</tt></li>
-<li>The <tt>-pre</tt> pass is incomplete (there are cases it doesn't handle that
- it should) and not thoroughly tested.</li>
-<li>The <tt>llvm-db</tt> tool is in a very early stage of development.</li>
-<li>The "iterative scan" register allocator (enabled with -regalloc=iterativescan)
- is not stable.</li>
+<li>The following passes are incomplete or buggy, and may be removed in future
+ releases: <tt>-cee, -branch-combine, -instloops, -paths, -pre</tt></li>
+<li>The <tt>llvm-db</tt> tool is in a very early stage of development, but can
+ be used to step through programs and inspect the stack.</li>
+<li>The "iterative scan" register allocator (enabled with
+ <tt>-regalloc=iterativescan</tt>) is not stable.</li>
+<li>The SparcV8, Alpha, and IA64 ports are experimental.</li>
</ul>
</div>
<div class="doc_text">
<ul>
- <li>In the JIT, <tt>dlsym</tt> on a symbol compiled by the JIT will not work.
- </li>
+ <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not
+ work.</li>
<li>The JIT does not use mutexes to protect its internal data structures. As
such, execution of a threaded program could cause these data structures to be
corrupted.
</li>
- <li>Linking in static archive files (.a files) is slow by default because
- there is no symbol table in the archive. To remedy this, run
- <a href="CommandGuide/html/llvm-ranlib.html"><tt>llvm-ranlib</tt></a> on the
- archive to add an LLVM symbol table.
- </li>
- <li>The gccld program <a href="http://llvm.cs.uiuc.edu/PR139">does not link
- objects/archives in the order specified on the command line.</a>
- </li>
<li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
mark values live across a setjmp as volatile</a>. This missing feature
only affects targets whose setjmp/longjmp libraries do not save and restore
the entire register file.</li>
- <li><a href="http://llvm.cs.uiuc.edu/PR427">[bytecode] Assertion on V1
- Bytecode Files</a>. This bug won't be fixed because V1 bytecode had its own
- problems, no one is using V1 bytecode any more, and the fix is non-trivial.
- </li>
</ul>
</div>
</pre></li>
<li>Initialization of global union variables can only be done <a
-href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=162">with the largest union
-member</a>.</li>
-
-<li><a href="http://llvm.cs.uiuc.edu/PR244">[llvm-gcc] Error when an implicitly
-external function is re-declared as static</a></li>
+href="http://llvm.cs.uiuc.edu/PR162">with the largest union member</a>.</li>
</ul>
</div>
<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>
<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>
<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>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread-Local.html#Thread-Local">Thread-Local</a>: Per-thread variables.</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Thread_002dLocal.html">Thread-Local</a>: Per-thread variables.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pragmas.html#Pragmas">Pragmas</a>: Pragmas accepted by GCC.</li>
</ol>
return.<br>
<b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
- <tt>constructor</tt>, <tt>destructor</tt>, <tt>unused</tt>,
+ <tt>noreturn</tt>, <tt>constructor</tt>, <tt>destructor</tt>,
+ <tt>unused</tt>,
<tt>deprecated</tt>, <tt>warn_unused_result</tt>, <tt>weak</tt><br>
- <b>Ignored:</b> <tt>noreturn</tt>, <tt>noinline</tt>,
+ <b>Ignored:</b> <tt>noinline</tt>,
<tt>always_inline</tt>, <tt>pure</tt>, <tt>const</tt>, <tt>nothrow</tt>,
<tt>malloc</tt>, <tt>no_instrument_function</tt>, <tt>cdecl</tt><br>
<tt>__builtin_types_compatible_p</tt>, <tt>__builtin_choose_expr</tt>,
<tt>__builtin_constant_p</tt>, and <tt>__builtin_expect</tt>
(currently ignored). We also support builtins for ISO C99 floating
- point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
+ point comparison macros (e.g., <tt>__builtin_islessequal</tt>), and
+ <tt>__builtin_prefetch</tt>.</li>
</ol>
<p>The following extensions <b>are</b> known to be supported:</p>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html#Mixed%20Declarations">Mixed Declarations</a>: Mixing declarations and code.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Prototypes.html#Function%20Prototypes">Function Prototypes</a>: Prototype declarations and old-style definitions.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/C---Comments.html#C++%20Comments">C++ Comments</a>: C++ comments are recognized.</li>
+ <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>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Dollar-Signs.html#Dollar%20Signs">Dollar Signs</a>: Dollar sign is allowed in identifiers.</li>
<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>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alignment.html#Alignment">Alignment</a>: Inquiring about the alignment of a type or variable.</li>
<div class="doc_text">
-<p>For this release, the C++ front-end is considered to be fully functional but
-has not been tested as thoroughly as the C front-end. It has been tested and
-works for a number of non-trivial programs, but there may be lurking bugs.
-Please report any bugs or problems.</p>
+<p>For this release, the C++ front-end is considered to be fully
+tested and works for a number of non-trivial programs, including LLVM
+itself.</p>
</div>
(for example, GCC requires the <tt>-fno-strict-aliasing</tt> option). This
problem probably cannot be fixed.</li>
-<li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
-cannot include special floating point numbers like Not-A-Number or
-Infinity.</li>
-
<li><a href="http://llvm.cs.uiuc.edu/PR56">Zero arg vararg functions are not
supported</a>. This should not affect LLVM produced by the C or C++
frontends.</li>
<div class="doc_text">
<p>A wide variety of additional information is available on the LLVM web page,
-including mailing lists and publications describing algorithms and components
-implemented in LLVM. The web page also contains versions of the API
-documentation which is up-to-date with the CVS version of the source code. You
-can access versions of these documents specific to this release by going into
-the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
+including <a href="http://llvm.cs.uiuc.edu/docs/#maillist">mailing lists</a> and
+<a href="http://llvm.cs.uiuc.edu/pubs/">publications describing algorithms and
+components implemented in LLVM</a>. The web page also contains versions of the
+API documentation which is up-to-date with the CVS version of the source code.
+You can access versions of these documents specific to this release by going
+into the "<tt>llvm/doc/</tt>" directory in the LLVM tree.</p>
<p>If you have any questions or comments about LLVM, please feel free to contact
us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
projects / oota-llvm.git / blobdiff