Merged from RELEASE_16.

[oota-llvm.git] / docs / ReleaseNotes.html

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index 2374278d35653b9476a6ab15612397b537fac426..e5378ba9602a0973df56db40ba8ed0d3ea22fc19 100644 (file)
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -64,7 +64,7 @@ href="http://llvm.org/releases/">releases page</a>.</p>
 release incorporates a large number of enhancements and additions (primarily in
 the code generator), which combine to improve the quality of the code generated
 by LLVM by up to 30% in some cases.  This release is also the first release to
-have first-class support for Mac OS/X: all of the major bugs have been shaken
+have first-class support for Mac OS X: all of the major bugs have been shaken
 out and it is now as well supported as Linux on X86.</p>
 
 </div>
@@ -111,8 +111,8 @@ definition.  The first line specifies what to match (a xor with an arbitrary
 immediate) the second line specifies what to produce:</p>
 
 <div class="doc_code"><p>
-<pre>def : Pat<(xor GPRC:$in, imm:$imm),
-          (XORIS (XORI GPRC:$in, (LO16 imm:$imm)), (HI16 imm:$imm))>;
+<pre>def : Pat&lt;(xor GPRC:$in, imm:$imm),
+          (XORIS (XORI GPRC:$in, (LO16 imm:$imm)), (HI16 imm:$imm))&gt;;
 </pre>
 </p></div>
 
@@ -172,7 +172,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
     giving up completely.  In addition, <a href="http://llvm.org/PR576">the JIT
     debugging mode of bugpoint is much faster</a>.</li>
   <li>LLVM now includes Xcode project files in the llvm/Xcode directory.</li>
-  <li>LLVM now supports Mac OS/X on Intel.</li>
+  <li>LLVM now supports Mac OS X on Intel.</li>
   <li>LLVM now builds cleanly with GCC 4.1.</li>
 </ol>
 </div>
@@ -193,7 +193,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
       we find that it often speeds up programs from 10-40% depending on the
       program.</li>
   <li>The code produced when exception handling is enabled is far more
-      efficient in some cases, particularly on Mac OS/X.</li>
+      efficient in some cases, particularly on Mac OS X.</li>
 </ol>
 </div>
 
@@ -229,7 +229,7 @@ this case, using "<tt>llc -march=ppc32 -mcpu=g5 -mattr=-altivec</tt>".</p>
 <div class="doc_text">
 <ol>
   <li>A vast number of bugs have been fixed in the PowerPC backend and in
-      llvm-gcc when configured for Mac OS/X (particularly relating to ABI
+      llvm-gcc when configured for Mac OS X (particularly relating to ABI
       issues).  For example:
       <a href="http://llvm.org/PR603">PR449</a>,
       <a href="http://llvm.org/PR594">PR594</a>, 
@@ -316,6 +316,19 @@ components, please contact us on the llvmdev list.</p>
 
 </div>
 
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+  <a name="build">Known problems with the Build System</a>
+</div>
+
+<div class="doc_text">
+
+<ul>
+  <li>The <a href="http://llvm.org/PR656">configure script sometimes fails on Solaris/Sparc</a>. A work around is documented in <a href="http://llvm.org/PR656">PR656.</a></li>
+</ul>
+</div>
+
+
 <!-- ======================================================================= -->
 <div class="doc_subsection">
   <a name="core">Known problems with the LLVM Core</a>
@@ -635,8 +648,6 @@ several programs in the LLVM test suite</a></li>
 <li>On 21164s, some rare FP arithmetic sequences which may trap do not have the
 appropriate nops inserted to ensure restartability.</li>
 
-<li>Due to the vararg problems, C++ exceptions do not work.  Small changes are required to the CFE (which break correctness in the exception handler) to compile the exception handling library (and thus the C++ standard library).</li>
-
 </ul>
 
 </div>