search for: functionblock

...m at a loss to understand how the LLVM JIT could be acting any differently with multiple threads calling JIT routines, than in a single-threaded environment, unless the identical IR build routines executing for multiple threads are creating some sort of conflicting state within the list of internal FunctionBlocks or something of that nature. Any and all ideas would be appreciated. Thanks much, Eric Yew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090227/06763838/attachment.html>

...======== > --- lib/ExecutionEngine/JIT/JITMemoryManager.cpp (revision 46612) > +++ lib/ExecutionEngine/JIT/JITMemoryManager.cpp (working copy) > @@ -256,6 +256,7 @@ > sys::MemoryBlock getNewMemoryBlock(unsigned size); > > std::map<const Function*, MemoryRangeHeader*> FunctionBlocks; > + std::map<const Function*, MemoryRangeHeader*> TableBlocks; > public: > DefaultJITMemoryManager(); > ~DefaultJITMemoryManager(); > @@ -290,6 +291,28 @@ > FreeMemoryList =CurBlock->TrimAllocationToSize(FreeMemoryList, > BlockSize); > } &...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL: