search for: jitsymbolresolver

...9;m really interested into this subject. In my current use case I have two BC files which have cross references to each other, normally I could just add them both to the llvm::ExecutionEngine and they will be resolved. But I would like to resolve these cross references by myself, through the llvm::JITSymbolResolver but I see no way for this, since both files references each other. If I jit A, it will reach the undefined function from file B. So at this point I would have to jit B, but B references a function from A, which isn't completely resolved yet. Is there a way to get the addresses of the functions...

...9;m really interested into this subject. In my current use case I have two BC files which have cross references to each other, normally I could just add them both to the llvm::ExecutionEngine and they will be resolved. But I would like to resolve these cross references by myself, through the llvm::JITSymbolResolver but I see no way for this, since both files references each other. If I jit A, it will reach the undefined function from file B. So at this point I would have to jit B, but B references a function from A, which isn't completely resolved yet. Is there a way to get the addresses of the functions...

...rested into this subject. > > In my current use case I have two BC files which have cross references to each other, normally I could just add them both to the llvm::ExecutionEngine and they will be resolved. > But I would like to resolve these cross references by myself, through the llvm::JITSymbolResolver but I see no way for this, since both files references each other. > > If I jit A, it will reach the undefined function from file B. So at this point I would have to jit B, but B references a function from A, which isn't completely resolved yet. > Is there a way to get the addresses o...

...m::JITEvaluatedSymbol>>> <Params_1>) Line 280 C++ libravi.dll!llvm::jitLinkForORC(llvm::object::ObjectFile & Obj, std::unique_ptr<llvm::MemoryBuffer,std::default_delete<llvm::MemoryBuffer>> UnderlyingBuffer, llvm::RuntimeDyld::MemoryManager & MemMgr, llvm::JITSymbolResolver & Resolver, bool ProcessAllSections, llvm::unique_function<llvm::Error __cdecl(std::unique_ptr<llvm::RuntimeDyld::LoadedObjectInfo,std::default_delete<llvm::RuntimeDyld::LoadedObjectInfo>>,std::map<llvm::StringRef,llvm::JITEvaluatedSymbol,std::less<llvm::StringRef>,std::...

...; references with own addresses? Like when somebody used printf in the > generated obj-File, but I replace the address with my own printf? > > You can load precompiled object files by calling addObjectSet on the > ObjectLayer. > > All external symbol references are resolved by the JITSymbolResolver that > is created by createLambdaResolver. In your example the resolution process > is two-step: First the JIT searches its own function definitions to see if > there is a function called "printf" defined there (this is what the call to > CompileLayer.findSymbol does): > &g...