<html>
<head>
<link rel="stylesheet" href="llvm.css" type="text/css">
- <title>LLVM 1.1 Release Notes</title>
+ <title>LLVM 1.3 Release Notes</title>
</head>
<body>
-<div class="doc_title">
- LLVM 1.1 Release Notes
-</div>
+<div class="doc_title">LLVM 1.3 Release Notes</div>
<ol>
<li><a href="#intro">Introduction</a></li>
<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="#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>
</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.3. 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.3/">LLVM 1.3 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
<div class="doc_text">
-<p>This is the second public release of the LLVM compiler infrastructure. This
-release is primarily a bugfix release, dramatically improving the C/C++
-front-end, and improving support for C++ in the LLVM core. This release also
-includes a few new features, such as a simple profiler, support for Mac OS/X,
-better interoperability with external source bases, a new example language
-front-end, and improvements in a few optimizations.</p>
-
-<p>At this time, LLVM is known to correctly compile the C & C++ SPEC CPU2000
-benchmarks with the C backend (X86 only), 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>
+This is the fourth public release of the LLVM compiler infrastructure.
</p>
<p>
-Note 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. Support for unwinding will be added in a future release.
+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>
-
<!--=========================================================================-->
<div class="doc_subsubsection">
-This release implements the following new features:
+<a name="newfeatures">This release implements the following new features:</a>
</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 OS/X! Mac OS/X users can
-now explore the LLVM optimizer with the C backend and interpreter. Note that
-LLVM requires GCC 3.3 on Mac OS/X.</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 lack of namespace support in GDB 5.x, you will probably
-want to upgrade to GDB 6 or better to debug LLVM code.</li>
-
-<li>
-The build system now copies Makefiles dynamically from the source tree to the
-object tree as subdirectories are built. This means that:
- <ol>
- <li>
- New directories can be added to the source tree, and the build will
- automatically pick them up (i.e. no need to re-run <tt>configure</tt>).
- </li>
-
- <li>
- You will need to build LLVM from the top of the object tree once to ensure
- that all of the Makefiles are copied into the object tree subdirectories.
- </li>
- </ol>
-</li>
-
-<li>A front-end for "Stacker" (a simple Forth-like language) is now
- <a href="http://llvm.cs.uiuc.edu/PR136">included in the main LLVM tree</a>.
- Additionally, Reid Spencer, the author, contributed a document <a href="Stacker.html">describing his experiences writing Stacker, and the language itself</a>. This document is invaluable for others writing front-ends targetting LLVM.</li>
-
-<li>The <tt>configure</tt> script will now configure all projects placed in the
-<tt>llvm/projects</tt> directory.</li>
-
-<li>The <tt>-tailcallelim</tt> pass can now introduce "accumulator" variables
- to transform functions in many common cases that it could not before.</li>
-
-<li>The <tt>-licm</tt> pass can now sink instructions out the bottom of loops
-in addition to being able to hoist them out the top.</li>
-
-<li>The <tt>-basicaa</tt> pass (the default alias analysis) has been upgraded
-to be <a href="http://llvm.cs.uiuc.edu/PR86">significantly more
-precise</a>.</li>
-
-<li>LLVM 1.1 implements a simple size optimization for LLVM bytecode files.
- This means that the 1.1 files are smaller than 1.0, but that 1.0 won't
- read 1.1 bytecode files.</li>
-
-<li><a href="http://llvm.cs.uiuc.edu/PR140">The gccld program produces a runner script that includes command-line options to load the necessary shared objects.</a></li>
+<li>The LLVM <a href="LangRef.html#i_select"><tt>select</tt></a> instruction is
+now fully implemented and supported by all targets.</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>
</ol>
</div>
<ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR88">The interpreter does not support
-invoke or unwind</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR82">LLVM cannot handle structures with more than 256 elements</a></li>
+</ol>
-<li><a href="http://llvm.cs.uiuc.edu/PR99">Interpreter does not support the
-<tt>vaarg</tt> instruction</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR117">llvm-nm cannot read archive
-files</a></li>
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+<a name="qualityofimp">In this release, the following Quality of Implementation issues were fixed:</a>
+</div>
-<li><a href="http://llvm.cs.uiuc.edu/PR146">Interpreter does not handle
-setne constant expression</a></li>
+<ol>
+<li><a href="http://llvm.cs.uiuc.edu/PR305">LLVM tools will happily spew bytecode onto your terminal</a></li>
</ol>
-
<!--=========================================================================-->
<div class="doc_subsubsection">
-In this release, the following Quality of Implementation issues were
-fixed:
+In this release, the following build problems were fixed:
</div>
<ol>
+<li></li>
+</ol>
-<li>The C++ front-end now compiles functions to
- <a href="http://llvm.cs.uiuc.edu/PR29">use the linkonce linkage type</a>
- more, giving the optimizer more freedom.</a></li>
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+<a name="codequality">In this release, the following Code Quality issues were fixed:</a>
+</div>
+
+<ol>
+<li><a href="http://llvm.cs.uiuc.edu/PR309">[vmcore] Code quality problem due to
+long operand of getelementptr</a></li>
-<li>The C front-end now <a href="http://llvm.cs.uiuc.edu/PR84">generates
- type-safe code</a> in several cases that it did not before, which prevented
- some important optimizations.</li>
+<li>The X86 backend now generates substantially better code for 64-bit integer
+and floating point operations.</li>
-<li>The LLVM build system has been taught to catch some common configuration
- problems that <a href="http://llvm.cs.uiuc.edu/PR96">caused it to get
- horribly confused</a> before.</li>
+<li>The -inline pass no longer inlines mutually recursive functions until it
+hits the inlining threshold.</li>
-<li>The LLVM header files are now
- <a href="http://llvm.cs.uiuc.edu/PR114">-Wold-style-cast clean</a>.</li>
+<li>The -inline pass no longer misses obvious inlining opportunities just
+because the callee eventually calls into an external function.</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>
+<li>The -simplifycfg pass can now "if convert" simple statements into the new
+<tt>select</tt> instruction.</li>
-<li>In C++, methods and functions in anonymous namespaces <a href="http://llvm.cs.uiuc.edu/PR85">now get internal linkage</a>.</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>Constant initializers now generate loops instead of potentially <a href="http://llvm.cs.uiuc.edu/PR75">huge amounts of straight-line code</a>.</li>
+<li>The -adce pass can now eliminate calls to functions that do not not write to
+memory.</li>
-<li>Code for running C++ destructors is now properly shared when possible. Before, the C++ front-end
-<a href="http://llvm.cs.uiuc.edu/PR11">generated N^2 amounts of duplicated cleanup code</a> in some cases.</li>
+<li>The link-time optimizer now runs the -prune-eh pass (to remove unused
+exception handlers.</li>
-<li>The JIT used to <a href="http://llvm.cs.uiuc.edu/PR177">generate code for
- all functions pointed to by globals</a> immediately, before the program
- started execution, but now it waits until the first time they are called to
- compile them. This dramatically speeds up short runs of large C++ programs,
- which often have large numbers of functions pointed to by vtables.</li>
</ol>
<!--=========================================================================-->
<div class="doc_subsubsection">
-In this release, the following bugs in the previous release were fixed:
+<a name="bugfix">In this release, the following bugs in the previous release were fixed:</a>
</div>
<p>Bugs in the LLVM Core:</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/PR64">[constmerge] Constant merging pass merges constants with external linkage</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/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/PR83">[X86] Emission of global bool initializers broken</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/PR95">SymbolTable::getUniqueName is very inefficient</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/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/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/PR116">[adce] ADCE considers blocks without postdominators to be unreachable</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/PR130">[vmcore] Symbol table doesn't rename colliding variables during type resolution</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR138">Archive reader does not understand 4.4BSD/Mac OS X long filenames</a></li>
-<li><a href="http://llvm.cs.uiuc.edu/PR30">[llvm-ar] Command line arguments have funny syntax</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>
</ol>
+
<p>Bugs in the C/C++ front-end:</p>
<ol>
-<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/PR65">C front-end miscompiles the builtin_expect intrinsic!</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/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/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/PR94">llvm-gcc tries to add bools</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/PR54">C front-end miscompiles unsigned enums whose LLVM types are signed</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/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/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/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/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>
-<li><a href="http://llvm.cs.uiuc.edu/PR165">[llvmg++] call through array of pointers to member functions causes assertion</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 has been tested on Sun UltraSPARC workstations running Solaris 8.
+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
+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. 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
+href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug database</a> and submit a bug if
there isn't already one.</p>
</div>
-<!-- _______________________________________________________________________ -->
-<!--
-</ul><h4><a name="portability"><hr size=0>Portability Problems</h4><ul>
--->
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+ <a name="experimental">Experimental features included with this release</a>
+</div>
+
+<div class="doc_text">
+
+<p>
+The following components of this LLVM release are either untested, known to be
+broken or unreliable, or are in early development. These components should not
+be relied on, and bugs should not be filed against them, but they may be useful
+to some people. In particular, if you would like to work on one of these
+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>
+</ul>
+</div>
<!-- ======================================================================= -->
<div class="doc_subsection">
<li>Linking in static archive files (.a files) is very slow (there is no symbol
table in the archive).</li>
-<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/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>
</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>
-</ul>
+<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>
+
+</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/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>
<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>
<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>,
<p>The following extensions <b>are</b> known to be supported:</p>
<ol>
+ <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/Statement-Exprs.html#Statement%20Exprs">Statement Exprs</a>: Putting statements and declarations inside expressions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Typeof.html#Typeof">Typeof</a>: <code>typeof</code>: referring to the type of an expression.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Lvalues.html#Lvalues">Lvalues</a>: Using <code>?:</code>, "<code>,</code>" and casts in lvalues.</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/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/Case-Ranges.html#Case%20Ranges">Case Ranges</a>: `case 1 ... 9' and such.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Alternate-Keywords.html#Alternate%20Keywords">Alternate Keywords</a>:<code>__const__</code>, <code>__asm__</code>, etc., for header files.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Incomplete-Enums.html#Incomplete%20Enums">Incomplete Enums</a>: <code>enum foo;</code>, with details to follow.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Function-Names.html#Function%20Names">Function Names</a>: Printable strings which are the name of the current function.</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>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html#Unnamed%20Fields">Unnamed Fields</a>: Unnamed struct/union fields within structs/unions.</li>
<li><a href="http://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute%20Syntax">Attribute Syntax</a>: Formal syntax for attributes.</li>
</ol></li>
<div class="doc_text">
-<p>For this release, the C++ front-end is considered to be fully functional, but
+<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>
</div>
<!-- _______________________________________________________________________ -->
-<div class="doc_subsubsection">
- Bugs
-</div>
+<div class="doc_subsubsection">Bugs</div>
<div class="doc_text">
<ul>
<li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
- front-end</a></li>
+ front-end</a>.</li>
</ul>
-
</div>
<!-- _______________________________________________________________________ -->
<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
<div class="doc_text">
<ul>
-
-<li>The X86 code generator <a
-href="http://llvm.cs.uiuc.edu/PR16">does not currently
-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>None so far.
</ul>
</div>
<div class="doc_text">
<ul>
-
-<li>The Sparc code generator <a
-href="http://llvm.cs.uiuc.edu/PR15">does not currently
-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>There are several programs in the LLVM testsuite that the Sparc code generator is known to miscompile.</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
<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