<html>
<head>
<link rel="stylesheet" href="llvm.css" type="text/css">
- <title>LLVM 1.1 Release Notes</title>
+ <title>LLVM 1.2 Release Notes</title>
</head>
<body>
<div class="doc_title">
- LLVM 1.1 Release Notes
+ LLVM 1.2 Release Notes
</div>
<ol>
<li><a href="#install-instructions">Installation Instructions</a></li>
<li><a href="#knownproblems">Known Problems</a>
<ul>
-<!-- <li><a href="#portabilityprobs">Portability Problems</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>
</ol>
<div class="doc_text">
- <p><b>Written by
<a href="mailto:sabre@nondot.org">Chris Lattner</a></b><p>
+ <p><b>Written by
the <a href="http://llvm.cs.uiuc.edu">LLVM team</a></b><p>
</div>
<!-- *********************************************************************** -->
<div class="doc_text">
<p>This document contains the release notes for the LLVM compiler
-infrastructure, release 1.1. 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.2. Here we describe the status of LLVM, including any
+known problems and bug fixes 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.1/">LLVM 1.1 web site</a>. If you are
-not reading this on the LLVM web pages, you should probably go there, because
+href="http://llvm.cs.uiuc.edu/releases/1.2/">LLVM 1.2 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
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, that this document applies
-to the <i>next</i> release, not the previous one. To see the release notes for
-the
previous release, see the <a
+<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
href="http://llvm.cs.uiuc.edu/releases/">releases page</a>.</p>
</div>
<div class="doc_text">
-<p>This is the second public release of the LLVM compiler infrastructure. This
-release implements the following new features:</p>
+<p>This is the third public release of the LLVM compiler infrastructure.
+</p>
+
+<p>At this time, LLVM is known to correctly compile and run all non-unwinding 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 much less testing than the C front-end.
+</p>
+
+<p>
+The LLVM native code generators are very stable but do not currently support
+unwinding (exception throwing or <tt>longjmp</tt>ing), which prevent them from
+working with programs like the <tt>253.perlbmk</tt> in SPEC CPU2000. The C
+backend and the rest of LLVM supports these programs, so you can
+still use LLVM with them. Support for unwinding will be added in a future
+release.
+</p>
+
+
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+This release implements the following new features:
+</div>
<ol>
-<li><a
-href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000528.html">A new
-LLVM profiler, similar to gprof</a> is available</li>
-
-<li>LLVM and the C/C++ front-end now compile on Mac OSX! Mac OSX users can
-now explore the LLVM optimizer with the C backend (note that LLVM requires GCC
-3.3 on Mac OSX).</li>
-
-<li>LLVM has been <a
-href="http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-November/000554.html">moved
-into an 'llvm' C++ namespace</a>, for easier integration with third-party
-code. Note that due to a bug in GDB 5.x, to debug namespacified LLVM code,
-you will need to upgrade to GDB 6.</li>
+<li></li>
+<li></li>
</ol>
-<p>In this release, the following missing features were implemented:</p>
+
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+In this release, the following missing features were implemented:
+</div>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR88">The interpreter does not support
-invoke or unwind</a></li>
+<li></li>
+<li></li>
+</ol>
+
+
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+In this release, the following Quality of Implementation issues were fixed:
+</div>
-<li><a href="http://llvm.cs.uiuc.edu/PR99">Interpreter does not support the
-<tt>vaarg</tt> instruction</a></li>
+<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR117">llvm-nm cannot read archive
-files</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR135">JIT should lazily initialize global variables</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR192">[X86] X86 Backend never releases memory for machine code structures</a></li>
+<li></li>
</ol>
-<p>In this release, the following Quality of Implementation issues were
-fixed:</p>
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+In this release, the following Code Quality issues were fixed:
+</div>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR29">C++ front-end is not generating
-linkonce linkage type when it can</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR187">[loopsimplify] Many pointless phi nodes are created</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR84">C front-end doesn't emit
-getelementptr for address of array element</a></li>
-
-<li><a href="http://llvm.cs.uiuc.edu/PR96">Bad path to the C/C++ frontend causes
-build problems</a></li>
+<li></li>
+</ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR114">LLVM header files should be -Wold-style-cast clean</a></li>
-<li>The LLVM bytecode reader has been <a
-href="http://llvm.cs.uiuc.edu/PR127">sped up a lot</a> (up to 4x in some
-cases).</li>
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+In this release, the following bugs in the previous release were fixed:
+</div>
-<li>Methods and functions in anonymous namespaces <a href="http://llvm.cs.uiuc.edu/PR85">now get internal linkage</a>.</li>
+<p>Bugs in the LLVM Core:</p>
-<li>Constant initializers now generate loops instead of potentially <a href="http://llvm.cs.uiuc.edu/PR75">huge amounts of straight-line code</a>.</li>
+<ol>
+<li><a href="http://llvm.cs.uiuc.edu/PR179">[licm] LICM promotes volatile memory
+locations to registers</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR191">[licm] Memory read after free causes
+infrequent crash</a></li>
</ol>
-<p>In this release, the following bugs in the previous release were fixed:</p>
+
+<p>Bugs in the C/C++ front-end:</p>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR57">[inliner] Inlining invoke with PHI in unwind target is broken</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR58">[linker] linkonce globals should link successfully to external globals</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR59">C++ frontend can crash when compiling virtual base classes</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR62">C backend fails on constant cast expr to ptr-to-anonymous struct</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR63">#ident is not recognized by C frontend</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR64">[constmerge] Constant merging pass merges constants with external linkage</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR65">C front-end miscompiles the builtin_expect intrinsic!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR66">[scalarrepl] Scalar Replacement of aggregates is decimating structures it shouldn't be</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR67">1.0 precompiled libstdc++ does not include wchar_t support</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR68">llvmgcc asserts when compiling functions renamed with asm's</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR69">C frontend crashes on some programs with lots of types.</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR70">[instcombine] Resolving invoke inserts cast after terminator</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR71">llvm-as crashes when labels are used in phi nodes</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR72">[build problem] Callgraph.cpp not pulled in from libipa.a</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR77">Variables in scope of output setjmp
-calls should be volatile</a>. Note that this does not effect correctness on
-many platforms, such as X86.</li>
-<li><a href="http://llvm.cs.uiuc.edu/PR79">llvm-gcc crashes compiling global union initializer</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR80">C front-end crash on empty structure</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR81">CFrontend crashes when compiling C99 compound expressions</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR83">[X86] Emission of global bool initializers broken</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR87">llvm-gcc infinite loops on "case MAXINT:"</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR89">[C++] Catch blocks make unparsable labels</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR90">[C++] Initializing array with constructable objects fail</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR91">[gccld] The -r (relinking) option does not work correctly</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR92">[bcreader] Cannot read shift constant expressions from bytecode file</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR93">[lowersetjmp] Lowersetjmp pass breaks dominance properties!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR94">llvm-gcc tries to add bools</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR95">SymbolTable::getUniqueName is very inefficient</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR98">[buildscripts] Building into objdir with .o in it fails</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR101">[setjmp/longjmp] Linking C programs which use setjmp/longjmp sometimes fail with references to the C++ runtime library!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR104">[c++] C++ Frontend lays out superclasses like anonymous bitfields!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR107">AsmParser Misses Symbol Redefinition Error</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR108">gccld -Lfoo -lfoo fails to find ./foo/libfoo.a</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR110">[bcreader] Incorrect cast causes misread forward constant references</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR112">Casting a string constant to void crashes llvm-gcc</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR116">[adce] ADCE considers blocks without postdominators to be unreachable</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR54">C front-end miscompiles unsigned enums whose LLVM types are signed</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR123">[X86] div and rem constant exprs invalidate iterators!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR125">[llvmg++] Enum types are incorrectly shrunk to smaller than 'int' size</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR128">[llvmg++] Cannot use pointer to member to initialize global</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR130">[vmcore] Symbol table doesn't rename colliding variables during type resolution</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR131">[llvm-gcc] ?: operator as lvalue not implemented</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR133">[C/C++] Bogus warning about taking the address of 'register' variable</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR97">bugpoint must not pass -R<directory> to Mach-O linker</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR113">crash assigning into an array in a struct which contains a bitfield</a>.</li>
-<li><a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR140">gccld produces a runner script that includes command-line options to load the necessary shared objects</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR141">[llvm-gcc] Bitfields & large array don't mix well</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR132">[llvm-gcc] Complex division is not supported</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR143">[llvm-gcc] Illegal union field reference</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR148">[llvmg++] Front-end attempts to return structure by value</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR152">[llvmg++] Pointer to member initializers not supported in constructors</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR155">[llvm-gcc] crash on union initialization</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR124">[llvm-g++] ?: expressions do not run correct number of destructors!</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR157">[llvm-gcc] Pointer & constant results in invalid shift</a></li>
-</ol><p>
-
-<p>At this time, LLVM is known to work properly with SPEC CPU 2000 (X86 only),
-the Olden benchmarks, and the Ptrdist benchmarks among many other programs.
-Note however that the Sparc and X86 backends do not currently support exception
-throwing or long jumping (including 253.perlbmk in SPEC). For these programs,
-you must use the C backend.</p>
+<li><a href="http://llvm.cs.uiuc.edu/PR186">Need weak linkage on memory
+management functions in libc runtime to allow them to be overriden</a></li>
+<li></li>
+</ol>
</div>
<div class="doc_text">
<p>LLVM has been extensively tested on Intel and AMD machines running Red
-Hat Linux, and Sun UltraSPARC workstations running Solaris 8. Additionally,
-LLVM works on Mac OS/X 10.3 and above, but only with the C back-end (no native
-backend for the PowerPC is available yet).
+Hat Linux and FreeBSD. It has also been tested on Sun UltraSPARC workstations running Solaris 8.
+Additionally,
+LLVM works on Mac OS X 10.3 and above, but only with the C backend or
+interpreter (no native backend for the PowerPC is available yet).
The core LLVM infrastructure uses "autoconf" for portability, so hopefully we
work on more platforms than that. However, it is likely that we
-missed something, and that minor porting is required to get LLVM to work on
+missed something and that minor porting is required to get LLVM to work on
new platforms. We welcome portability patches and error messages.</p>
</div>
<p>This section contains all known problems with the LLVM system, listed by
component. As new problems are discovered, they will be added to these
-sections.</p>
+sections. If you run into a problem, please check the <a
+href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
+there isn't already one.</p>
</div>
<li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with
more than 256 elements</a>.</li>
+<li>
+The gccld program
+<a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=139">
+does not link objects/archives in the order specified on the command line.
+</a>
+</li>
+
+<li>
+<a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=174">
+Tail duplication does not update SSA form correctly.
+</a>
+</li>
</ul>
</div>
</div>
<!-- _______________________________________________________________________ -->
-<div class="doc_subsubsection">
- Bugs
-</div>
+<div class="doc_subsubsection">Bugs</div>
<div class="doc_text">
-
<ul>
-
<li>C99 Variable sized arrays do not release stack memory when they go out of
scope. Thus, the following program may run out of stack space:
<pre>
}
</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/bugs/show_bug.cgi?id=182">
+Functions marked "extern inline" are not compiled into LLVM with linkonce
+linkage.
+</a>
+</li>
+
+
+<li>
+The memory management functions in the libc runtime
+<a href="http://llvm.cs.uiuc.edu/PR186">need weak linkage so that they can be
+overridden.
+</a>
+</li>
</ul>
-
</div>
<!-- _______________________________________________________________________ -->
the following extensions are known to <b>not be</b> supported:
<ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Local-Labels.html#Local%20Labels">Local Labels</a>: Labels local to a block.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels, and computed gotos.</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Labels-as-Values.html#Labels%20as%20Values">Labels as Values</a>: Getting pointers to labels and computed gotos.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html#Nested%20Functions">Nested Functions</a>: As in Algol and Pascal, lexical scoping of functions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constructing-Calls.html#Constructing%20Calls">Constructing Calls</a>: Dispatching a call to another function.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Extended%20Asm">Extended Asm</a>: Assembler instructions with C expressions as operands.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Constraints.html#Constraints">Constraints</a>: Constraints for asm operands.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Asm-Labels.html#Asm%20Labels">Asm Labels</a>: Specifying the assembler name to use for a C symbol.</li>
<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/Return-Address.html#Return%20Address">Return Address</a>: Getting the return or frame address of a function.</li>
<p>The following GCC extensions are <b>partially</b> supported. An ignored
attribute means that the LLVM compiler ignores the presence of the attribute,
but the code should still work. An unsupported attribute is one which is
- ignored by the LLVM compiler, which will cause a different interpretation of
+ ignored by the LLVM compiler and will cause a different interpretation of
the program.</p>
<ol>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function%20Attributes">Function Attributes</a>:
- Declaring that functions have no side effects, or that they can never
+ Declaring that functions have no side effects or that they can never
return.<br>
<b>Supported:</b> <tt>format</tt>, <tt>format_arg</tt>, <tt>non_null</tt>,
<tt>vector_size</tt>, <tt>dllimport</tt>,
<tt>dllexport</tt>, all target specific attributes.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html#Type%20Attributes">Type Attributes</a>: Specifying attributes of types.<br>
<b>Supported:</b> <tt>transparent_union</tt>, <tt>unused</tt>,
- <tt>deprecated</tt>, <tt>may_alias</tt>
+ <tt>deprecated</tt>, <tt>may_alias</tt><br>
<b>Unsupported:</b> <tt>aligned</tt>, <tt>packed</tt>,
all target specific attributes.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Variadic-Macros.html#Variadic%20Macros">Variadic Macros</a>: Macros with a variable number of arguments.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Escaped-Newlines.html#Escaped%20Newlines">Escaped Newlines</a>: Slightly looser rules for escaped newlines.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Subscripting.html#Subscripting">Subscripting</a>: Any array can be subscripted, even if not an lvalue.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>:Arithmetic on <code>void</code>-pointers and function pointers.</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html#Pointer%20Arith">Pointer Arith</a>: Arithmetic on <code>void</code>-pointers and function pointers.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Initializers.html#Initializers">Initializers</a>: Non-constant initializers.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions or arrays as values.</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Compound-Literals.html#Compound%20Literals">Compound Literals</a>: Compound literals give structures, unions,
+or arrays as values.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Designated-Inits.html#Designated%20Inits">Designated Inits</a>: Labeling elements of initializers.</li>
- <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>:Casting to union type from any member of the union.</li>
+ <li><a href="http://gcc.gnu.org/onlinedocs/gcc/Cast-to-Union.html#Cast%20to%20Union">Cast to Union</a>: Casting to union type from any member of the union.</li>
<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>
<div class="doc_text">
<p>For this release, the C++ front-end is considered to be fully functional but
-of <b>beta</b> quality. It has been tested and works for a number of simple
-programs that collectively exercise most of the language. Nevertheless, it has
-not been in use as long as the C front-end. Please report any bugs or
-problems.</p>
+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>
</div>
<ul>
<li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
- front-end</a></li>
-</ul>
+ front-end</a>.</li>
+<li>
+<a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=137">
+Code is generated for empty classes.
+</a>
+</li>
+</ul>
</div>
<!-- _______________________________________________________________________ -->
<li>The C++ front-end is based on a pre-release of the GCC 3.4 C++ parser. This
parser is significantly more standards compliant (and picky) than prior GCC
versions. For more information, see the C++ section of the <a
-href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.<p>
+href="http://gcc.gnu.org/gcc-3.4/changes.html">GCC 3.4 release notes</a>.</li>
<li>Destructors for local objects are not always run when a <tt>longjmp</tt> is
performed. In particular, destructors for objects in the <tt>longjmp</tt>ing
function and in the <tt>setjmp</tt> receiver function may not be run.
- Objects in intervening stack frames will be destroyed however (which is
+ Objects in intervening stack frames will be destroyed, however (which is
better than most compilers).</li>
<li>The LLVM C++ front-end follows the <a
different from the model used in the Itanium ABI, so <b>exceptions will not
interact correctly</b>. </li>
-<li><a href="http://llvm.cs.uiuc.edu/PR11">Code for executing destructors when
- unwinding is not shared</a> (this is a quality of implementation problem,
- which does not effect functionality).</li>
-
</ul>
</div>
support the <tt>unwind</tt> instruction</a>, so code that throws a C++ exception
or calls the C <tt>longjmp</tt> function will abort.</li>
+<li>
+<a href="http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=167">
+The llc program can crash on legal code.
+</a>
+</li>
</ul>
</div>
supported</a>. This should not affect LLVM produced by the C or C++
frontends.</li>
-<li>The code produces by the C back-end has only been tested with the Sun CC,
-GCC, and Intel compilers. It is possible that it will have to be adjusted to
-support other C compilers.</li>
-
</ul>
</div>
<div class="doc_text">
<p>A wide variety of additional information is available on the LLVM web page,
-including mailing lists publications describing algorithms and components
+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>
<p>If you have any questions or comments about LLVM, please feel free to contact
-us via the mailing lists.</p>
+us via the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">mailing
+lists</a>.</p>
</div>
<hr>
<address>
- <a href="http://jigsaw.w3.org/css-validator/"><img
+ <a href="http://jigsaw.w3.org/css-validator/
check/referer"><img
src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
<a href="http://validator.w3.org/check/referer"><img
src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
projects / oota-llvm.git / blobdiff