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

Chris Lattner lattner at cs.uiuc.edu
Thu Oct 23 23:04:01 PDT 2003


Changes in directory llvm/docs:

ReleaseNotes.html updated: 1.11 -> 1.12

---
Log message:

Update list of passes and buglist.


---
Diffs of the changes:  (+10 -1)

Index: llvm/docs/ReleaseNotes.html
diff -u llvm/docs/ReleaseNotes.html:1.11 llvm/docs/ReleaseNotes.html:1.12
--- llvm/docs/ReleaseNotes.html:1.11	Wed Oct 22 13:19:08 2003
+++ llvm/docs/ReleaseNotes.html	Thu Oct 23 23:03:19 2003
@@ -64,7 +64,10 @@
 The default optimizer sequence used by the C/C++ front-ends is:<p>
 
 <ol>
+<li>CFG simplification (-simplifycfg)
 <li>Interprocedural dead code elimination (-globaldce)
+<li>Interprocedural constant propagation (-ipconstprop)
+<li>Dead argument elimination (-deadargelim)
 <li>Exception handling pruning (-prune-eh)
 <li>Function inlining (-inline)
 <li>Instruction combining (-instcombine)
@@ -94,6 +97,7 @@
 <ol>
 <li>Global constant merging (-constmerge)
 <li>[optional] Internalization [which marks most functions and global variables static] (-internalize)
+<li>Interprocedural constant propagation (-ipconstprop)
 <li>Interprocedural dead argument elimination (-deadargelim)
 <li>Instruction combining (-instcombine)
 <li>CFG simplification (-simplifycfg)
@@ -103,7 +107,8 @@
 At this time, LLVM is known to work properly with SPEC CPU 2000, 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.  For these programs you must use the C backend.<p>
+long jumping (including 253.perlbmk in SPEC).  For these programs you must use
+the C backend.<p>
 
 
 <!-- *********************************************************************** -->
@@ -357,6 +362,10 @@
 
 <li><a href="http://llvm.cs.uiuc.edu/PR33">Initializers for global variables</a>
 cannot include special floating point numbers like Not-A-Number or Infinity.<p>
+
+<li><a href="http://zion.cs.uiuc.edu/PR56">Zero arg vararg functions are not 
+supported</a>.  This should not affect LLVM produced by the C or C++ 
+frontends.<p>
 
 <li>The code produces by the C back-end has only been tested with the Sun CC and
 GCC compilers.  It is possible that it will have to be adjusted to support other





More information about the llvm-commits mailing list