John Criswell wrote:> Dear All, > > I have finished updating the DSA and Poolalloc source code so that it > compiles with the LLVM 2.6 API. If you check out the LLVM 2.6 branch > (directions are in the llvmdev archives; look for the email by Tanya > Lattner about the LLVM 2.6 branch), you should be able to build mainline > DSA and Pool Allocation against it. > > If you have trouble building DSA/Pool Allocation, please email llvmdev. >To aid in checking out LLVM 2.6, I went and looked up the command. It is: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_26 llvm -- John T.
John Criswell wrote:> John Criswell wrote: > >> Dear All, >> >> I have finished updating the DSA and Poolalloc source code so that it >> compiles with the LLVM 2.6 API. If you check out the LLVM 2.6 branch >> (directions are in the llvmdev archives; look for the email by Tanya >> Lattner about the LLVM 2.6 branch), you should be able to build mainline >> DSA and Pool Allocation against it. >> >> If you have trouble building DSA/Pool Allocation, please email llvmdev. >> >> > > To aid in checking out LLVM 2.6, I went and looked up the command. It is: > > svn co https://llvm.org/svn/llvm-project/llvm/branches/release_26 llvm > > -- John T. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >Does this mean poolalloc isn't meant to build with the LLVM trunk anymore? I recently updated both poolalloc and my LLVM checkout to the latest revision, and poolalloc isn't building (something about "Ostream" being undefined). Should I switch my checkout to the "release_26" branch? --Patrick -- If I'm not here, I've gone out to find myself. If I get back before I return, please keep me here.
Patrick Simmons wrote:> [snip] >> >> >> > Does this mean poolalloc isn't meant to build with the LLVM trunk > anymore? I recently updated both poolalloc and my LLVM checkout to the > latest revision, and poolalloc isn't building (something about "Ostream" > being undefined). Should I switch my checkout to the "release_26" branch? > > --Patrick > >That is correct. Mainline poolalloc will compile with the LLVM 2.6 branch instead of LLVM mainline for the foreseeable future. This is because 1) we want to make a "release" of poolalloc that works with LLVM 2.6 so that there is a poolalloc/SAFECode version that works with an LLVM release; and 2) I believe the LLVM API is changing again in mainline, and LLVM 2.6 seems like a good point at which to synchronize and stop. I think we'll create a release_26 branch for poolalloc in the future, but I'm not sure when. That is something we can discuss in the next few weeks. -- John T.