Displaying 3 results from an estimated 3 matches for "functionstubmap".
2005 Apr 21
0
[LLVMdev] Control Flow and Locks when JITing Functions
On Thu, 21 Apr 2005, Evan Jones wrote:
> I just located a concurrency error in my LLVM patch to add locks to the
> JIT. I did not add any locks to the JITResolver class in JITEmitter.cpp,
> which clearly is a problem since This particular issue causes an
> assertion failure on occasion when running a task that spawns threads on
> a parallel machine. Any recommendations about if I am
2005 Apr 21
1
[LLVMdev] Control Flow and Locks when JITing Functions
...at I ended up doing. So now, the lock in
"ExecutionEngine" is public, and everything involved in the JIT locks
it.
However, it turns out that the issue isn't quite what I thought it was.
I thought it was a concurrent modification issue, where two threads
were trying to update the FunctionStubMap at the same time. Well, it
sort of is, but for a different reason. I'm not sure how I should fix
this, so suggestions are welcome.
My application is spawning multiple threads that are calling in to the
same function. They all call the stub, and they all end up calling into
JITResolve::JITC...
2005 Apr 21
2
[LLVMdev] Control Flow and Locks when JITing Functions
I just located a concurrency error in my LLVM patch to add locks to the
JIT. I did not add any locks to the JITResolver class in JITEmitter.cpp,
which clearly is a problem since This particular issue causes an
assertion failure on occasion when running a task that spawns threads on
a parallel machine. Any recommendations about if I am doing something
that seems horribly wrong are welcome. I'll