search for: medyld

...nto separate modules. > > ...loading those bitcode files into separate modules (and handing those > modules to JIT) works as expected. What *should* be same code going > directly into JIT does not work. > > Which smells like the problem may be in my JIT hookup and not in > RuntimeDyld. > > I'll try to sort out my codepaths before digging into RuntimeDyld, so I > can be sure I'm doing same things in "live" JIT and when dumping/loading > bitcode. > > I'll let you know what turns up. > > Cheers, > > -- nikodemus > > > On...

...movl $213, 4 00000054: IMAGE_REL_I386_DIR32 _foo It looks like the offset `4` of the second field of your struct is correct in the object file, so this does seem to be a problem in the JIT-specific linking/loading. Can you try debugging into lib/ExecutionEngine/RuntimeDyld/Targets/RuntimeDyldCOFFI386.h to see if the relocation is getting applied correctly in the context of your JIT? You may be able to repro this more easily using `lli`. It has a `-jit-kind` argument that should get you into the JIT codepath. (see test/ExecutionEngine/{MCJIT,ORCMCJIT}/) -- Sean Silv...