summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/commands
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2019-10-18 18:25:15 +0000
committerLang Hames <lhames@gmail.com>2019-10-18 18:25:15 +0000
commit1ac3f80a6a097afd776e925fee4b1176b4383d7f (patch)
tree78df555bfd47ae86b6123e225d2c950e2b8e7d0e /lldb/packages/Python/lldbsuite/test/commands
parent2f41a023afdb68364ea490135874425e85faa574 (diff)
downloadbcm5719-llvm-1ac3f80a6a097afd776e925fee4b1176b4383d7f.tar.gz
bcm5719-llvm-1ac3f80a6a097afd776e925fee4b1176b4383d7f.zip
[examples] Add an example of how to use JITLink and small-code-model with LLJIT.
JITLink is LLVM's newer jit-linker. It is an alternative to (and hopefully eventually a replacement for) LLVM's older jit-linker, RuntimeDyld. Unlike RuntimeDyld which requries JIT'd code to be complied with the large code model, JITlink can link code compiled with the small code model, which is the native code model for a number of targets (including all supported MachO targets). This example shows how to: -- Create a JITLink InProcessMemoryManager -- Set the code model to small -- Use a JITLink backed ObjectLinkingLayer as the linking layer for LLJIT (rather than the default RTDyldObjectLinkingLayer). Note: This example will only work on platforms supported by JITLink. As of this commit that's MachO/x86-64 and MachO/arm64. llvm-svn: 375266
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud