search for: llilcjit

Displaying 8 results from an estimated 8 matches for "llilcjit".

Did you mean: 2fllilcjit
2015 Oct 01
2
[cfe-dev] Orc Windows C++
Moving to the LLVM Dev list & cc'ing Lang. On Thu, Oct 1, 2015 at 4:23 AM, Joshua Gerrard via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hello folks, > > I’m developing an application that uses Orc JIT for C++, which works > swimmingly on Mac OS X. However, the Windows version has been a battle and > a half, and it’s now at the point where I need some assistance
2015 May 30
2
[LLVMdev] MCJit interface question
Agreed, that sounds like the best plan. I'll look into moving LLILC to ORC. Thanks -Joseph From: Russell Hadley Sent: Friday, May 29, 2015 8:13 PM To: Lang Hames; Joseph Tremoulet Cc: llvmdev at cs.uiuc.edu Subject: RE: [LLVMdev] MCJit interface question Hey Joseph, What Lang said made me wonder. Is it the right time for us (LLILC) to move to ORC? The long term plan was to go there but
2015 Jun 04
2
[LLVMdev] MCJit interface question
When we were using MCJIT, I could do this: // Attach the event listener Context.EE->RegisterJITEventListener( LLILCJitEventListener::createLLILCJitEventListener( new LLILCJitEventWrapper(&Context))); The event listeners listened for when an object is emitted (NotifyObjectEmitted), and that’s when we’d go through and extract debug info from the ObjectFile. Now, I imagine I’d need to add some sort of l...
2016 May 20
0
External function resolution: MCJIT vs ORC JIT
...ly want to improve support for it so patches, bug reports and feature requests are all very welcome. In case it's useful too, here's a link to the LLILC JIT file, which uses a simple ORC setup on Windows: https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299 Cheers, Lang. On Thu, May 19, 2016 at 11:57 AM, Larry Gritz <lg at larrygritz.com> wrote: > Thanks so much! This seems to do the trick. I would have spun my wheels > for a long time before discovering all of this, wow. > > Do I even want to know what additional chicken...
2016 May 22
1
External function resolution: MCJIT vs ORC JIT
...improve support for it so patches, bug reports and feature requests are all very welcome. > > In case it's useful too, here's a link to the LLILC JIT file, which uses a simple ORC setup on Windows: https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299 > > Cheers, > Lang. > > On Thu, May 19, 2016 at 11:57 AM, Larry Gritz <lg at larrygritz.com> wrote: > Thanks so much! This seems to do the trick. I would have spun my wheels for a long time before discovering all of this, wow. > > Do I even want to know wha...
2015 Jun 04
2
[LLVMdev] MCJit interface question
Hi all, So I’m also working on LLILC. Specifically, I have been working on a JITEventListener to pass debug line info to the CoreCLR EE. With Joe’s change, I’ve lost the ability (or as far as I can tell) to attach an event listener. Is there a way within Orc to do the sorts of things that the JITEventListeners do in MCJIT? How would I go about adding a layer to add debugging support? Thanks,
2016 May 19
2
External function resolution: MCJIT vs ORC JIT
Thanks so much! This seems to do the trick. I would have spun my wheels for a long time before discovering all of this, wow. Do I even want to know what additional chickens need to be sacrificed to get this to work on Windows? -- lg > On May 18, 2016, at 1:52 PM, Lang Hames <lhames at gmail.com> wrote: > > Hi Larry, > > You're basically there, but you're hitting
2015 Oct 02
2
[cfe-dev] Orc Windows C++
...me code there that looks extremely relevant to say the least. > On 1 Oct 2015, at 19:00, Hayden Livingston <halivingston at gmail.com> wrote: > > Maybe looking at their code might help: > > https://github.com/dotnet/llilc/blob/dd12743f9cdb5418f1c39b2cd756da1e8396a922/lib/Jit/LLILCJit.cpp#L299 > > On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Moving to the LLVM Dev list & cc'ing Lang. >> >> On Thu, Oct 1, 2015 at 4:23 AM, Joshua Gerrard via cfe-dev >> <cfe-dev at lists.llvm...