X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FOpenProjects.html;h=5f648374d1a5539e5340adb6bfbc89b848a3314c;hb=0b4ffea8665025988a3a5da2106070de561adeb2;hp=b79c0aae92e18ae97abe03360d1aeaf43702c1f3;hpb=b71310982a1782f435e3836c8b9bdc489d4135e2;p=oota-llvm.git diff --git a/docs/OpenProjects.html b/docs/OpenProjects.html index b79c0aae92e..5f648374d1a 100644 --- a/docs/OpenProjects.html +++ b/docs/OpenProjects.html @@ -92,12 +92,13 @@ could use the following improvements:
+
@@ -111,7 +112,11 @@ 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.
+into CVS and the automated tester can use it to track progress of the
+compiler. + +When testing a code, try running it with a variety of optimizations, and with +all the back-ends: CBE, llc, and lli. @@ -122,12 +127,8 @@ into CVS and the automated tester can use it to track progress of the compiler. |
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:
-
- A linear time or nearly so algorithm
-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...
@@ -244,8 +238,8 @@ Ideas for profile guided transformations:
- Pick one of the somewhat efficient algorithms, but strive for maximum
precision
-
+
- Just an efficient local algorithm perhaps?
- store int X, int* P
- Y = load int* P
- into:
-
- store int X, int *P
- Y = X
-