llvm dev - Feb 2009 - [LLVMdev] Recommended pattern to use LLVM JIT in a multithreaded application

Since my last question was a bit long, I'll keep this short:

What is the "best practice" way to use LLVM JIT in a multithreaded
application? I've noticed there can only be one JIT ExecutionEngine present
in the application, and putting the engine in a singleton instance doesn't
seem to work.

Thanks,
Eric Yew
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090227/d94f4e08/attachment.html>

I forgot the details. But I believe your application needs to manage  
the lock to the module provider.

Evan

On Feb 27, 2009, at 1:42 PM, Eric wrote:
> Since my last question was a bit long, I'll keep this short:
>
> What is the "best practice" way to use LLVM JIT in a
multithreaded
> application? I've noticed there can only be one JIT ExecutionEngine  
> present in the application, and putting the engine in a singleton  
> instance doesn't seem to work.
>
> Thanks,
> Eric Yew
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev