search for: llvmorclljitaddllvmirmodul

...es say that: /** * Create a ThreadSafeModule wrapper around the given LLVM module. This takes * ownership of the M argument which should not be disposed of or referenced * after this function returns. * * Ownership of the ThreadSafeModule 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, LLVMO...

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

...le) (Layer.cpp:28) | | | ->03.53% (97,542B) 0x83BCBF5: llvm::orc::LLJIT::addIRModule(llvm::orc::JITDylib&, llvm::orc::ThreadSafeModule, llvm::IntrusiveRefCntPtr<llvm::orc::ResourceTracker>) (LLJIT.cpp:990) | | | ->03.52% (97,354B) 0x840C95B: LLVMOrcLLJITAddLLVMIRModule (OrcV2CBindings.cpp:263) | | | | ->03.52% (97,354B) 0x80639E9: llvm_compile_module (llvmjit.c:608) | | | | ->03.52% (97,354B) 0x8063000: llvm_get_function (llvmjit.c:275) | | | | ->03.52% (97,354B) 0x80758E1: ExecRunC...

...->03.53% (97,542B) 0x83BCBF5: >> llvm::orc::LLJIT::addIRModule(llvm::orc::JITDylib&, >> llvm::orc::ThreadSafeModule, >> llvm::IntrusiveRefCntPtr<llvm::orc::ResourceTracker>) (LLJIT.cpp:990) >> | | | ->03.52% (97,354B) 0x840C95B: >> LLVMOrcLLJITAddLLVMIRModule (OrcV2CBindings.cpp:263) >> | | | | ->03.52% (97,354B) 0x80639E9: >> llvm_compile_module (llvmjit.c:608) >> | | | | ->03.52% (97,354B) 0x8063000: >> llvm_get_function (llvmjit.c:275) >> | | | |...