[llvm-commits] CVS: llvm-www/OpenProjects.html

[Chris Lattner]

Changes in directory llvm-www:

OpenProjects.html updated: 1.13 -> 1.14
---
Log message:

Add a new open project


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

 OpenProjects.html |   31 +++++++++++++++++++++----------
 1 files changed, 21 insertions(+), 10 deletions(-)


Index: llvm-www/OpenProjects.html
diff -u llvm-www/OpenProjects.html:1.13 llvm-www/OpenProjects.html:1.14
--- llvm-www/OpenProjects.html:1.13	Tue Apr 11 23:18:36 2006
+++ llvm-www/OpenProjects.html	Tue May  9 22:53:37 2006
@@ -7,8 +7,8 @@
   <li><a href="#improving">Improving the current system</a>
   <ol>
     <li><a href="#code-cleanups">Implementing Code Cleanup bugs</a></li>
-    <li><a href="#glibc">Port glibc to LLVM</a></li>
     <li><a href="#programs">Compile programs with the LLVM Compiler</a></li>
+    <li><a href="#llvmtest">Add programs to the llvm-test suite</a></li>
     <li><a href="#llvm_ir">Extend the LLVM intermediate representation</a></li>
     <li><a href="#benchmark">Benchmark the LLVM compiler</a></li>
     <li><a href="#misc_imp">Miscellaneous Improvements</a></li>
@@ -92,18 +92,29 @@
 
 <!-- ======================================================================= -->
 <div class="www_subsubsection">
-  <a name="glibc">Port glibc to LLVM</a>
+  <a name="llvmtest">Add programs to the llvm-test testsuite</a>
 </div>
 
 <div class="www_text">
 
-<p>It would be very useful to <a
-href="http://www.gnu.org/software/libc/manual/html_node/Porting.html">port</a> <a
-href="http://www.gnu.org/software/libc/">glibc</a> to LLVM.  This would allow a
-variety of interprocedural algorithms to be much more effective in the face of
-library calls.  The most important pieces to port are things like the string
-library and the <tt>stdio</tt> related functions... low-level system calls like
-'<tt>read</tt>' should stay unimplemented in LLVM.</p>
+<p>
+The <a href="docs/TestingGuide.html#wholeprograms">llvm-test</a> testsuite is
+a large collection of programs we use for nightly testing of generated code
+performance, compile times, correctness, etc.  Having a large testsuite gives
+us a lot of coverage of programs and enables us to spot and improve any
+problem areas in the compiler.</p>
+
+<p>
+One extremely useful task, which does not require in-depth knowledge of 
+compilers, would be to extend our testsuite to include <a href=
+"http://nondot.org/sabre/LLVMNotes/#benchmarks">new programs and benchmarks</a>.
+In particular, we are interested in cpu-intensive programs that have few
+library dependencies, produce some output that can be used for correctness
+testing, and that are redistributable in source form.  Many different programs 
+are suitable, for example, see <a 
+href="http://nondot.org/sabre/LLVMNotes/#benchmarks">this list</a> for some
+potential candidates.
+</p>
 
 </div>
 
@@ -365,7 +376,7 @@
   src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
 
   <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
-  Last modified: $Date: 2006/04/12 04:18:36 $
+  Last modified: $Date: 2006/05/10 03:53:37 $
 </address>
 
 <!--#include virtual="footer.incl" -->