<li><a href="#what">What is this?</a></li>
<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="#NightlyTest">Improving the Nightly Tester</a></li>
<li><a href="#programs">Compile programs with the LLVM Compiler</a></li>
<li><a href="#llvm_ir">Extend the LLVM intermediate representation</a></li>
<li><a href="#misc_imp">Miscellaneous Improvements</a></li>
<li><a href="#new">Adding new capabilities to LLVM</a>
<ol>
+ <li><a href="#newfeaturebugs">Implementing new feature PRs</a></li>
<li><a href="#pointeranalysis">Pointer and Alias Analysis</a></li>
<li><a href="#profileguided">Profile Guided Optimization</a></li>
<li><a href="#xforms">New Transformations and Analyses</a></li>
<!-- ======================================================================= -->
<div class="doc_subsection">
- <a name="glibc">Port glibc to LLVM</a>
+ <a name="code-cleanups">Implementing Code Cleanup bugs</a>
</div>
<div class="doc_text">
-<p>It would be very useful to <a
-href="http://www.gnu.org/software/libc/porting.html">port</a> <a
-href="http://www.gnu.org/software/glibc/">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="http://llvm.cs.uiuc.edu/bugs/">LLVM bug tracker</a> occasionally
+has <a href="http://llvm.cs.uiuc.edu/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=code-cleanup&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=">"code-cleanup" bugs</a> filed in it. Taking one of these and fixing it is a good
+way to get your feet wet in the LLVM code and discover how some of its components
+work.
+</p>
</div>
<!-- ======================================================================= -->
<div class="doc_subsection">
- <a name="NightlyTest">Improving the Nightly Tester</a>
+ <a name="glibc">Port glibc to LLVM</a>
</div>
<div class="doc_text">
-<p>The <a href="/testresults/">Nightly Tester</a> is a simple perl script
-(located in <tt>utils/NightlyTest.pl</tt>) which runs every night to generate a
-daily report. It could use the following improvements:</p>
-
-<ol>
-<li>Regression tests - We should run the regression tests in addition to the
- program tests...</li>
-</ol>
+<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>
</div>
</div>
+
+<!-- ======================================================================= -->
+<div class="doc_subsection">
+ <a name="newfeaturebugs">Implementing new feature PRs</a>
+</div>
+
+<div class="doc_text">
+
+<p>Many ideas for feature requests are stored in LLVM bugzilla. Just <a href="http://llvm.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=new-feature&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=All+PRs&newqueryname=&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=">search for bugs with a "new-feature" keyword</a>.</p>
+
+</div>
+
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="pointeranalysis">Pointer and Alias Analysis</a>
<li>Implement a better instruction selector</li>
<li>Implement support for the "switch" instruction without requiring the
lower-switches pass.</li>
+<li>Implement interprocedural register allocation. The CallGraphSCCPass can be
+ used to implement a bottom-up analysis that will determine the *actual*
+ registers clobbered by a function. Use the pass to fine tune register usage
+ in callers based on *actual* registers used by the callee.</li>
</ol>
</div>
<div class="doc_text">
<ol>
-<li>Port the <A HREF="http://www-sop.inria.fr/mimosa/fp/Bigloo/">Bigloo</A>
+<li>Port the <a href="http://www-sop.inria.fr/mimosa/fp/Bigloo/">Bigloo</A>
Scheme compiler, from Manuel Serrano at INRIA Sophia-Antipolis, to
output LLVM bytecode. It seems that it can already output .NET
bytecode, JVM bytecode, and C, so LLVM would ostensibly be another good
candidate.</li>
+<li>Write a new frontend for C/C++ <b>in</b> C++, giving us the ability to
+directly use LLVM C++ classes from within a compiler rather than use
+C-based wrapper functions a la llvm-gcc. One possible starting point is the <a
+href="http://www.parashift.com/c++-faq-lite/compiler-dependencies.html#faq-37.11">C++
+yacc grammar by Ed Willink</a>.</li>
<li>Write a new frontend for some other language (Java? OCaml? Forth?)</li>
<li>Write a new backend for a target (IA64? MIPS? MMIX?)</li>
<li>Write a disassembler for machine code that would use TableGen to output