Svadev mailing list

[Daniel Huang <dehuang AT fas.harvard.edu>]

Ok thanks. Also, I can't get poolalloc release_27 to compile. According to the README, it is broken for LLVM 2.7. I'm wondering if this is indeed the case and should revert to release_26.

On Tue, May 15, 2012 at 1:10 AM, John Criswell <criswell AT illinois.edu> wrote:

On 5/14/12 8:19 PM, Daniel Huang wrote:

Hi SVAdev,

What is the most recent version of Safecode that has pool allocation and type-safety optimizations turned on?

I believe the last version was LLVM 2.7.  If you check out the release_27 branches of LLVM, SAFECode, and Poolalloc, you should get it.

However, the SAFECode integration with clang wasn't done for LLVM 2.7.  If you want to use SAFECode with LLVM 2.7, you'll have to link the entire program into a single bitcode file and run the sc tool on it (check the docs directory for information on the sc tool).

Also, when do you expect the most recent version to have those turned on.

The type-safety optimization could probably be turned on now since it won't break correct programs.  It won't be sound without poolalloc or garbage collection, but for debug mode, people probably won't care.

We have not made any plans yet on when we'll be working on poolalloc.  There are other optimizations which are easier to make robust that should help SAFECode's performance; this (and other obligations) are why poolalloc hasn't been worked on in awhile.

Since you need poolalloc for your work, I think what we can do is to try running it within libLTO at a higher optimization level so that it doesn't affect the average SAFECode user but is available for you (and other adventerous souls) to use.  I can try to look at that later this week or next week.

-- John T.

Regards,

Dan

_______________________________________________
svadev mailing list
svadev AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/svadev