summaryrefslogtreecommitdiffstats
path: root/llvm/examples/LLJITExamples/LLJITWithJITLink/LLJITWithJITLink.cpp
Commit message (Collapse)AuthorAgeFilesLines
* [examples] Rename LLJITWithJITLink to LLJITWithCustomObjectLinkingLayer.Lang Hames2019-12-151-68/+0
| | | | | | | | LLJIT now uses JITLink/ObjectLinkingLayer by default where available, so these steps aren't required to use it. The tutorial is still useful though: Clients can use it to test altervative linking layer implementations (e.g. handing off to the system linker) or to test implementations of JITLink that are still under development.
* [examples] Update LLJITWithJITLink example for change in c0143f37dab.Lang Hames2019-12-151-11/+9
|
* [examples] Fix some comments in the LLJITWithJITLink exampleLang Hames2019-10-181-2/+2
| | | | llvm-svn: 375269
* [examples] Add an example of how to use JITLink and small-code-model with LLJIT.Lang Hames2019-10-181-0/+70
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
OpenPOWER on IntegriCloud