Svadev mailing list

[John Criswell <criswell AT illinois.edu>]

Dear All,

After some discussion, we've decided to bite the bullet and start moving 
SAFECode to LLVM mainline.  This is to permit a GSoC student to try 
SAFECode with the common memory-safety infrastructure that he's been 
developing as well as to gain better C++ support from Clang.

I'll be creating release_30 branches of poolalloc and safecode this 
afternoon and updating the Install Guides to direct users to use the 
branch.  Work will then commence on updating SAFECode to compile and 
work with mainline SAFECode.

Baozeng, I realize this creates a complication with the Baggy Bounds 
Checking work that you're doing.  If you want, I think you can continue 
working on the release_30 branch until the update to mainline is done; 
merging your changes back into mainline should be easy.

-- John T.