search for: jitmodule

...o localFunction = llvm::Function::Create(functionType, llvm::GlobalValue::LinkageTypes::ExternalWeakLinkage, callableName, &ModuleA);</div><div> </div><div>    Function seems to be copied, together with complex types its using:</div><div>    ; ModuleID = 'JitModule'</div><div>    source_filename = "JitModule"   </div><div>    %struct._EN12RecordStreamE = type { %class.RecordStream }</div><div>    declare extern_weak void @_EN12RecordStream4InitEPTsN18_EN12RecordStreamEEPvv(%struct._EN12RecordStreamE*, i8*)<...

...) > - When I have to call a runtime function from the jit-module, I define > an external reference to the function in the jit-module. Something > like: > > llvm::Function* orig = runtimeModule->getFunction("my-function"); > llvm::Function* copy = > (llvm::Function*)jitModule->getOrInsertFunction(orig->getName(), > orig->getFunctionType()); > > This step is not mandatory as you will see after (but I have not > tested a direct use of remote references). > > - Then I use a llvm pass (a FunctionPass). For each function, I > explore each of the...

Thanks for the pointers. Am I correct in assuming that putting the precompiled bitcode into a second module and linking (or using the object caches) would result in ordinary function calls, but would not be able to inline the functions? -- lg On Jan 21, 2014, at 11:55 AM, Kaylor, Andrew <andrew.kaylor at intel.com> wrote: > I would say that the incompatibility is by design. Not