Displaying 3 results from an estimated 3 matches for "llvmmaysuspendcallback".
2014 May 13
5
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...d 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 (*LLVMMaySuspendCallback)(LLVMContextRef, void *);
/**
* Set the may-suspend callback function for this context.
*
* @see LLVMContext::setMaySuspendCallback()
*/
void LLVMContextSetMaySuspendCallback(LLVMContextRef C,
LLVMMaySuspendCallback Callback,...
2014 May 15
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...ested 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 (*LLVMMaySuspendCallback)(LLVMContextRef, void *);
>>
>> /**
>> * Set the may-suspend callback function for this context.
>> *
>> * @see LLVMContext::setMaySuspendCallback()
>> */
>> void LLVMContextSetMaySuspendCallback(LLVMContextRef C,
>>...
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,