similar to: [LLVMdev] SAFECode and Poolalloc Branches for LLVM 2.6

On Mar 6, 2010, at 7:26 AM, Patrick Sathyanathan wrote: > Hi, > > I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything related to pool allocation. I don't think

Bob Wilson wrote: > On Mar 6, 2010, at 7:26 AM, Patrick Sathyanathan wrote: > > >> Hi, >> >> I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything

Thanks Bob and John for the response. I am having problems building poolalloc with my MinGW and gcc 4.4.0 setup. Running make in the poolalloc directory results in a bunch of "undefined reference to ..." link errors building Release/lib/LLVMDataStructure.dll. I looked at the command line for this link and found that there are no libraries included with "-l..." options even

Dear SAFECoders and LLVMers, There is some new work on moving DSA to the new LLVM 2.7 API. I am hoping to do something similar for SAFECode once the code freeze occurs. To keep things running smoothly, there are now release_26 branches for the poolalloc and safecode projects. If you are using SAFECode, Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches. To get

Hi, I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything related to pool allocation. I don't think MinGW includes svn. Is there an download location where I can get the

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

I suggest you stick to John's release_26 branch of poolalloc for now. 2.7 breaks poolalloc, and dsa is undergoing some changes. Andrew On Tue, Mar 9, 2010 at 11:13 AM, John Criswell <criswell at uiuc.edu> wrote: > Dear Patrick and Antron, > > I've modified the Makefiles in the poolalloc module so that they do not > build shared libraries on MingW or Cygwin.  Patrick, if

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"

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

Hello, I am trying to build llvm-poolalloc and safecode under current trunk llvm. After building llvm, I cannot build poolalloc. I got following error message: make[1]: Entering directory `/host/llvm/projects/llvm-poolalloc/lib' make[2]: Entering directory `/host/llvm/projects/llvm-poolalloc/lib/DSA' llvm[2]: Compiling AddressTakenAnalysis.cpp for Debug+Asserts build (PIC)

Hi John, That worked for me. I am using llvm 3.2 only and following http://safecode.cs.illinois.edu/docs/Install.html So for I am able to make inside llvm/projects/poolalloc by doing such cosmetic changes. Now, when I tried to make inside llvm/projects/safecode, I see another error. kpawar at KPAWAR-LT ~/SAFECode/LLVM_SRC/llvm/projects/safecode $ /usr/bin/clang -cc1 -triple

Hi, On Linux I observed [root at localhost poolalloc]# find . -name *.a ./Release+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT

John, The release source code (sc-main.tar) won't compile cleanly under Debian6-i386 (gcc/g++: 4.4.5). The compiler back trace is attached. Please fix it/them and repost. Or, 64b system is a requirement? Thank you Chuck llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC) cc1plus: warnings being treated as errors

Hi, My apologies for the trouble. I've disabled building DynamicTypeChecks for now (r138224) and now it builds cleanly on 32bit for me here. As for SAFECode support for 32bit vs 64bit, I believe 32bit should work just fine although I haven't personally tested this. Let me know if you have any further issues/questions. ~Will On Sun, Aug 21, 2011 at 9:26 AM, Chuck Zhao <czhao at

Dear Qiuping, If you use the release_32 branch of poolalloc, then you need to use LLVM 3.2. For directions on compiling poolalloc with LLVM 3.2, please the SAFECode build directions at http://safecode.cs.illinois.edu/docs/Install.html. You can just skip the steps in the directions that compile SAFECode. Regards, John Criswell On 1/30/15 10:05 AM, Qiuping Yi wrote: > Hi, all > > I

On 1/30/15 11:32 PM, Qiuping Yi wrote: > Hi, John Criswell > > Thank you very much. > > I am installing LLVM-3.2, but I encounter the next error when carrying > out "make": Is this error occurring when compiling the version of Clang within SAFECode or standard Clang? If it's the former, you should know that you don't need to compile SAFECode to use

Thank you. But now I am using LLVM 2.9, so which version of poolalloc I should use ? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Fri, Jan 30, 2015 at 11:12 PM, John Criswell <jtcriswel at gmail.com> wrote: > Dear Qiuping, > > If you use the release_32 branch of poolalloc, then you need to use LLVM > 3.2. >

On 1/30/15 10:17 AM, Qiuping Yi wrote: > Thank you. But now I am using LLVM 2.9, so which version of > poolalloc I should use ? Why are you using LLVM 2.9? That's an old version of LLVM (even by my standards). Is there some other LLVM-based tool that requires that you use LLVM 2.9? Regards, John Criswell > > > -------------------------------------------- > Qiuping Yi

I am just not upgrade my LLVM. So I must use some higer LLVM version, right? -------------------------------------------- Qiuping Yi Institute Of Software Chinese Academy of Sciences On Fri, Jan 30, 2015 at 11:21 PM, John Criswell <jtcriswel at gmail.com> wrote: > On 1/30/15 10:17 AM, Qiuping Yi wrote: > > Thank you. But now I am using LLVM 2.9, so which version of poolalloc I

On 1/30/15 10:24 AM, Qiuping Yi wrote: > I am just not upgrade my LLVM. So I must use some higer LLVM version, > right? Yes. For working with poolalloc, I would recommend using LLVM 3.2 as we know poolalloc compiles with LLVM 3.2. If there's a release_29 branch for poolalloc, you could use that, but you won't get any bug fixes that we added between poolalloc 2.9 and poolalloc