On Fri, Mar 30, 2012 at 10:12 AM, Jose Fonseca wrote:
>
>
> - Original Message -
>> Ok, what if I one uses a global lock around every gl call?
>
> What do you mean with around every gl call? You mean not on the GL driver but
> in the GL application? Yeah, that'd work. Though in that case
- Original Message -
> Ok, what if I one uses a global lock around every gl call?
What do you mean with around every gl call? You mean not on the GL driver but
in the GL application? Yeah, that'd work. Though in that case there's not much
point to use GL from multiple threads.
> Woul
Ok, what if I one uses a global lock around every gl call? Would that
work with the current version of pipeline before proper thread support
is in place?
On Fri, Mar 30, 2012 at 3:42 AM, Jose Fonseca wrote:
> gallivm/llvmpipe is not thread safe.
>
> To fix it, we need to have separate LLVMContext
gallivm/llvmpipe is not thread safe.
To fix it, we need to have separate LLVMContext / JIT engines for each
pipe_context (i.e., each thread).
I'm working on a branch that does most of this, and I plan to commit over the
next month or so. That branch also has changes for the compilation to happe
Hi,
last time I was wondering about thread safety in Mesa 8.0 build with
llvm=no - this configuration seems to be working with the lock patch.
Now I am testing 8.0 branch with LLVM 3.0 (with scons script fix
a1482b21cb438c271cf20e7d52cb9e4e0537344c - stop me if it is not
supposed to work)
I have
