"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" href="llvm.css" type="text/css">
- <title>LLVM 1.3 Release Notes</title>
+ <title>LLVM 1.5 Release Notes</title>
</head>
<body>
-<div class="doc_title">LLVM 1.3 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="#sparc-be">Known problems with the Sparc 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.3. 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.3/">LLVM 1.3 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 fourth public release of the LLVM compiler infrastructure. This
-release primarily improves the <a href="#codequality">performance of the
-code</a> produced by all aspects of the LLVM compiler and adds many <a
-href="#newfeatures">new features</a>, and <a href="#bugfix">fixes a few
-bugs</a> as well.</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 CPU2000 benchmarks, the Olden benchmarks, and the Ptrdist benchmarks. It
-has also been used to compile <b>many</b> other programs. LLVM now also works
-with a broad variety of C++ programs, though it has still received less testing
-than the C front-end.</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>
<div class="doc_text">
-
<ol>
-<li>The LLVM <a href="LangRef.html#i_select"><tt>select</tt></a> instruction is
-now fully implemented and supported by all transformations, native code
-generators, and the interpreter.</li>
-<li>Bugpoint can now narrow down code-generation bugs to a loop nest, where
-before it could only narrow them down to a function being miscompiled.</li>
-<li><a href="http://llvm.cs.uiuc.edu/PR40">Bugpoint can now debug arbitrary
-modes of llc</a> and lli, by passing them command line flags (e.g.,
-<tt>-regalloc=linearscan</tt>, <tt>-enable-correct-eh-support</tt>, etc.) </li>
-<li>The Control Flow Graph in the native code generators is no longer
-constrained to be the same as the CFG for the LLVM input code.</li>
-<li>The LLVM induction variable analysis routines have been rewritten.</li>
-<li>LLVM now has new loop unrolling and loop unswitching passes.</li>
-<li>The induction variable substitution pass performs linear function test
-replacement and exit value replacement optimizations.</li>
-<li>LLVM now has first-class support for <a href="GarbageCollection.html">Accurate
-Garbage Collection</a>, enabling the use of aggressive copying and generational
-collectors.</li>
-<li>LLVM now includes an implementation of Andersen's interprocedural alias
-analysis algorithm.</li>
-<li>Bugpoint can <a href="http://llvm.cs.uiuc.edu/PR327">extract individual
-basic blocks</a> to track down reduce miscompilation testcases.</li>
-<li>LLVM and the C front-end now work under Win32 using the
-<a href="http://www.cygwin.com">Cygwin</a> runtime libraries.
-This includes the JIT compiler.</li>
-<li>The LLVM code generator is now being <a
- href="CodeGenerator.html">documented</a>.</li>
-<li>There is a new tool, llvm-abcd, the Analysis of ByteCode Dumper (abcd).
-This tool can compute basic statistics and bytecode density statistics on a
-module or function basis and also dump out bytecode in a textual format that
-is lower level than assembly (values are not resolved from slot numbers).
-It should only be of interest to (a) those who are working to improve the
-bytecode format and (b) those who really want to understand or document the
-details of the bytecode format.</li>
-<li>The <a href="BytecodeFormat.html">LLVM Bytecode file format</a> is now
- being documented.</li>
-<li>LLVM now provides an <a href="LangRef.html#i_isunordered">llvm.isunordered</a> intrinsic
-for efficient implementation of unordered floating point comparisons.</li>
-<li>The llvmgcc front-end now supports the GCC builtins for ISO C99 floating
-point comparison macros (e.g., <tt>__builtin_islessequal</tt>).</li>
-<li>Now that there are more source files than can fit on a 32Kbyte command
-line (Linux's limit), there's a new utility for searching the sources. The
-llvmgrep tool in the utils directory combines an egrep and a find without
-passing filenames through the command line. This improves performance
-slightly. Simply run llvmgrep like you might egrep but leave off the file
-names.</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 and
+ Alpha.</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/PR82">LLVM cannot handle structures with
-more than 256 elements</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR38">[bugpoint] External functions used in
-non-instruction entities, such as global constant initializer</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR178">Stacker does not handle targets
-with 64-bit pointers.</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR290">Bugpoint doesn't support
-uses of external fns by immediate constant exprs</a></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>
</ol>
</div>
<div class="doc_text">
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR305">LLVM tools will happily spew
-bytecode onto your terminal</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR329">[llvmgcc] type names are not emitted
-for structure typedefs</a></li>
-<li>All documentation is now conformant to the HTML 4.01 (Strict) level.</li>
-<li>The spurious "WARNING: Found global types that are not compatible" warning
-produced when linking C++ programs has been fixed.</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/PR301">Minor configure bugs with
--disable/enable-povray and -disable-spec</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR289">shell scripts output by gccld don't
-work if you change PATH</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR364">[llvmgcc] llvmgcc does not compile
-with gcc 3.4</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR373">[llvmgcc] obstack.h relies on
-obsolete casts-as-lvalues GCC extension</a></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>Fixed: <a href="http://llvm.cs.uiuc.edu/PR309">[vmcore] Code quality problem
-due to long operand of getelementptr</a></li>
-
-<li>The X86 backend now generates substantially better code for 64-bit integer
-and floating point operations.</li>
-
-<li>The -inline pass no longer inlines mutually recursive functions until it
-hits the inlining threshold.</li>
-
-<li>The -inline pass no longer misses obvious inlining opportunities just
-because the callee eventually calls into an external function.</li>
-
-<li>The -simplifycfg pass can now "if convert" simple statements into the new
-<tt>select</tt> instruction.</li>
-
-<li>The -loopsimplify pass can now break <a
-href="http://llvm.cs.uiuc.edu/PR35">natural loops with multiple backedges</a>
-into multiple nested loops. This enables a variety of subsequent
-optimizations.</li>
-
-<li>The -adce pass can now eliminate calls to functions that do not not write to
-memory.</li>
-
-<li>The link-time optimizer now runs the -prune-eh pass (to remove unused
-exception handlers).</li>
-
-<li>The -simplifycfg pass can now eliminate simple correlated branches (such as
-"<tt>if (A < B && A < B)</tt>", and can turn short-circuiting
-operators into the strict versions when useful (such as "<tt>if (A < B || A
-> C)</tt>" into "<tt>if (A < B | A > C)</tt>"</li>
-
-<li>LLVM now has infrastructure for (simple and sparse conditional) constant
-propagation of function calls. It currently supports a few math library
-functions like sqrt/sin/cos/etc.</li>
-
-<li>The C backend now emits <a href="http://llvm.cs.uiuc.edu/PR334">Syntactic
-loops</a> in the code to help C compilers whose optimizers do not recognize
-loops formed from gotos (like GCC).</li>
-
-<li>Fixed: <a href="http://llvm.cs.uiuc.edu/PR368">[sparcv9] null
-often spilled to constant pool</a>.</li>
+ <li></li>
</ol>
</div>
<div class="doc_text">
-<p>Bugs in the LLVM Core:</p>
+<p>Bugs fixed in the LLVM Core:</p>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR330">[vmcore] Linker causes erroneous
-asssertion</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR306">[loopsimplify] Loop simplify
-incorrectly updates dominator information</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR310">[tailduplicate] DemoteRegToStack
-breaks SSA form</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR313">[X86] JIT miscompiles unsigned short
-to floating point cast</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR332">[adce] Crash handling unreachable
-code that unwinds</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR333">[sparc] LLC can't emit 2 functions
-of the same name, both having constant pools</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR337">[livevar] Live variables missed
-physical register use of aliased definition</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR340">Verifier misses malformed switch instruction</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR315">[jit] abort, don't warn, when missing external functions encountered</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR369">[X86] stackifier crash on floating point setcc X, X</a></li>
+ <li><a href="http://llvm.cs.uiuc.edu/PR491">[dse] DSE deletes stores that
+ are partially overwritten by smaller stores</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/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 in the C/C++ front-end:</p>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR377">[llvmgcc] miscompilation of staticly initialized unsigned bitfields</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR326">[llvmgcc] Crash on use of undeclared
-enum type</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR298">[llvmgcc] Variable length array
-indexing miscompiled</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR355">[llvmgcc] Errors handling function
-prototypes that take opaque structs by-value</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR374">[llvmgcc] Crash compiling variable
-length array of structures</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>PowerPC-based Mac OS X boxes, running 10.3 and above (C backend and
- interpreter only, no native codegen is available yet).</li>
-<li>Intel and AMD machines running on Win32 with the Cygwin libraries.</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
<a href="http://www.gnu.org/software/autoconf/">GNU autoconf</a> to adapt itself
to the machine and operating system on which it is built. However, minor
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).</p>
-
-</div>
-
-<!--=========================================================================-->
-<div class="doc_subsection">
-In this release, the following portability problems were fixed:
-</div>
-
-<div class="doc_text">
-
-<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR304">warnings compiling Stacker compiler
-on Mac OS X</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR308">Archive file reader doesn't
-understand abbreviated names in headers</a></li>
-</ol>
-
</div>
<!-- *********************************************************************** -->
components, please contact us on the llvmdev list.</p>
<ul>
-<li>The following passes are incomplete or buggy: <tt>-pgmdep, -memdep,
- -ipmodref, -sortstructs, -swapstructs, -cee</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-ar</tt> tool is incomplete and probably buggy.</li>
-<li>The <tt>llvm-db</tt> tool is in a very early stage of development.</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 -regalloc=iterativescan)
+ is not stable.</li>
+<li>The SparcV8 and Alpha 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>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>It is not possible to <tt>dlopen</tt> an LLVM bytecode file in the JIT.</li>
-
-<li>Linking in static archive files (.a files) is very slow (there is no symbol
-table in the archive).</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>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><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>
</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>
<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>
<ul>
<li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
front-end</a>.</li>
+
+<li><b>IA-64 specific</b>: The C++ front-end does not use <a
+href="http://llvm.cs.uiuc.edu/PR406">IA64 ABI compliant layout of v-tables</a>.
+In particular, it just stores function pointers instead of function
+descriptors in the vtable. This bug prevents mixing C++ code compiled with
+LLVM with C++ objects compiled by other C++ compilers.</li>
+
</ul>
+
</div>
<!-- _______________________________________________________________________ -->
<div class="doc_text">
<ul>
- <li>Optimized (Release) versions of LLVM built with GCC 3.3.2 or 3.3.3 will
- produce an llc tool that always enters an infinite loop due to what
- appears to be an optimization bug (-O2 and -O3) in those versions of GCC.
- This problem does not happen in GCC 3.3.1 nor GCC 3.4.0 nor does it happen if
- you build a Debug version of LLVM. You are cautioned not to use GCC 3.3.2 or
- GCC 3.3.3 to build Optimized versions of LLVM. It is unclear whether this problem
- affects other backends but it is unlikely.</li>
+ <li>none yet</li>
</ul>
</div>
<!-- ======================================================================= -->
<div class="doc_subsection">
- <a name="sparc-be">Known problems with the Sparc back-end</a>
+ <a name="sparcv9-be">Known problems with the SparcV9 back-end</a>
</div>
<div class="doc_text">
<ul>
-<li>There are several programs in the LLVM testsuite that the Sparc code generator is known to miscompile.</li>
+<li><a href="http://llvm.cs.uiuc.edu/PR60">[sparcv9] SparcV9 backend miscompiles
+several programs in the LLVM test suite</a></li>
+</ul>
+
+</div>
+
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+ <a name="ppc-be">Known problems with the PowerPC back-end</a>
+</div>
+
+<div class="doc_text">
+
+<ul>
+<li>none yet</li>
</ul>
</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>
projects / oota-llvm.git / blobdiff