search for: andysomogyi

...e, "bla", module)); executionengine.addGlobalMapping(llvmfunc, &somefunc); // now I have llvmfunc to work with and don't need to consider anything else The GlobalMappingLayer class seems to provide the functionality I want. I oriented myself on the example from https://github.com/AndySomogyi/cayman/blob/aaa809c/src/llvm_orc_initial.cpp#L1172 (just oriented, because at least on 3.9, I can not stack the GlobalMappingLayer on the ObjectLinkingLayer. I have to put it onto the IRCompileLayer. One question I'd have: How does that order matter?) The problem I have with that conceptually...

...ang, > > I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping functionality out of execution engine and hooked up the lambda resolver to reference them. > > Here's the code if you want it: > > https://github.com/AndySomogyi/cayman/blob/master/src/llvm_orc_initial.cpp > > > On Aug 19, 2015, at 9:14 PM, Lang Hames wrote: > >> Hi Andy, >> >> I think that makes sense. I'm currently rewriting the core Kaleidoscope tutorials - I'll look at adding support for this. >> >>...

Hi Andy, I think that makes sense. I'm currently rewriting the core Kaleidoscope tutorials - I'll look at adding support for this. - Lang. On Fri, Aug 14, 2015 at 7:38 AM, Andy Somogyi <andy.somogyi at gmail.com> wrote: > After some fiddling with it, it does in fact look like it works as you > describe Lang. > > The trick was you had to call > >