similar to: [LLVMdev] MCJIT crash on 64 bit Linux, works find on OSX

Displaying 8 results from an estimated 8 matches similar to: "[LLVMdev] MCJIT crash on 64 bit Linux, works find on OSX"

2015 Aug 20
2
Linking existing functions from JITed code
Lang, I added the add/get global mapping to my kaleidoscope JIT, but I think perhaps these would make more sense if they were added to the object linking layer as they would be generally usable there. On Aug 19, 2015, at 11:19 PM, Andy Somogyi wrote: > Hey Lang, > > I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping
2015 Aug 20
2
Linking existing functions from JITed code
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 > >
2015 Aug 13
2
Linking existing functions from JITed code
Hi Andy, I haven't tested this on Linux, but on MacOS the RuntimeDyldMemorManager::getSymbolAddressInProcess method should find symbol addresses in the host program, including symbols from static archives linked into the program. However, one gotcha is that the symbol has to be reachable from main, otherwise the linker may strip it from the final executable. Do you have a test-case that I
2015 Aug 24
2
enumerate symbols in RuntimeDyld
Hi All Is there any technical reason why we can’t or shouldn’t have RuntimeDyld be able to enumerate all symbols in the dyld? I know elf, mach-o apis have this capability, and I’m reasonably sure coff has support for it as well.
2015 Aug 13
4
Linking existing functions from JITed code
Hi I’ve previously used the ExecutionEngine::addGlobalMapping to make existing functions available to my JITed code. I’m currently using ORC, as MCJIT does not appear to be maintained any longer (the kaleidoscope examples have not worked for some time with MCJIT). I’m using just the basic ORC CompileLayer directly. So, I’ve essentially copied the ExecutionEngine::addGlobalMapping related
2007 Jun 22
1
Implicit storage tiering w/ ZFS
I''m curious if there has been any discussion of or work done toward implementing storage classing within zpools (this would be similar to the storage foundation QoSS feature). I''ve searched the forum and inspected the documentation looking for a means to do this, and haven''t found anything, so pardon the post if this is redundant/superfluous. I would imagine this would
2007 Dec 14
0
nfs4 acl support to be implemented
Hi List, I'm interested in implementing nfs4 acl support for rsync. Are there any pointers to start? Is anybody else working on this? -- Peter Somogyi Gamax Kft Bartok Bela ut 15/D H-1114, Budapest, Hungary e-mail: psomogyi@gamax.hu phone: +36 1 382 5469
2015 Jul 28
0
[LLVMdev] ORC name mangling
Hi, I’d like to make sure my understanding of the name mangling in the ORC examples is correct. In the ORC lazy examples, each function gets IR’ed into its own separate LLVM module, and each module is compiled separately. So, in the name resolver, all functions need to be resolved by their mangled name, as they are linked with external linkage. I’m still not clear on what exactly performs the