aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/ELFObjectFile.cpp
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2023-03-26 18:13:15 -0700
committerLang Hames <lhames@gmail.com>2023-03-26 18:20:47 -0700
commitd02ef707cbdab295aa4b645a068d298bfa85997a (patch)
tree93cf80d9dc59aa1060eb5b075c17058662f3dedc /llvm/lib/Object/ELFObjectFile.cpp
parent6cef325481a8efc039ae9df5630609fd3a84560c (diff)
downloadllvm-d02ef707cbdab295aa4b645a068d298bfa85997a.zip
llvm-d02ef707cbdab295aa4b645a068d298bfa85997a.tar.gz
llvm-d02ef707cbdab295aa4b645a068d298bfa85997a.tar.bz2
[LLJIT] Add convenience methods for loading dylibs and linking static libs.
LLJIT::loadPlatformDynamicLibrary loads a dynamic library at a given path (interpreted in the executor process -- the process containing the JIT'd code), and returns a JITDylib (whose name is the given path) that reflects the symbols in that library. LLJIT clients wishing to make the given symbols visible to their JIT'd code can add this JITDylib to the link order of their JITDylib(s) using JITDylib::addToLinkOrder. The LLJIT::linkStaticLibraryInto overloads load a static library (or universal binary) at a given path (interpreted in the controller process -- the process containing the LLJIT instance) and adds its symbols to the given JITDylib. The lli tool is updated to use LLJIT::linkStaticLibraryInto to implement the extra-archive option. LLJIT::loadPlatformDynamicLibrary is not tested in this patch as we don't have a good way to produce dylibs in LLVM's regression test suite.
Diffstat (limited to 'llvm/lib/Object/ELFObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions