| -What is this? - |
+
This document is meant to be a sort of "big TODO list" for LLVM. Each +project in this document is something that would be useful for LLVM to have, and +would also be a great way to get familiar with the system. Some of these +projects are small and self-contained, which may be implemented in a couple of +days, others are larger. Several of these projects may lead to interesting +research projects in their own right. In any case, we welcome all +contributions.
-If you are thinking about tackling one of these projects, please send a mail to -the LLVM +If you are thinking about tackling one of these projects, please send a mail +to the LLVM Developer's 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.
+or to suggest other projects to add to this page. Another good place to look +for ideas is the LLVM bug +tracker.
+| -Improving the current system - |
+
Improvements to the current infrastructure are always very welcome and tend +to be fairly straight-forward to implement. Here are some of the key areas that +can use improvement...
+ +| - -Port glibc to LLVM - |
It would be very useful to port glibc 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 stdio related functions... low-level system calls like -'read' should stay unimplemented in LLVM.
+'read' should stay unimplemented in LLVM.
+ -| - -Improving the Nightly Tester - |
+
The Nightly Tester is a simple perl script +(located in utils/NightlyTest.pl) which runs every night to generate a +daily report. It could use the following improvements:
++ program tests...
| - -Compile programs with the LLVM Compiler - |
We are always looking for new testcases and benchmarks for use with LLVM. In particular, it is useful to try compiling your favorite C source code with LLVM. If it doesn't compile, try to figure out why or report it to the llvm-bugs list. If you get the program to compile, it would be extremely useful to convert the build system to be compatible with the LLVM Programs testsuite so that we can check it into CVS and the automated tester can use it to track progress of the -compiler.
+compiler.
-When testing a code, try running it with a variety of optimizations, and with -all the back-ends: CBE, llc, and lli.+
When testing a code, try running it with a variety of optimizations, and with +all the back-ends: CBE, llc, and lli.
+| - -Extend the LLVM intermediate representation - |
| - -Miscellaneous Improvements - |
| -Adding new capabilities to LLVM - |
+
Sometimes creating new things is more fun that improving existing things. +These projects tend to be more involved and perhaps require more work, but can +also be very rewarding.
+ +| - -Pointer and Alias Analysis - |
+
We have a strong base for development of +both pointer analysis based optimizations as well as pointer analyses +themselves. It seems natural to want to take advantage of this...
- Change: -
- store int X, int* P - Y = load int* P- into: -
- store int X, int *P - Y = X-
| - -Profile Guided Optimization - |
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.
+The LLVM transformation itself shouldn't need to know how it is being used.
-Ideas for profile guided transformations:+
Ideas for profile guided transformations:
+
| - -New Transformations and Analyses - |
| - -X86 Back-end Improvements - |
| - -Miscellaneous Additions - |