aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/ExecutionEngine/Orc/DebugObjectManagerPlugin.cpp
diff options
context:
space:
mode:
authorStefan Gränitz <stefan.graenitz@gmail.com>2021-02-23 14:54:21 +0000
committerStefan Gränitz <stefan.graenitz@gmail.com>2021-03-02 15:07:36 +0100
commit99a6d003edbe97fcb94854547276ffad3382ec1d (patch)
tree1cafa01ee244356fd672f2539958624412c3ea2a /llvm/lib/ExecutionEngine/Orc/DebugObjectManagerPlugin.cpp
parentef2389235c5dec03be93f8c9585cd9416767ef4c (diff)
downloadllvm-99a6d003edbe97fcb94854547276ffad3382ec1d.zip
llvm-99a6d003edbe97fcb94854547276ffad3382ec1d.tar.gz
llvm-99a6d003edbe97fcb94854547276ffad3382ec1d.tar.bz2
[lli] Add JITLink in-process debug support
lli aims to provide both, RuntimeDyld and JITLink, as the dynamic linkers/loaders for it's JIT implementations. And they both offer debugging via the GDB JIT interface, which builds on the two well-known symbol names `__jit_debug_descriptor` and `__jit_debug_register_code`. As these symbols must be unique accross the linked executable, we can only define them in one of the libraries and make the other depend on it. OrcTargetProcess is a minimal stub for embedding a JIT client in remote executors. For the moment it seems reasonable to have the definition there and let ExecutionEngine depend on it, until we find a better solution. This is the second commit for the reviewed patch. Reviewed By: lhames Differential Revision: https://reviews.llvm.org/D97339
Diffstat (limited to 'llvm/lib/ExecutionEngine/Orc/DebugObjectManagerPlugin.cpp')
0 files changed, 0 insertions, 0 deletions