1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
5 <title>Open LLVM Projects</title>
6 <link rel="stylesheet" href="llvm.css" type="text/css">
10 <div class="doc_title">
15 <li><a href="#what">What is this?</a></li>
16 <li><a href="#improving">Improving the current system</a>
18 <li><a href="#glibc">Port glibc to LLVM</a></li>
19 <li><a href="#NightlyTest">Improving the Nightly Tester</a></li>
20 <li><a href="#programs">Compile programs with the LLVM Compiler</a></li>
21 <li><a href="#llvm_ir">Extend the LLVM intermediate representation</a></li>
22 <li><a href="#misc_imp">Miscellaneous Improvements</a></li>
25 <li><a href="#new">Adding new capabilities to LLVM</a>
27 <li><a href="#pointeranalysis">Pointer and Alias Analysis</a></li>
28 <li><a href="#profileguided">Profile Guided Optimization</a></li>
29 <li><a href="#xforms">New Transformations and Analyses</a></li>
30 <li><a href="#x86be">X86 Back-end Improvements</a></li>
31 <li><a href="#misc_new">Miscellaneous Additions</a></li>
35 <!-- *********************************************************************** -->
36 <div class="doc_section">
37 <a name="what">What is this?</a>
39 <!-- *********************************************************************** -->
41 <div class="doc_text">
43 <p>This document is meant to be a sort of "big TODO list" for LLVM. Each
44 project in this document is something that would be useful for LLVM to have, and
45 would also be a great way to get familiar with the system. Some of these
46 projects are small and self-contained, which may be implemented in a couple of
47 days, others are larger. Several of these projects may lead to interesting
48 research projects in their own right. In any case, we welcome all
51 <p>If you are thinking about tackling one of these projects, please send a mail
52 to the <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev">LLVM
53 Developer's</a> mailing list, so that we know the project is being worked on.
54 Additionally this is a good way to get more information about a specific project
55 or to suggest other projects to add to this page. Another good place to look
56 for ideas is the <a href="http://llvm.cs.uiuc.edu/bugs/">LLVM bug
61 <!-- *********************************************************************** -->
62 <div class="doc_section">
63 <a name="improving">Improving the current system</a>
65 <!-- *********************************************************************** -->
67 <div class="doc_text">
69 <p>Improvements to the current infrastructure are always very welcome and tend
70 to be fairly straight-forward to implement. Here are some of the key areas that
71 can use improvement...</p>
75 <!-- ======================================================================= -->
76 <div class="doc_subsection">
77 <a name="glibc">Port glibc to LLVM</a>
80 <div class="doc_text">
82 <p>It would be very useful to <a
83 href="http://www.gnu.org/software/libc/porting.html">port</a> <a
84 href="http://www.gnu.org/software/glibc/">glibc</a> to LLVM. This would allow a
85 variety of interprocedural algorithms to be much more effective in the face of
86 library calls. The most important pieces to port are things like the string
87 library and the <tt>stdio</tt> related functions... low-level system calls like
88 '<tt>read</tt>' should stay unimplemented in LLVM.</p>
92 <!-- ======================================================================= -->
93 <div class="doc_subsection">
94 <a name="NightlyTest">Improving the Nightly Tester</a>
97 <div class="doc_text">
99 <p>The <a href="/testresults/">Nightly Tester</a> is a simple perl script
100 (located in <tt>utils/NightlyTest.pl</tt>) which runs every night to generate a
101 daily report. It could use the following improvements:</p>
104 <li>Graphs - It would be great to have gnuplot graphs to keep track of how the
105 tree is changing over time. We already gather a several statistics, it
106 just necessary to add the script-fu to gnuplotize it.</li>
108 <li>Regression tests - We should run the regression tests in addition to the
109 program tests...</li>
114 <!-- ======================================================================= -->
115 <div class="doc_subsection">
116 <a name="programs">Compile programs with the LLVM Compiler</a>
119 <div class="doc_text">
121 <p>We are always looking for new testcases and benchmarks for use with LLVM. In
122 particular, it is useful to try compiling your favorite C source code with LLVM.
123 If it doesn't compile, try to figure out why or report it to the <a
124 href="http://mail.cs.uiuc.edu/pipermail/llvmbugs/">llvm-bugs</a> list. If you
125 get the program to compile, it would be extremely useful to convert the build
126 system to be compatible with the LLVM Programs testsuite so that we can check it
127 into CVS and the automated tester can use it to track progress of the
130 <p>When testing a code, try running it with a variety of optimizations, and with
131 all the back-ends: CBE, llc, and lli.</p>
135 <!-- ======================================================================= -->
136 <div class="doc_subsection">
137 <a name="llvm_ir">Extend the LLVM intermediate representation</a>
140 <div class="doc_text">
144 <li>Add a new conditional move instruction: <tt>X = select bool Cond, Y,
147 <li>Add support for platform-independent prefetch support. The GCC <a
148 href="http://gcc.gnu.org/projects/prefetch.html">prefetch project</a> page
149 has a good survey of the prefetching capabilities of a variety of modern
156 <!-- ======================================================================= -->
157 <div class="doc_subsection">
158 <a name="misc_imp">Miscellaneous Improvements</a>
161 <div class="doc_text">
164 <li>Someone needs to look into getting the <tt>ranlib</tt> tool to index LLVM
165 bytecode files, so that linking in .a files is not hideously slow. They
166 would also then have to implement the reader for this index in
169 <li>Improve the efficiency of the bytecode loader/writer</li>
171 <li>Extend the FunctionPassManager to use a ModuleProvider to stream functions
172 in on demand. This would improve the efficiency of the JIT.</li>
174 <li>Rework the PassManager to be more flexible</li>
176 <li>Some transformations and analyses only work on reducible flow graphs. It
177 would be nice to have a transformation which could be "required" by these passes
178 which makes irreducible graphs reducible. This can easily be accomplished
179 through code duplication. See <a
180 href="http://citeseer.nj.nec.com/janssen97making.html">Making Graphs Reducible
181 with Controlled Node Splitting</a> and perhaps <a
182 href="http://doi.acm.org/10.1145/262004.262005">Nesting of Reducible and
183 Irreducible Loops</a>.</li>
189 <!-- *********************************************************************** -->
190 <div class="doc_section">
191 <a name="new">Adding new capabilities to LLVM</a>
193 <!-- *********************************************************************** -->
195 <div class="doc_text">
197 <p>Sometimes creating new things is more fun that improving existing things.
198 These projects tend to be more involved and perhaps require more work, but can
199 also be very rewarding.</p>
203 <!-- ======================================================================= -->
204 <div class="doc_subsection">
205 <a name="pointeranalysis">Pointer and Alias Analysis</a>
208 <div class="doc_text">
210 <p>We have a <a href="AliasAnalysis.html">strong base for development</a> of
211 both pointer analysis based optimizations as well as pointer analyses
212 themselves. It seems natural to want to take advantage of this...</p>
215 <li>Implement a flow-sensitive context-sensitive alias analysis algorithm<br>
216 - Pick one of the somewhat efficient algorithms, but strive for maximum
219 <li>Implement a flow-sensitive context-insensitive alias analysis algorithm<br>
220 - Just an efficient local algorithm perhaps?</li>
222 <li>Implement an interface to update analyses in response to common code motion
225 <li>Implement alias-analysis-based optimizations:
227 <li>Dead store elimination</li>
234 <!-- ======================================================================= -->
235 <div class="doc_subsection">
236 <a name="profileguided">Profile Guided Optimization</a>
239 <div class="doc_text">
241 <p>We are getting to the point where we really need a unified infrastructure for
242 profile guided optimizations. It would be wonderful to be able to write profile
243 guided transformations which can be performed either at static compile time
244 (compile time or offline optimization time) or at runtime in a JIT type setup.
245 The LLVM transformation itself shouldn't need to know how it is being used.</p>
247 <p>Ideas for profile guided transformations:</p>
250 <li>Superblock formation (with many optimizations)</li>
251 <li>Loop unrolling/peeling</li>
252 <li>Profile directed inlining</li>
259 <!-- ======================================================================= -->
260 <div class="doc_subsection">
261 <a name="xforms">New Transformations and Analyses</a>
264 <div class="doc_text">
267 <li>Implement a Dependence Analysis Infrastructure<br>
268 - Design some way to represent and query dep analysis</li>
269 <li>Implement a faster Dominator Set Construction Algorithm<br>
270 - A linear time or nearly so algorithm</li>
271 <li>Implement a strength reduction pass</li>
272 <li>Value range propagation pass</li>
273 <li>Implement an unswitching pass</li>
274 <li>Write a loop unroller, with a simple heuristic for when to unroll</li>
279 <!-- ======================================================================= -->
280 <div class="doc_section">
281 <a name="x86be">X86 Back-end Improvements</a>
284 <div class="doc_text">
287 <li>Implement a global register allocator</li>
288 <li>Implement a better instruction selector</li>
289 <li>Implement support for the "switch" instruction without requiring the
290 lower-switches pass.</li>
295 <!-- ======================================================================= -->
296 <div class="doc_subsection">
297 <a name="misc_new">Miscellaneous Additions</a>
300 <div class="doc_text">
303 <li>Write a new frontend for some language (Java? OCaml? Forth?)</li>
304 <li>Write a new backend for a target (IA64? MIPS? MMIX?)</li>
309 <!-- *********************************************************************** -->
312 <div class="doc_footer">
313 <address><a href="mailto:sabre@nondot.org">Chris Lattner</a></address>
314 <a href="http://llvm.cs.uiuc.edu">The LLVM Compiler Infrastructure</a>
316 Last modified: $Date$