[llvm-dev] Pool allocator + safecode

John Criswell via llvm-dev llvm-dev at lists.llvm.org
Thu Oct 1 08:51:22 PDT 2015

Dear Ed,

First, someone has updated the DSA code in the poolalloc project to LLVM 
3.7, and a Master's student worked for me over the summer to update a 
large chunk of SAFECode to LLVM 3.7.  However, the update to LLVM 3.7 
isn't finished (we need to finish integrating SAFECode back into Clang), 
and my student has opted to focus on his studies instead of finishing 
the update, so the current status of SAFECode for LLVM 3.7 is that it's 
nearly done but suspended.

If you want the currently updated code, you can get it at 

Second, if you need the pool allocation transform, then I must sadly 
disappoint.  The Automatic Pool Allocation (APA) transformation has 
suffered bit-rot over the years, and we've stopped using it.  We haven't 
updated it to work with LLVM 3.7 and currently have no plans to do so.

The code is still publicly available, so if you are sufficiently 
motivated, you can update it and fix it if you would like.

Just out of curiosity, what are you trying to accomplish? Depending on 
what you need, there may be simpler approaches that will require less 
engineering effort.


John Criswell

On 10/1/15 10:51 AM, Ed Robbins via llvm-dev wrote:
> Hi,
> I'm trying to get the pool allocator and safe code building against llvm
> trunk. I've run into a build error, and I see that in the past another
> user was told just not to build the pool allocator for use with safecode
> [1]. However, I really want the pool allocator transforms, so I just
> wanted to check why the suggestion was not to use it. Has it been
> superseded in some way by something else? Or is it just broken at the
> moment? I'll assume the latter for now and see if I can fix it...
> Cheers
> [1] http://lists.llvm.org/pipermail/llvm-dev/2015-July/088739.html

John Criswell
Assistant Professor
Department of Computer Science, University of Rochester

More information about the llvm-dev mailing list