search for: globalnodes

Is there some efficient way to find the malloc instructions which point to the memory represented by a DSNode? Right now the only way I see is by iterating through the value map in the DSGraph object and finding every value that points to my DSNode. A possibly related question: is there a way to tell that the node has been merged, and if so, what types of nodes went into the merge? Thanks,

I have some questions regarding how globals are represented in DS graph. Specifically, I wrote the following simple program: List *g; void alloc_func(){ g = ( List* ) malloc( sizeof( List ) ); } void free_func(){ free( g ); } int main(){ alloc_func(); free_func(); } I noticed that the DSnode for g in alloc_func is different from that of free_func and NEITHER of them had GlobalNode

Ganesh, I modified DataStructure.cpp so that global nodes are no longer removed from any graphs. Only that file has changed. Chris, if you get a chance to do this, it would be nice if you could take a quick look at the change I made and make sure that's all that's needed. Thanks, --Vikram http://www.cs.uiuc.edu/~vadve > From: Chris Lattner <sabre at nondot.org> >

We have created a new alias -- llvmbugs at cs.uiuc.edu. Please use this for reporting bugs or turning in patches for LLVM. Any such feedback would be appreciated! Please continue to use llvmdev to post questions or have discussions about LLVM. --Vikram http://www.cs.uiuc.edu/~vadve

> Is there some efficient way to find the malloc instructions which point > to the memory represented by a DSNode? Right now the only way I see is > by iterating through the value map in the DSGraph object and finding > every value that points to my DSNode. You're right, you have to iterate over the program, looking to see what DSNodes the Malloc instructions point to. This is

On Fri, 22 Nov 2002, lee white baugh wrote: > do calls to exit() always have a null target-function pointer? that is > what i think i am seeing. Currently, yes. What's actually happening is that the call gets moved to the "globals graph". Essentially, this is due to the fact that the function call cannot modify the local memory graph of the current function. In cases where

> Specifically, I wrote the following simple program: > List *g; > void alloc_func(){ > g = ( List* ) malloc( sizeof( List ) ); > } > void free_func(){ > free( g ); > } I don't have an LLVM tree available to me right now (as tank/llvm.cs.uiuc.edu) is down, so take this with a grain of salt... > I noticed that the DSnode for g in alloc_func is different from

...================================== --- include/poolalloc/PoolAllocate.h (revision 44934) +++ include/poolalloc/PoolAllocate.h (working copy) @@ -144,7 +144,9 @@ /// map contains the global variable that holds the pool descriptor for the /// node. std::map<const DSNode*, Value*> GlobalNodes; - + protected: + PoolAllocate(intptr_t id, bool passAllArguments) + : ModulePass (id), PassAllArguments (passAllArguments) {} public: static char ID; #ifdef SAFECODE @@ -276,14 +278,14 @@ void CalculateLivePoolFreeBlocks(std::set<BasicBlock*> &LiveBlocks,Value *PD); }; -...

Prof. Vikram, I updated the DataStructure.cpp and recompiled the llvm. But still I have the same scenario. I don't get the same DSnode for global. I tried several methods; but none of them were successful. I used the getNodeForValue and again I found that the global value had different nodes in different functions. However, the getGlobals worked well for function call. Thanks, Ganesh On Mon,

Chris Lattner wrote: > > Is there some efficient way to find the malloc instructions which point > > to the memory represented by a DSNode? Right now the only way I see is > > by iterating through the value map in the DSGraph object and finding > > every value that points to my DSNode. > > You're right, you have to iterate over the program, looking to see what