similar to: [LLVMdev] llvm-poolalloc DSA patch: code cleanups and thread safety

On Jun 29, 2010, at 9:59 AM, Will Dietz wrote: > Hi all, > > While working on a loadable Alias Analysis module pass, I'm running > into the following issue: > > I'm finding my pass queried for results after it has had > 'releaseMemory' called on it and its dependencies, but before > runOnModule is called again (on my pass or its deps). As you might >

Hi all, While working on a loadable Alias Analysis module pass, I'm running into the following issue: I'm finding my pass queried for results after it has had 'releaseMemory' called on it and its dependencies, but before runOnModule is called again (on my pass or its deps). As you might expect, this makes my pass rather unhappy (and I think correctly so). This happens with LICM

Hi, I compiled the poolalloc from SVN head. opt complains about missing symbol PoolAlloc::ID when I try to load libpoolalloc.so. Defining PoolAlloc::ID is not enough, since it is reused in PoolAllocPassAllPools. The append patch fixes the problem for me. Kind regards, Martin Index: include/poolalloc/PoolAllocate.h ===================================================================

Kevin Streit wrote: > Hi all, > > is there any plan when poolalloc and DSA will be adapted to compile and run with LLVM 2.7? I'm currently about to start a bigger project using DSA and it would be nice if I could use LLVM 2.7 instead of porting everything I do now from 2.6 to 2.7 later. > Mainline DSA/Poolalloc already compiles with LLVM 2.7. I will probably create a

Hi all, is there any plan when poolalloc and DSA will be adapted to compile and run with LLVM 2.7? I'm currently about to start a bigger project using DSA and it would be nice if I could use LLVM 2.7 instead of porting everything I do now from 2.6 to 2.7 later. Cheers, Kevin -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type:

Ryan M. Lefever wrote: > I have a few questions on using dsa now that it has been moved out of > llvm. I have llvm -r release_19 checked out from cvs, and > llvm-poolalloc -r release_19 checked out from cvs into the projects > directory, as John Criswell previously suggested. > > 1) I have some compiler transforms that I'm writing that use DSA. They > can no longer

On Feb 13, 2007, at 11:08 AM, John T. Criswell wrote: > there is a difference between RELEASE_19 and release_19. I have not tried, but I won't be surprised if CVS itself gets confused between this two on systems like Darwin which is case insensitive but case preserving. - Devang -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have a few questions on using dsa now that it has been moved out of llvm. I have llvm -r release_19 checked out from cvs, and llvm-poolalloc -r release_19 checked out from cvs into the projects directory, as John Criswell previously suggested. 1) I have some compiler transforms that I'm writing that use DSA. They can no longer find the header files for DSA. My transforms are located

On 12/6/12 4:47 PM, Zvonimir Rakamaric wrote: > Hi all, > > I've been using LLVM in my software analysis projects for quite a few > years now, and several years back I relied on results of DSA analysis > in my SMACK tool for checking C programs. > > At some point that part of SMACK got deprecated, but now I would like > to revisit it since it was working quite well.

Hi all, I've been using LLVM in my software analysis projects for quite a few years now, and several years back I relied on results of DSA analysis in my SMACK tool for checking C programs. At some point that part of SMACK got deprecated, but now I would like to revisit it since it was working quite well. Therefore, I would like to learn what's the status of the poolalloc project, and

Hello, I am trying to apply DSA (from the poolalloc project - I'm on LLVM 3.2) on the following C program and found that the generated callgraph over-approximates the callees for the simple indirect call. #include <stdio.h> __attribute__((noinline)) static int f1(int arg1, int arg2) { return arg1 + arg2; } __attribute__((noinline)) static int run_func(int (*fptr)(int, int), int

Tanya M. Lattner wrote: >>I recommend that you stick with the release_19 branch of both llvm and >>llvm-poolalloc. I and others are actively using these branches, so >>llvm-poolalloc bug fixes will most likely be made to this branch in >>addition to mainline CVS for the forseeable future. The release_19 >>branch of llvm-poolalloc is designed to always work with the

> I recommend that you stick with the release_19 branch of both llvm and > llvm-poolalloc. I and others are actively using these branches, so > llvm-poolalloc bug fixes will most likely be made to this branch in > addition to mainline CVS for the forseeable future. The release_19 > branch of llvm-poolalloc is designed to always work with the release_19 > branch of LLVM, which

Hi, LLVM dev team: Thanks for your suggestion, I have done the experiment to compare the two pointer analysis(Andersen and Steensgaard) methods in LLVM, but the result was unexpected. In each test, I compare these two methods using same optimization; There are several tests, each with a different optimization. The benchmark is all the 11 C programs in CINT2000 of SPEC. In all the tests, I found

Hi Daniel, To my knowledge, there is no other implementation available for Steensgaard AA except poolalloc. I have tried Steensgaard AA under LLVM 2.7 poolalloc, but there are lots of bugs which need to be fixed. It will be a good idea to use previous implementation, but you will have to modify (a lot) it with respect to the latest version of LLVM poolalloc. Thanks, -Yogesh -------------- next

Hi, LLVM dev team: Thanks for your suggestion, I have done the experiment to compare the two pointer analysis(Andersen and Steensgaard) methods in LLVM, but the result was unexpected. In each test, I compare these two methods using same optimization; There are several tests, each with a different optimization. The benchmark is all the 11 C programs in CINT2000 of SPEC. In all the tests, I found

Thanks guys! I was looking into ModRef before, but I don't think that's exactly what I need. ModRef API call getModRefInfo requires a Value to be passed to it. However, some memory location M (which is a <DSNode, offset> pair) visible to the caller can be modified in the callee without any Value in the caller actually pointing to that location. I also need to capture those... I

聪明陈 wrote: > Hi LLVM dev team: > I am now doing an experiment to comparing Steensgaard-style and > Andersen-style pointer analysis on LLVM. Since steensgaard pointer > analysis is in module "poolalloc", so I installed poolalloc release > 2.6 on my machine(intel X86_64 RedHatEnterpriseLinux 5.1, gcc-4.2.4), > two directories "include" and "lib" were

Hi LLVM dev team: I am now doing an experiment to comparing Steensgaard-style and Andersen-style pointer analysis on LLVM. Since steensgaard pointer analysis is in module "poolalloc", so I installed poolalloc release 2.6 on my machine(intel X86_64 RedHatEnterpriseLinux 5.1, gcc-4.2.4), two directories "include" and "lib" were created after installation but no

Hi, I ran into a problem when running DSA on Linux kernel (the Kernel version I used is 2.4.31). The analysis was aborted when it tried to do DSNode::mergeTypeInfo on some data structure in the kernel. I have filed a bug report at http://llvm.org/bugs/show_bug.cgi?id=1656. My question is what version of Linux kernel LLVM has been tested on successfully? To run DSA analysis, should I use the