Displaying 3 results from an estimated 3 matches for "maysuspendcallbackti".
Did you mean:
maysuspendcallbackty
2014 May 13
5
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
Sounds good. Lets get started by nailing down the C API and semantics for this first.
I mirrored the C API for the LLVM context diagnostic handler and used Andy’s suggested name for the callback.
The opaque handle was suggested by Duncan and can provide optional user specified information that is
provided back during the callback (i.e. barrier, etc).
Cheers,
Juergen
Core.h:
typedef void
2014 May 15
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
On May 15, 2014, at 9:50 AM, Philip Reames <listmail at philipreames.com> wrote:
> Given the use case (user mode scheduling), I'm not going to oppose this proposal. I would like to see a couple of things clarified documentation wise:
> - When is this interface valid? (i.e. the single thread case)
> - If a context does have multiple threads, is this called once per thread? Or
2014 May 13
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
On May 12, 2014, at 3:52 PM, Philip Reames <listmail at philipreames.com> wrote:
> I don't have a strong opinion on this topic at the moment, but given that it is potentially GC related, I figured I'd speak up.
>
> I see two unspoken assumptions in the thread so far:
> - The runtime needs a means to bring all threads to a stop to perform some action. In particular,