Displaying 2 results from an estimated 2 matches for "llvmorccreatenewthreadsafemodule".
2020 Oct 01
2
OrcV1 removal
...Module is unique: If it is transferred to the JIT
* (e.g. by LLVMOrcLLJITAddLLVMIRModule), in which case the client is no longer
* responsible for it. If it is not transferred to the JIT then the client
* should call LLVMOrcDisposeThreadSafeModule to dispose of it.
*/
LLVMOrcThreadSafeModuleRef
LLVMOrcCreateNewThreadSafeModule(LLVMModuleRef M,
LLVMOrcThreadSafeContextRef TSCtx);
/**
* Dispose of a ThreadSafeModule. This should only be called if ownership has
* not been passed to LLJIT (e.g. because some error prevented the client from
* adding this to the JIT).
*/
void LLVMOrcDispose...
2020 Oct 01
2
OrcV1 removal
Hi,
On 2020-09-30 19:00:45 -0700, Lang Hames wrote:
> Ok -- I'll make getting the new lookup API working a priority then.
Cool.
> > I see a memory leak with OrcV2 that I didn't see with V1. I'm not yet
> > sure where exactly they're coming from. Possible that I'm just missing a
> > step somewhere. Or something around the removable code support