<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>
<!-- *********************************************************************** -->
<p>This document contains the release notes for the LLVM compiler
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
+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.2/">LLVM 1.2 web site</a>. If you are
-not reading this on the LLVM web pages, you should probably go there, because
+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 third public release of the LLVM compiler infrastructure. OTHER
-OVERVIEW STUFF HERE.
+<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
+<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 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 does support these programs however, so you can
-still use LLVM with them. Support for unwinding will be added in a future
-release.
+received less testing than the C front-end.
</p>
</div>
<ol>
-<li></li>
+<li><a href="SourceLevelDebugging.html">A new LLVM source-level debugger has been started.</a></li>
<li></li>
</ol>
</div>
<ol>
-<li></li>
-<li></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR16">Exception handling support in the X86
+& Sparc native code generators</a></li>
</ol>
<!--=========================================================================-->
<div class="doc_subsubsection">
-In this release, the following Quality of Implementation issues were
-fixed:
+In this release, the following Quality of Implementation issues were fixed:
</div>
<ol>
-<li></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><a href="http://llvm.cs.uiuc.edu/PR196">[vmcore] OpaqueType objects memory leak</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR182">[llvmgcc] C front-end does not compile "extern inline" into linkonce</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR73">Bytecode format inconsistent</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR209">[loadvn/inline/scalarrepl] Slow optimizations with extremely large basic blocks</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR224">[asmparser] Really slow parsing of types with complex upreferences</a></li>
+</ol>
-<li></li>
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+LLVM gained several improvements to its build and installation
+infrastructure in this release. There is now
+a <tt>autoconf/AutoRegen.sh</tt> script that you can run to rebuild the
+<tt>configure</tt> script and its associated files
+(<a href="http://llvm.cs.uiuc.edu/PR105">Bug 105</a>) as well as beta support
+for "make install" (<a href="http://llvm.cs.uiuc.edu/PR208">Bug 208</a> and
+<a href="http://llvm.cs.uiuc.edu/PR220">Bug 220</a>) and RPM package generation
+(<a href="http://llvm.cs.uiuc.edu/PR203">Bug 203</a>).
+Additionally, in this release, the following build problems were fixed:
+</div>
+
+<ol>
+<li><a href="http://llvm.cs.uiuc.edu/PR210">[build] Makefiles break if C frontend target string has unexpected value</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR214">[build] hard-wired assumption that shared-library extension is ".so"</a></li>
+<li><A href="http://llvm.cs.uiuc.edu/PR222">make tools-only doesn't make lib/Support</a></li>
+</ol>
+
+<!--=========================================================================-->
+<div class="doc_subsubsection">
+In this release, the following Code Quality issues were fixed:
+</div>
+
+<ol>
+<li><a href="http://llvm.cs.uiuc.edu/PR187">[loopsimplify] Many pointless phi nodes are created</a></li>
+<li>The X86 backend didn't generate <tt>fchs</tt> to negate floating point numbers</li>
+<li>The X86 backend didn't expand memcpy() into the <tt>rep movs</tt> instruction</li>
</ol>
<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>
+<li><a href="http://llvm.cs.uiuc.edu/PR194">[indvars] Induction variable
+canonicalization always makes 32-bit indvars</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR193">[constantmerge] Merging globals can
+cause use of invalid pointers!</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR212">[bcreader] Bytecode reader misreads 'long -9223372036854775808'!</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>
+<li><a href="http://llvm.cs.uiuc.edu/PR218">VMCore mishandles double -0.0</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR219">[X86] X86 backend code generates -0.0 as +0.0</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR223">[loopsimplify] Loopsimplify incorrectly updates dominator information</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR225">[pruneeh] -pruneeh pass removes invoke instructions it shouldn't</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR228">[sparc] Boolean constants are emitted as true and false</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR235">Tablegen aborts on errors</a></li>
</ol>
+
<p>Bugs in the C/C++ front-end:</p>
<ol>
<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>
+<li><a href="http://llvm.cs.uiuc.edu/PR202">[llvm-gcc] asserts when an extern inline function is redefined</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR204">[llvmg++] Dynamically initialized constants cannot be marked 'constant'</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR216">[llvmgcc] floating-point unary minus is incorrect for +0.0</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR221">[llvm-gcc] miscompilation of 'X = Y = Z' with aggregate values</a></li>
+<li><a href="http://llvm.cs.uiuc.edu/PR233">[llvmgcc] Structure copies result in a LOT of code</a></li>
</ol>
</div>
<p>LLVM has been extensively tested on Intel and AMD machines running Red
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>
<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>
</ul>
-
</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>
</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>,
<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>
<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>
<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>None so far.
</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