similar to: [LLVMdev] Mapping Local DSA Nodes to their callers

Okay, are C standard library functions typically external in a fully linked LLVM bytecode file? --Patrick Andrew Lenharth wrote: > If the function is external, then DSA won't create a graph for it. > > Andrew > > On Mon, Jul 13, 2009 at 4:54 PM, Patrick Alexander > Simmons<simmon12 at cs.uiuc.edu> wrote: > >> I'm noticing that DSA graphs are not

What is this used for? Does DSA put anything here? If I want to add call sites here during my pass, will it confuse pool allocation if it runs afterwards? If so, is there any way I could clear it at the end of my pass? Thanks, --Patrick -- If I'm not here, I've gone out to find myself. If I get back before I return, please keep me here.

On Tue, Jul 21, 2009 at 10:58 PM, Patrick Simmons<simmon12 at illinois.edu> wrote: > What is this used for?  Does DSA put anything here?  If I want to add > call sites here during my pass, will it confuse pool allocation if it > runs afterwards?  If so, is there any way I could clear it at the end of > my pass? This is used for unprocessed callsites. Clearing it between DSA

Andrew Lenharth wrote: > On Fri, Aug 7, 2009 at 4:45 PM, Patrick Alexander > Simmons<simmon12 at cs.uiuc.edu> wrote: > >> I'm iterating over all LoadInst and StoreInst-type Instructions in a >> Function, and getNodeForValue() is sometimes returning NULL. Why is >> this happening? Shouldn't every load from or store to memory correspond >> to some

Unless you compile a bytecode version of the C standard library, and link it in, then yes. - Daniel On Mon, Jul 13, 2009 at 7:33 PM, Patrick Simmons<simmon12 at illinois.edu> wrote: > Okay, are C standard library functions typically external in a fully > linked LLVM bytecode file? > > --Patrick > > Andrew Lenharth wrote: >> If the function is external, then DSA

I'm iterating over all LoadInst and StoreInst-type Instructions in a Function, and getNodeForValue() is sometimes returning NULL. Why is this happening? Shouldn't every load from or store to memory correspond to some DSNode? --Patrick

On Fri, Aug 7, 2009 at 4:45 PM, Patrick Alexander Simmons<simmon12 at cs.uiuc.edu> wrote: > I'm iterating over all LoadInst and StoreInst-type Instructions in a > Function, and getNodeForValue() is sometimes returning NULL.  Why is > this happening?  Shouldn't every load from or store to memory correspond > to some DSNode? Not if the pointer is null or the pointer

Patrick Alexander Simmons wrote: > Andrew Lenharth wrote: > >> On Fri, Aug 7, 2009 at 4:45 PM, Patrick Alexander >> Simmons<simmon12 at cs.uiuc.edu> wrote: >> >> >>> I'm iterating over all LoadInst and StoreInst-type Instructions in a >>> Function, and getNodeForValue() is sometimes returning NULL. Why is >>> this

I'm noticing that DSA graphs are not created for library functions like "puts". The bytecode file runs with lli, so I think I did my linking okay. Is this normal, or does it mean I'm somehow not giving the algorithm the complete program information it needs? Thanks, --Patrick

If the function is external, then DSA won't create a graph for it. Andrew On Mon, Jul 13, 2009 at 4:54 PM, Patrick Alexander Simmons<simmon12 at cs.uiuc.edu> wrote: > I'm noticing that DSA graphs are not created for library functions like > "puts".  The bytecode file runs with lli, so I think I did my linking > okay.  Is this normal, or does it mean I'm

Patrick Alexander Simmons wrote: > Thank you, and I apologize for conflating the two passes. > > My main remaining concern is about what happens when there is a node in > a function's DSGraph that points to a pool (or pools, if there are > multiple callers) that is not in the DSGraph of that function. For > example, on page 3 of the 2005 PLDI paper, the DSGraph given for

Thank you, and I apologize for conflating the two passes. My main remaining concern is about what happens when there is a node in a function's DSGraph that points to a pool (or pools, if there are multiple callers) that is not in the DSGraph of that function. For example, on page 3 of the 2005 PLDI paper, the DSGraph given for createnode(), Data is pointing to an unlabeled node in the

Patrick Alexander Simmons wrote: > I don't really have a specific question, but, as I've been looking > through pool allocation and the DS graphs extensively, I wanted to > verify that my understanding of the representations used is correct. > Therefore, I'm summarizing my understanding below (which, if it's > correct, may hopefully be helpful to others). I

I don't really have a specific question, but, as I've been looking through pool allocation and the DS graphs extensively, I wanted to verify that my understanding of the representations used is correct. Therefore, I'm summarizing my understanding below (which, if it's correct, may hopefully be helpful to others). I would appreciate if someone who understands pool allocation

Thanks for all your help so far. My problem is that what I have are the pool descriptors, which I by traversing the uses of poolinit and accessing the first argument of each call. I need to find the DSNode (in the original function) to which this pool descriptor corresponds. The rub is that this pool descriptor of course does not exist except in the clone. If I call getFuncInfo(), I get a

Patrick Alexander Simmons wrote: > John Criswell wrote: > >> You can sometimes get NULL DSNodes if a previously-run transform pass >> adds pointers to the program but doesn't update DSA while claiming to >> preserve it. The pool allocation pass, for example, does this: it >> claims to preserve the DSA results (when used for SAFECode) but doesn't >>

John Criswell wrote: > You can sometimes get NULL DSNodes if a previously-run transform pass > adds pointers to the program but doesn't update DSA while claiming to > preserve it. The pool allocation pass, for example, does this: it > claims to preserve the DSA results (when used for SAFECode) but doesn't > properly update the DSGraph when it adds pool handles. Therefore,

Hi all, I just ran into a strange problem. When using the Equivalence-class Bottom-up Data Structure Analysis pass and pool allocation, I noticed some objects using different pool descriptors where I expected them to be in the same pool. We use svn revision 66285 of the DSA. The following 2 programs expose the problem. First the version that runs correctly, ie. producing a single DSNode.

Torvald Riegel wrote: > On Thursday 11 June 2009 18:14:08 John Criswell wrote: > >> If your use of pool allocation requires that you can always get the pool >> handle for a pointer, you need to make sure that pool allocation is >> configured so that it doesn't generate the above scenario. I think >> there is an option to make all pools be global pools.

Hi, I'm trying to run the pool allocation pass through opt, and I'm running into problems. It segfaults frequently; for example, it does this when the input is a simple Hello World program: [simmon12 at apoc testcases]$ opt -load /home/vadve/simmon12/llvm/llvm/projects/llvm-poolalloc/Debug/lib/libLLVMDataStructure.so -load