[LLVMdev] multithreading and the JIT, specifically llvm::sys::Memory

Justin Bogner mail at justinbogner.com
Mon Mar 23 11:51:39 PDT 2015

Dale Martin <Dale.Martin at mathworks.com> writes:
> We were doing some experiments to deserialize/JIT bitcode on multiple threads
> and we hit what looks like this issue:
> http://lists.cs.uiuc.edu/pipermail/llvmbugs/2013-April/027937.html
> We’re using LLVM-3.5 so I was a bit surprised that the patch that was provided
> in 2013 doesn’t appear to be in the current codebase. I’m curious what the
> status of this patch and issue are? Are other people multithreading their code
> this way?

I didn't look into it, but the bug's description states this only
happens when LLVM is built by a pre-C++11 compiler. Trunk requires C++11
these days, so is this fix even relevant anymore?

More information about the llvm-dev mailing list