[llvm-commits] CVS: llvm-www/releases/1.0/docs/ReleaseNotes.html

[Chris Lattner]

Changes in directory llvm-www/releases/1.0/docs:

ReleaseNotes.html updated: 1.5 -> 1.6

---
Log message:

Clarify what is a bug and what isn't


---
Diffs of the changes:  (+24 -14)

Index: llvm-www/releases/1.0/docs/ReleaseNotes.html
diff -u llvm-www/releases/1.0/docs/ReleaseNotes.html:1.5 llvm-www/releases/1.0/docs/ReleaseNotes.html:1.6
--- llvm-www/releases/1.0/docs/ReleaseNotes.html:1.5	Mon Oct 27 11:57:10 2003
+++ llvm-www/releases/1.0/docs/ReleaseNotes.html	Mon Oct 27 12:28:05 2003
@@ -167,11 +167,11 @@
 <!-- _______________________________________________________________________ -->
 </ul><h4><a name="c-fe"><hr size=0>Known problems with the C front-end</h4><ul>
 
-<li>Inline assembly is not yet supported.<p>
+</ul><b>Bugs:</b><ul><p>
+
+<li><a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a>.<p>
+
 
-<li>"long double" is transformed by the front-end into "double".  There is no
-    support for floating point data types of any size other than 32 and 64 bits.
-    <p>
 <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>
@@ -181,6 +181,14 @@
     }
 </pre><p>
 
+</ul><b>Notes:</b><ul><p>
+
+<li>Inline assembly is not yet supported.<p>
+
+<li>"long double" is transformed by the front-end into "double".  There is no
+    support for floating point data types of any size other than 32 and 64 bits.
+    <p>
+
 <li>The following Unix system functionality has not been tested and may not work:
 <ol>
    <li><tt>sigsetjmp</tt>, <tt>siglongjmp</tt> - These are not turned into the
@@ -190,9 +198,6 @@
        - These functions have not been tested.
 </ol><p>
 
-<li>Bugs:<br>
-  <a href="http://llvm.cs.uiuc.edu/PR6">Oversized integer bitfields cause crash</a>.<br>
-<p>
 
 <li>Although many GCC extensions are supported, some are not.  In particular,
     the following extensions are known to <b>not be</b> supported:
@@ -305,9 +310,16 @@
 has not been in use as long as the C front-end.  Please report any bugs or
 problems.<p>
 
+</ul><b>Bugs</b>:<ul><p>
+
 <li>The C++ front-end inherits all problems afflicting the <a href="#c-fe">C
     front-end</a><p>
 
+<li><a href="http://llvm.cs.uiuc.edu/PR59">C++ frontend can crash when compiling
+virtual base classes</a> (fixed in 1.1)</li><p>
+
+</ul><b>Notes</b>:<ul><p>
+
 <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
@@ -328,13 +340,11 @@
     Itanium ABI C++ compilers (such as G++, the Intel and HP compilers, etc).
     <i>However</i>, the exception handling mechanism used by LLVM is very
     different from the model used in the Itanium ABI, so <b>exceptions will not
-    interact correctly</b>.
+    interact correctly</b>.<p>
 
-<li><a href="http://llvm.cs.uiuc.edu/PR11">Code for executing
-destructors when unwinding is not shared</a>.
-
-<li><a href="http://llvm.cs.uiuc.edu/PR59">C++ frontend can crash when compiling
-virtual base classes</a> (fixed in 1.1)</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).<p>
 
 <!-- _______________________________________________________________________ -->
 </ul><h4><a name="x86-be"><hr size=0>Known problems with the X86 back-end</h4><ul>
@@ -402,6 +412,6 @@
 Maintained By: <a href="http://llvm.cs.uiuc.edu/">The LLVM Team</a><br>
 <!-- Created: Wed Oct  1 17:38:54 CDT 2003 -->
 <!-- hhmts start -->
-Last modified: Mon Oct 27 11:56:23 CST 2003
+Last modified: Mon Oct 27 12:27:16 CST 2003
 <!-- hhmts end -->
 </body></html>