search for: defaultmemorymanager

...f the function is? I need this to register the function for profiling. varth said: aph, you need to intercept the "endFunctionBody" call on the memory manager, it will tell you the start pointer and the end pointer But how can I do this? The obvious way would be for me to inherit from DefaultMemoryManager and pass an instance of my class to ExecutionEngine::createJIT. But DefaultMemoryManager isn't public so I can't inherit from it. It's not at all obvious to me how I'm supposed to intercept endFunctionBody. Thanks, Andrew.

...g. > > varth said: aph, you need to intercept the "endFunctionBody" call on > the memory manager, it will tell you the start pointer and the end > pointer > Yep, that's what I said :) > But how can I do this? The obvious way would be for me to inherit > from DefaultMemoryManager and pass an instance of my class to > ExecutionEngine::createJIT. Correct. > But DefaultMemoryManager isn't public so > I can't inherit from it. You should inherit from JITMemoryManager. > It's not at all obvious to me how I'm > supposed to intercept endFunctio...

Folks, Is anyone else the failure below? On Mac OS X everything builds properly... Thanks for any help, snaroff -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture 27.png Type: image/png Size: 18959 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081217/e7d37fee/attachment.png>

...eed to intercept the "endFunctionBody" call on >> the memory manager, it will tell you the start pointer and the end >> pointer >> > > Yep, that's what I said :) > >> But how can I do this? The obvious way would be for me to inherit >> from DefaultMemoryManager and pass an instance of my class to >> ExecutionEngine::createJIT. > > Correct. > >> But DefaultMemoryManager isn't public so >> I can't inherit from it. > > You should inherit from JITMemoryManager. >> It's not at all obvious to me how I...

...8 So what should the right long-term behavior be? It makes sense to me to use the JITMemoryManager for this so that clients of the JIT can customize allocation instead of using malloc or new char[]. On the other hand, that complicates the API and requires a homegrown malloc implementation in the DefaultMemoryManager. Reid

...e right long-term behavior be? It makes sense to me > to use the JITMemoryManager for this so that clients of the JIT can > customize allocation instead of using malloc or new char[]. On the > other hand, that complicates the API and requires a homegrown malloc > implementation in the DefaultMemoryManager. > > Reid > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev