<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
+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>
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 a broad range of
-C and C++ programs, including the SPEC CPU95 & 2000 suite. This release
-includes several major enhancements to the LLVM system, including a new
-PowerPC JIT, enhancements to the C/C++ front-end to provide source line number
-information in LLVM, a new <a href="CommandGuide/html/llvmc.html">compiler
-driver</a>, and several other enhancements listed below. It also includes
-bug fixes for those problems found since the 1.3 release.</p>
-
-<p>Note that this release seperates the LLVM Program Testsuite out of the
-main LLVM distribution into a seperate CVS repository and tarball. This
-reduces the size of the main LLVM distribution. Also note that LLVM now
-builds tools into llvm/Debug/bin by default instead of llvm/tools/Debug.</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 Just-In-Time compiler for the PowerPC target.</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>LLVM now optimizes global variables more aggressively 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>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="CommandGuide/html/llvmc.html">compiler driver</a>
- (llvmc) and
- an associated <a href="CommandGuide/html/llvm-ld.html">generic linker</a>
- (llvm-ld) have been added. The compiler driver is generic because it can be
- configured
- to pre-process, translate, optimize, assemble, and link code from any source
- language with an LLVM front-end. This makes it easier for compiler writers
- to hide the multiple steps required to compile a program (compiling,
- optimizing, linking runtime libraries, etc) in one simple command.
- </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 much faster and
- includes new targets (like dist-check, uninstall). One important user-visible
- change is that 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 JIT-Target interfaces <a href="http://llvm.cs.uiuc.edu/PR283">are
- now much simpler</a> and more powerful.
- </li>
- <li>LLVM now provides llvm-ar and llvm-ranlib tools for working with archives
- of LLVM bytecode files.</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 automatically generates assembly code writers
- from an abstract target descriptions, eliminating the need to write
- assembly printers manually.</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>The linker no longer <a href="http://llvm.cs.uiuc.edu/PR426">emits many
- useless warnings</a> when linking C++ programs.</a>
- </li>
- <li>The LLVM <a href="http://llvm.cs.uiuc.edu/PR352">#include namespace</a>
- has been made consistent. Files in <tt>llvm/include/{Support,Config}</tt>
- are now located in <tt>llvm/include/llvm/{Support,Config}</tt>.</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>The C++ frontend no longer expands and emits <a
- href="http://llvm.cs.uiuc.edu/PR459">all inline functions, even if they
- are unused</a>. It now properly tracks which functions are needed and
- only compiles those.</li>
-
- <li>Many improvements in the <a href="http://llvm.cs.uiuc.edu/PR256">autoconf
- and makefile systems</a> have been implemented.</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>The optimizer produces <a href="http://llvm.cs.uiuc.edu/PR362">more
- efficient code for std::min/std::max</a> and other similar functions.</li>
- <li>The X86 backend generates substantially faster code for floating point
- intensive programs.</li>
- <li>The PowerPC backend generates more efficient code in many common
- scenarios.</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/PR472">[cbackend] Static globals are
- prototyped as 'extern'</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/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 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
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>
<!-- *********************************************************************** -->
<ul>
<li>The following passes are incomplete or buggy, and may be removed in future
- releases: <tt>-pgmdep, -memdep, -ipmodref, -cee, -branch-combine,
- -instloops, -paths, -pre</tt></li>
+ 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, Alpha, and IA64 ports are experimental.</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. It has been
+<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>