search for: lllazyjit

Hi, We are using the new LLJIT class in our compiler. We have not been successful using the parallel JIT feature. When we tried it previously on multiple modules, our compile-time increased significantly. I don't know if we are using it incorrectly, or that we miss out on optimizations we get when running on a single merged module, but it hasn't worked for us yet. We are pretty far behind

Trying to put together a simple test JIT compiler, using ORC which as I understand it will be the supported API going forward, I noticed that in the first chapter of the updated Kaleidoscope tutorial, there is sample code that starts like this: ExecutionSession ES; RTDyldObjectLinkingLayer ObjectLayer; IRCompileLayer CompileLayer; DataLayout DL; MangleAndInterner Mangle; ThreadSafeContext Ctx;

We are trying to switch to the new orc v2 lljit engine at my work with hopes of parallel jitting. We are switching from the ExecutionEngine w/ OrcMCJitReplacement. We are having a hard time with global variables. We have found a way to create/emit new globals during jitting by using the old ExecutionEngine::getOrEmitGlobalVariable. Is there an easier way to do this with the new jit engine? We were

Hi folks, Rather by accident than on purpose I looked at the release notes and found the following: http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html#changes-to-the-jit-apis TL;DR: Orc v1 is deprecated and will be removed in the next release. I have several questions in this regard: 1. Is there a migration guide I can use to update my code to the new version? 2. Is there any development

...tions) to try to guess what functions are worth speculatively compiling next. Idea is proposed by Lang Hames. Current Status of ORC v2: 1. ORC currently supports concurrent compilation and Lazy (on request compilation), trunk contains default new ORC JIT implementations as LLJIT, LLLazyJIT. 2. [WIP]  Jit-linker a drop-in-replacement for RuntimeDyld atleast for MachO in ORC JIT. 3. Primitive code to handle speculative is in trunk. But it needs to refactored & designed to get generalized, simple APIs to support speculation. 4. Currently, no heuristi...

...2019 at 23:22, Praveen Velliengiri < praveenvelliengiri at gmail.com> wrote: > Hi Alex > Sorry for late reply > > The New ORC APIs support concurrent compilation. > I'm not aware of any migration guide to ORC v2 from v1. But there is a > in-tree classes called LLJIT and LLLazyJIT which is an example for using > new ORC APIs. > You can also take a look at "Updating ORC for Concurrency" talk by lang > hames, the talk explains about the new APIs. I hope discussions about JIT > is generally available in LLVM-dev mailing lists. > > For documentation k...

...piling next. >> Idea is proposed by Lang Hames. >> >> Current Status of ORC v2: >> >> 1. >> ORC currently supports concurrent compilation and Lazy (on >> request compilation), trunk contains default new ORC JIT >> implementations as LLJIT, LLLazyJIT. >> 2. >> [WIP]  Jit-linker a drop-in-replacement for RuntimeDyld atleast >> for MachO in ORC JIT. >> 3. >> Primitive code to handle speculative is in trunk. But it needs to >> refactored & designed to get generalized, simple APIs to support &...

...t; So below is the break down of the steps that I do: > >>>>>>> First I compile this code to an instance of llvm::Module by using > the logic borrowed from the lli tool. > >>>>>>> Once I have the Module instance I construct an instance of > orc::LLLazyJIT (J), configure it (again closely following the logic in lli > tool) > >>>>>>> to which I then add the module like this: > >>>>>>> > >>>>>>> // Add the main module. > >>>>>>> > >>>>&...

...td::cout << "Hello World!" << std::endl; return 0; } So below is the break down of the steps that I do: First I compile this code to an instance of llvm::Module by using the logic borrowed from the lli tool. Once I have the Module instance I construct an instance of orc::LLLazyJIT (J), configure it (again closely following the logic in lli tool) to which I then add the module like this: // Add the main module. ExitOnErr(J->addLazyIRModule(orc::ThreadSafeModule(std::move(MainModule), TSCtx))); Finally the module is executed like this: // Run main. auto M...

Hi Stefan Thank you! In case, you missed in llvm-dev listing: you can find the proposal here : link. <https://docs.google.com/document/d/1202EcXlWMQ8yxu5qD0b5fE0a_kihlcaPNpZo_Jk0YeQ/edit?usp=sharing> Thanks for working on summarising the Bugzilla tickets to track the recent changes in ORC this is really helpful. On Sat, 18 May 2019 at 21:33, Stefan Gränitz <stefan.graenitz at

Hi All, I'm back again after a couple of weeks hiatus, and I have some good news for anyone interested in cross-process JITing with OrcV2: The remote TargetProcessControl and Orc library breakup patch has landed in 1d0676b54c4 [1]. Thanks very much to Dave Blaikie and Stefan Graenitz for all their feedback on the review! As described in my last email, this commit breaks the OrcJIT library

...;>>>> So below is the break down of the steps that I do: >>>>> First I compile this code to an instance of llvm::Module by using the >>>>> logic borrowed from the lli tool. >>>>> Once I have the Module instance I construct an instance of orc::LLLazyJIT >>>>> (J), configure it (again closely following the logic in lli tool) >>>>> to which I then add the module like this: >>>>> >>>>> // Add the main module. >>>>> >>>>> >>>>> ExitOnErr(J->...

...t;>>> >>>> Current Status of ORC v2: >>>> >>>> 1. >>>> ORC currently supports concurrent compilation and Lazy (on >>>> request compilation), trunk contains default new ORC JIT >>>> implementations as LLJIT, LLLazyJIT. >>>> 2. >>>> [WIP]  Jit-linker a drop-in-replacement for RuntimeDyld atleast >>>> for MachO in ORC JIT. >>>> 3. >>>> Primitive code to handle speculative is in trunk. But it needs >>>> to refactored & desig...