similar to: [LLVMdev] Status of poolalloc, and in particular DSA

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.

Thanks for your help John... Yup, I looked at Local.cpp even before I fired off my question to the mailing list. Take a peek here at line 464: https://github.com/llvm-mirror/poolalloc/blob/master/lib/DSA/Local.cpp Based on my understanding of this line, if AtomicCmpXchgInst does not return a pointer type, nothing gets merged. And in the example I posted, a pointer value is indeed not returned

Dear John, I intend to implement the improvements on DSA. After running DSA on SPEC, I found DSA gives low precision for mcf and bzip2. I have checked the most imprecise c files in mcf an found that the code seems to be a mixture of "PHI" and "GEP" instructions. Could you please give me some hints about what the big picture of the improvement should be and how to start? Thank

Thanks Bill! So should I email you again in 5 months? -- http://www.zvonimir.info On Wed, Feb 6, 2013 at 1:10 AM, Bill Wendling <wendling at apple.com> wrote: > Hi Zvonimir, > > We normally list projects that use LLVM when we do a release. The next release will be 3.3, which will probably start up in 5 months or so. > > -bw > > On Feb 3, 2013, at 9:16 PM, Zvonimir

Hi, So, SMACK is a software verifier based around LLVM, and you can find more info (PDF, title, abstract) about our recent publication here: http://soarlab.org/2014/05/smack-decoupling-source-language-details-from-verifier-implementations/ I would appreciate if you could add it to your list of LLVM-based publications. Thanks! Best, -- Zvonimir -- http://zvonimir.info http://soarlab.org/

Hi all, I have yet another DSA-related question :), and I would appreciate your help. Actually, the following example generates some interesting potential issues in the LLVM IR too. Here is the example in C: #define CAS(x,y,z) __atomic_compare_exchange_n(x,&(y),z,true,0,0) int main() { int *x = 0; int y = 0; int *z = x; CAS(&z,x,&y); // if (z == x) z = &y; assert(*z ==

On Feb 6, 2013, at 7:22 AM, "Criswell, John T" <criswell at illinois.edu> wrote: > Dear All, > > We can add a link to the SMACK project on the LLVM User's page at http://llvm.org/Users.html at any time. Bill, does your comment refer to the release notes, or something else? > Just to the release notes. At least, that's when we do blurbs. :) -bw > In any

Dear All, We can add a link to the SMACK project on the LLVM User's page at http://llvm.org/Users.html at any time. Bill, does your comment refer to the release notes, or something else? In any event, if the SMACK project has a web site, I can add the URL to the User's page. Is the Github URL what you want to use, or is there a web page with more information that we should link to

Hi guys, So, I've been a long-term user of LLVM, and currently me and my students are actively using LLVM in several projects of ours. At this point, I would greatly appreciate if you could add SMACK static checker, which relies on LLVM, to the list of LLVM projects. SMACK is an open-source static checker built on top of LLVM, and we are hoping to get more collaborators and contributors this

Hi, Our tool SMACK (https://github.com/smackers/smack/) relies on installing LLMV from APT packages that used to be provided here: http://llvm.org/apt/ This link has been down for several weeks at this point (I think). Do you have a rough estimate for when you will bring this back? Our users are having trouble installing SMACK due to the above problem, and so I am wondering if we should look

Hi Zvonimir, We normally list projects that use LLVM when we do a release. The next release will be 3.3, which will probably start up in 5 months or so. -bw On Feb 3, 2013, at 9:16 PM, Zvonimir Rakamaric <zvonimir at cs.utah.edu> wrote: > Hi guys, > > So, I've been a long-term user of LLVM, and currently me and my > students are actively using LLVM in several projects of

Dear all, I am trying to reproduce the "Percent May Alias" result described in PLDI 07's paper "Making Context-Sensitive Points-to Analysis with Heap Cloning Practical For The Real World" (http://llvm.org/pubs/2007-06-10-PLDI-DSA.html ). However, my "Percent May Alias" for all the benchmarks is much greater, especially "bzip2". The DSA code I use is

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

Hi, We recently published another paper that leverages LLVM (through our SMACK software verifier and novel tool called Whoop), and this time we focus on detecting concurrency bugs in device drivers: http://soarlab.org/2015/08/ase2015-ddr/ You can find all the required info (PDF, title, abstract, etc.) at the above webpage. I would appreciate if you could add this paper to your list of

Hi, all I want to use the alias analysises in project poolalloc, but I encounter some problem during installing it. I install poolalloc as follow: 1) cd llvm/projects svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_32 poolalloc 3) cd LLVM-object-directory make tools-only cd projects/poolalloc make When I carried out "make", I get the next error

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. >

Greeting. I am working on one DSA related project. Got several questions about LLVM's DSA analysis: 1. I looked through the llvm doc, it seems "-ds-aa" option is the one I should use. (http://llvm.org/docs/AliasAnalysis.html#the-ds-aa-pass). however based on the poolalloc's svn history, this option was removed on (or before) 2011. May I know why this one was removed ? and is

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

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

Hi , This Is 'Suresh M' from AMD compiler team. 1) I obtained the source code of llvm and pool-alloc (relase_32 versions ) using the following commands, svn co http://llvm.org/svn/llvm-project/llvm/branches/release_32 llvm cd llvm/projects svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_32 poolalloc 2) Was able to build the binaries and libraries