search for: modulehandlet

Displaying 9 results from an estimated 9 matches for "modulehandlet".

Did you mean: modulehandle
2017 Sep 22
2
Question regarding GlobalMappingLayer in LLVM 5
...mizeLayer is: IRTransformLayer<GlobalMappingLayerT, OptimizeFunction> OptimizeLayer; This worked fine with LLVM 4, but causes a problem in LLVM 5. It looks like the issue is that IRTransformLayer::addModule returns an Expected<ModuleT>, whereas GlobalMappingLayer returns just a ModuleHandleT. However, in LLVM 4, IRTransformLayer::addModuleSet returned a ModuleSetT and GlobalMappingLayer::addModuleSet also returned a ModuleSetHandleT, so the types matched up. In LLVM 5, the CompileOnDemandLayer was changed to return an Expected<ModuleHandleT>, but not GlobalMappingLayer. Does t...
2017 Sep 28
0
Question regarding GlobalMappingLayer in LLVM 5
...t;GlobalMappingLayerT, OptimizeFunction> > OptimizeLayer; > > > > This worked fine with LLVM 4, but causes a problem in LLVM 5. It looks > like the issue is that IRTransformLayer::addModule returns an > Expected<ModuleT>, whereas GlobalMappingLayer returns just a > ModuleHandleT. However, in LLVM 4, IRTransformLayer::addModuleSet returned > a ModuleSetT and GlobalMappingLayer::addModuleSet also returned a > ModuleSetHandleT, so the types matched up. In LLVM 5, the > CompileOnDemandLayer was changed to return an Expected<ModuleHandleT>, but > not GlobalM...
2015 Mar 13
4
[LLVMdev] Thoughts about ExecutionEngine/MCJIT interface
Hi, I think ExecutionEngine as a common interface for both Interpreter and MCJIT is almost useless in the current form. There are separated methods in ExecutionEngine for similar or the same features provided by Interpreter and MCJIT, i.e. to get a pointer to function you should call getPointerToFunction() for Interpreter or getFunctionAddress() for MCJIT. Personally, I'm using MCJIT and
2016 May 17
3
External function resolution: MCJIT vs ORC JIT
...t; DL; DL.reset (new llvm::DataLayout (TM->createDataLayout())); std::unique_ptr<llvm::ExecutionEngine> EE; typedef llvm::orc::ObjectLinkingLayer<> ObjLayerT; typedef llvm::orc::IRCompileLayer<ObjLayerT> CompileLayerT; typedef CompileLayerT::ModuleSetHandleT ModuleHandleT; ObjLayerT Objlayer; CompileLayerT Compilelayer (Objlayer, llvm::orc::SimpleCompiler(*TM)); std::unique_ptr<llvm::Module> M (new llvm::Module("module", Context)); M->setDataLayout (*DL); // Declare stub for external function sqr auto type_float = llvm::Ty...
2017 Nov 14
1
OrcJIT + CUDA Prototype for Cling
...bjectTransformLayer<decltype(ObjectLayer), >                        decltype(&KaleidoscopeJIT::dumpObject)> > DumpObjectsLayer; >   IRCompileLayer<decltype(DumpObjectsLayer), SimpleCompiler> CompileLayer; > > public: >   using ModuleHandle = decltype(CompileLayer)::ModuleHandleT; > >   KaleidoscopeJIT() >       : TM(EngineBuilder().selectTarget()), DL(TM->createDataLayout()), >         ObjectLayer([]() { return > std::make_shared<SectionMemoryManager>(); }), >         DumpObjectsLayer(ObjectLayer, &KaleidoscopeJIT::dumpObject), >         C...
2016 May 19
2
External function resolution: MCJIT vs ORC JIT
...(new llvm::DataLayout (TM->createDataLayout())); > std::unique_ptr<llvm::ExecutionEngine> EE; > typedef llvm::orc::ObjectLinkingLayer<> ObjLayerT; > typedef llvm::orc::IRCompileLayer<ObjLayerT> CompileLayerT; > typedef CompileLayerT::ModuleSetHandleT ModuleHandleT; > ObjLayerT Objlayer; > CompileLayerT Compilelayer (Objlayer, llvm::orc::SimpleCompiler(*TM)); > std::unique_ptr<llvm::Module> M (new llvm::Module("module", Context)); > M->setDataLayout (*DL); > > // Declare stub for external function sqr...
2016 May 20
0
External function resolution: MCJIT vs ORC JIT
...ayout (TM->createDataLayout())); >> std::unique_ptr<llvm::ExecutionEngine> EE; >> typedef llvm::orc::ObjectLinkingLayer<> ObjLayerT; >> typedef llvm::orc::IRCompileLayer<ObjLayerT> CompileLayerT; >> typedef CompileLayerT::ModuleSetHandleT ModuleHandleT; >> ObjLayerT Objlayer; >> CompileLayerT Compilelayer (Objlayer, llvm::orc::SimpleCompiler(*TM)); >> std::unique_ptr<llvm::Module> M (new llvm::Module("module", Context)); >> M->setDataLayout (*DL); >> >> // Declare stub for...
2016 May 22
1
External function resolution: MCJIT vs ORC JIT
...ayout (TM->createDataLayout())); >> std::unique_ptr<llvm::ExecutionEngine> EE; >> typedef llvm::orc::ObjectLinkingLayer<> ObjLayerT; >> typedef llvm::orc::IRCompileLayer<ObjLayerT> CompileLayerT; >> typedef CompileLayerT::ModuleSetHandleT ModuleHandleT; >> ObjLayerT Objlayer; >> CompileLayerT Compilelayer (Objlayer, llvm::orc::SimpleCompiler(*TM)); >> std::unique_ptr<llvm::Module> M (new llvm::Module("module", Context)); >> M->setDataLayout (*DL); >> >> // Declare stub fo...
2017 Sep 27
2
OrcJIT + CUDA Prototype for Cling
Dear LLVM-Developers and Vinod Grover, we are trying to extend the cling C++ interpreter (https://github.com/root-project/cling) with CUDA functionality for Nvidia GPUs. I already developed a prototype based on OrcJIT and am seeking for feedback. I am currently a stuck with a runtime issue, on which my interpreter prototype fails to execute kernels with a CUDA runtime error. === How to use the