search for: pooldescriptor

...am reading the paper "Making Context-sensitive Points-to Analysis with Heap Cloning Practical For The Real World", and I build the poolalloc module, and run the program in Figure 1 in this paper with -ds-aa alias analysis. Now I know that X and Y in the program would have distinct PoolDescriptors to make them disjoint data structures. However, how can we use the PoolDescriptor? What is storing in it? It seems that the PoolDescriptor in the program is just parsed as an argument from top to down, but it is not modified, so I am a little confused. Thanks, Heming

...he paper "Making Context-sensitive Points-to > Analysis with Heap Cloning Practical For The Real World", and I build > the poolalloc module, and run the program in Figure 1 in this paper > with -ds-aa alias analysis. Now I know that X and Y in the program > would have distinct PoolDescriptors to make them disjoint data > structures. > However, how can we use the PoolDescriptor? What is storing in > it? It seems that the PoolDescriptor in the program is just parsed as > an argument from top to down, but it is not modified, so I am a little > confused. Pool descripto...

...ant to have a look at PoolAllocate.h. > > Per function, a PA::FuncInfo structure keeps track of all DSNodes that > should be pool allocated. ArgNodes contains pool arguments, NodesToPA > contains nodes that are locally pool allocated and thus initialized > using poolinit. > > PoolDescriptors contains a mapping from DSNodes to pool descriptors, and > you could easily invert this mapping. > > Finding a corresponding DSNode which is complete is not uniquely > determined. For example, if a function F uses a pool, but its DSNode > is incomplete, it might be called from two...

...e a look at PoolAllocate.h. >> >> Per function, a PA::FuncInfo structure keeps track of all DSNodes that should be pool allocated. ArgNodes contains pool arguments, NodesToPA >> contains nodes that are locally pool allocated and thus initialized using poolinit. >> >> PoolDescriptors contains a mapping from DSNodes to pool descriptors, and >> you could easily invert this mapping. >> >> Finding a corresponding DSNode which is complete is not uniquely determined. For example, if a function F uses a pool, but its DSNode >> is incomplete, it might be calle...

...) 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 NULL pointer. getFuncInfoOrClone() returns the original function's FuncInfo structure, but this function's DSNode <-> PoolDescriptor mapping will not have my pool descriptor in it because my pool descriptor only existed in the clone. I'm fine with the DSNode being the original function's DSNode -- in fact, I need that -- but I'm really at a loss as to how to get out of this catch-22. --Patrick On 03/19/10 04:10...

You might want to have a look at PoolAllocate.h. Per function, a PA::FuncInfo structure keeps track of all DSNodes that should be pool allocated. ArgNodes contains pool arguments, NodesToPA contains nodes that are locally pool allocated and thus initialized using poolinit. PoolDescriptors contains a mapping from DSNodes to pool descriptors, and you could easily invert this mapping. Finding a corresponding DSNode which is complete is not uniquely determined. For example, if a function F uses a pool, but its DSNode is incomplete, it might be called from two different function G and...

I figure (hopefully correctly) that I can iterate over all pool descriptors in a program by iterating over all users of poolinit and looking at the first argument. However, once I have a pool descriptor, I need to get its corresponding DSNode in the function in which it is complete (or in the global graph if it is a global). How do I do this? Thanks, --Patrick

...nit() to pass an argument containing DSNode information (such as a flag indicating type-homogeneity). -- John T. > If I call getFuncInfo(), I get a NULL pointer. getFuncInfoOrClone() > returns the original function's FuncInfo structure, but this function's > DSNode <-> PoolDescriptor mapping will not have my pool descriptor in it > because my pool descriptor only existed in the clone. I'm fine with the > DSNode being the original function's DSNode -- in fact, I need that -- > but I'm really at a loss as to how to get out of this catch-22. > > --Pa...