Displaying 3 results from an estimated 3 matches for "opaquehandl".
Did you mean:
opaquehandle
2014 May 15
3
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...tion for this context.
>> *
>> * @see LLVMContext::setMaySuspendCallback()
>> */
>> void LLVMContextSetMaySuspendCallback(LLVMContextRef C,
>> LLVMMaySuspendCallback Callback,
>> void *OpaqueHandle);
>>
>> LLVMContext.h:
>> /// \brief Registers a may-suspend callback with the context.
>> ///
>> /// The may-suspend callback function may be called by LLVM to transfer
>> /// control back to the client that invoked the LLVM compilation. The client
>> //...
2014 May 13
5
[LLVMdev] Finding safe thread suspension points while JIT-ing (was: Add pass run listeners to the pass manager.)
...ef, void *);
/**
* Set the may-suspend callback function for this context.
*
* @see LLVMContext::setMaySuspendCallback()
*/
void LLVMContextSetMaySuspendCallback(LLVMContextRef C,
LLVMMaySuspendCallback Callback,
void *OpaqueHandle);
LLVMContext.h:
/// \brief Registers a may-suspend callback with the context.
///
/// The may-suspend callback function may be called by LLVM to transfer
/// control back to the client that invoked the LLVM compilation. The client
/// is not garantueed to ever receive this callback. It is at the...
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,