[llvm-commits] [poolalloc] r98061 - in /poolalloc/trunk: README lib/DSA/README

[alenhar2 at llvm.org]

Author: alenhar2
Date: Tue Mar  9 10:43:02 2010
New Revision: 98061

URL: http://llvm.org/viewvc/llvm-project?rev=98061&view=rev
Log:
Update readme with known issues

Added:
    poolalloc/trunk/lib/DSA/README
Modified:
    poolalloc/trunk/README

Modified: poolalloc/trunk/README
URL: http://llvm.org/viewvc/llvm-project/poolalloc/trunk/README?rev=98061&r1=98060&r2=98061&view=diff
==============================================================================
--- poolalloc/trunk/README (original)
+++ poolalloc/trunk/README Tue Mar  9 10:43:02 2010
@@ -5,6 +5,20 @@
 Before using the Automatic Pool Allocator, you should read the pre-release
 license in LICENSE.TXT.
 
+KNOWN ISSUES:
+=============
+
+Automatic Pool Allocation is currently broken on 2.7 due to malloc and
+free instructions being removed.  Use the release_26 branch of llvm
+and poolalloc for a working poolalloc module.
+
+DSA is undergoing significant changes and may not be entirely stable or 
+correct.  See lib/DSA/README.
+
+Windows does not support loadable modules in llvm, so poolalloc must
+be linked into opt.
+
+
 BUILDING:
 =========
 To build the Automatic Pool Allocator, you will need to have installed and

Added: poolalloc/trunk/lib/DSA/README
URL: http://llvm.org/viewvc/llvm-project/poolalloc/trunk/lib/DSA/README?rev=98061&view=auto
==============================================================================
--- poolalloc/trunk/lib/DSA/README (added)
+++ poolalloc/trunk/lib/DSA/README Tue Mar  9 10:43:02 2010
@@ -0,0 +1,15 @@
+DSA is changed since PLDI07 in (at least) the following ways:
+
+1) DSA tracks types per offset.
+2) DSA does not assume that all clients will want to collapse a node if types 
+   conflict.  Many clients don't care that an offset is used as an int or a 
+   double, they just care about the points-to result.
+
+In Progress:
+
+1) DSA handles multiple entry points in a module.
+2) Optional assumption that only legal targets are called at indirect call sites
+3) Positional arguments, rather than pointer relative arguments.  This handles
+   the case where pointer and ints are assumed compatible and function pointers
+   containing them are cast freely.
+