summaryrefslogtreecommitdiffstats
path: root/llvm/docs/tutorial
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2018-02-06 21:25:11 +0000
committerLang Hames <lhames@gmail.com>2018-02-06 21:25:11 +0000
commit4b546c91452c5735ada1430f8a6943328e4dba4e (patch)
tree633421ee6cc4d06fce9ce73f625992e7dbedc6fe /llvm/docs/tutorial
parentffe72034a6d688efcd7035fe9caf5964f00037c0 (diff)
downloadbcm5719-llvm-4b546c91452c5735ada1430f8a6943328e4dba4e.tar.gz
bcm5719-llvm-4b546c91452c5735ada1430f8a6943328e4dba4e.zip
[ORC] Start migrating ORC layers to use the new ORC Core.h APIs.
In particular this patch switches RTDyldObjectLinkingLayer to use orc::SymbolResolver and threads the requried changse (ExecutionSession references and VModuleKeys) through the existing layer APIs. The purpose of the new resolver interface is to improve query performance and better support parallelism, both in JIT'd code and within the compiler itself. The most visibile change is switch of the <Layer>::addModule signatures from: Expected<Handle> addModule(std::shared_ptr<ModuleType> Mod, std::shared_ptr<JITSymbolResolver> Resolver) to: Expected<Handle> addModule(VModuleKey K, std::shared_ptr<ModuleType> Mod); Typical usage of addModule will now look like: auto K = ES.allocateVModuleKey(); Resolvers[K] = createSymbolResolver(...); Layer.addModule(K, std::move(Mod)); See the BuildingAJIT tutorial code for example usage. llvm-svn: 324405
Diffstat (limited to 'llvm/docs/tutorial')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud