<li><a href="#improving">Improving the current system</a>
<ol>
<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>
</ol></li>
</ul>
+<div class="doc_author">
+ <p>Written by the <a href="http://llvm.cs.uiuc.edu/">LLVM Team</a></p>
+</div>
+
+
<!-- *********************************************************************** -->
<div class="doc_section">
<a name="what">What is this?</a>
to the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM
Developer's</a> mailing list, so that we know the project is being worked on.
Additionally this is a good way to get more information about a specific project
-or to suggest other projects to add to this page. Another good place to look
-for ideas is the <a href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug
-tracker</a>.</p>
+or to suggest other projects to add to this page.
+</p>
+
+<p>The projects in this page are open-ended. More specific projects are
+filed as unassigned enhancements in the <a href="http://llvm.cs.uiuc.edu/bugs/">
+LLVM bug tracker</a>. See the <a href="http://llvm.cs.uiuc.edu/bugs/buglist.cgi?keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&emailassigned_to1=1&emailtype1=substring&email1=unassigned">list of currently outstanding issues</a> if you wish to help improve LLVM.</p>
</div>
</div>
-<!-- ======================================================================= -->
-<div class="doc_subsection">
- <a name="NightlyTest">Improving the Nightly Tester</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>
-
-</div>
-
<!-- ======================================================================= -->
<div class="doc_subsection">
<a name="programs">Compile programs with the LLVM Compiler</a>
<div class="doc_text">
<ol>
-
-<li>Add a new conditional move instruction: <tt>X = select bool Cond, Y,
- Z</tt></li>
-
<li>Add support for platform-independent prefetch support. The GCC <a
href="http://gcc.gnu.org/projects/prefetch.html">prefetch project</a> page
has a good survey of the prefetching capabilities of a variety of modern
<div class="doc_text">
-<p>Sometimes creating new things is more fun that improving existing things.
+<p>Sometimes creating new things is more fun than improving existing things.
These projects tend to be more involved and perhaps require more work, but can
also be very rewarding.</p>
<li>Implement a flow-sensitive context-insensitive alias analysis algorithm<br>
- Just an efficient local algorithm perhaps?</li>
-<li>Implement an interface to update analyses in response to common code motion
- transformations</li>
-
<li>Implement alias-analysis-based optimizations:
<ul>
<li>Dead store elimination</li>
<div class="doc_text">
-<p>We are getting to the point where we really need a unified infrastructure for
-profile guided optimizations. It would be wonderful to be able to write profile
-guided transformations which can be performed either at static compile time
-(compile time or offline optimization time) or at runtime in a JIT type setup.
-The LLVM transformation itself shouldn't need to know how it is being used.</p>
+<p>We now have a unified infrastructure for writing profile-guided
+transformations, which will work either at offline-compile-time or in the JIT,
+but we don't have many transformations. We would welcome new profile-guided
+transformations as well as improvements to the current profiling system.
+</p>
<p>Ideas for profile guided transformations:</p>
<li>...</li>
</ol>
+<p>Improvements to the existing support:</p>
+
+<ol>
+<li>The current block and edge profiling code that gets inserted is very simple
+and inefficient. Through the use of control-dependence information, many fewer
+counters could be inserted into the code. Also, if the execution count of a
+loop is known to be a compile-time or runtime constant, all of the counters in
+the loop could be avoided.</li>
+
+<li>You could implement one of the "static profiling" algorithms which analyze a
+piece of code an make educated guesses about the relative execution frequencies
+of various parts of the code.</li>
+
+<li>You could add path profiling support, or adapt the existing LLVM path
+profiling code to work with the generic profiling interfaces.</li>
+</ol>
+
</div>
<!-- ======================================================================= -->
- Design some way to represent and query dep analysis</li>
<li>Implement a strength reduction pass</li>
<li>Value range propagation pass</li>
-<li>Implement an unswitching pass</li>
-<li>Write a loop unroller, with a simple heuristic for when to unroll</li>
</ol>
</div>
<div class="doc_text">
<ol>
-<li>Implement a global register allocator</li>
<li>Implement a better instruction selector</li>
<li>Implement support for the "switch" instruction without requiring the
lower-switches pass.</li>
</div>
<!-- ======================================================================= -->
-<div class="doc_subsection">
+<div class="doc_section">
<a name="misc_new">Miscellaneous Additions</a>
</div>
<div class="doc_text">
<ol>
-<li>Write a new frontend for some language (Java? OCaml? Forth?)</li>
+<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 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
+<tt>MachineInstr</tt>s for transformations, optimizations, etc.</li>
+<li>Random test vector generator: Use a C grammar to generate random C code;
+run it through llvm-gcc, then run a random set of passes on it using opt.
+Try to crash opt. When opt crashes, use bugpoint to reduce the test case and
+mail the result to yourself. Repeat ad infinitum.</li>
+<li>Design a simple, recognizable logo.</li>
</ol>
</div>
<!-- *********************************************************************** -->
<hr>
-<div class="doc_footer">
- <address><a href="mailto:sabre@nondot.org">Chris Lattner</a></address>
- <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
- <br>
+<address>
+ <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
+ src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
+ <a href="http://validator.w3.org/check/referer"><img
+ src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!"></a>
+
+ <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
+ <a href="http://llvm.cs.uiuc.edu">LLVM Compiler Infrastructure</a><br>
Last modified: $Date$
-</div>
+</address>
</body>
</html>
projects / oota-llvm.git / blobdiff