Svadev mailing list

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

I added -DPOOLALLOC but still haven't been able to get any programs to emit poolalloc or poolinit instructions. Perhaps I misunderstood you, but I modified safecode's Makefile.common SC_FLAGS with -DPOOLALLOC.

Also, do you have an example program which will cause the tool to emit these instructions? I'm really curious to see where pools are created and destroyed. For example, can they be created in the middle of the function, or are they only ever created at the beginning of a function and destroyed at the end.

On Mon, May 21, 2012 at 10:41 AM, John Criswell <criswell AT illinois.edu> wrote:

On 5/19/12 11:11 AM, John Criswell wrote:

[snip]

I think fixing the runtime should be simple; I'll take a look into that early next week.  In the meantime, you might want to take APA for a spin on the programs you want to compile to see if it crashes.

I've fixed the SAFECode and Pool Allocator run-time libraries so that programs link.  Please try it out and let me know if you run into any problems.  I recommend working with toy programs first to see how well things are working; chances are good that automatic pool allocation, in its current form, will break larger programs.

-- John T.

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

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