aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2016-08-29 00:54:29 +0000
committerLang Hames <lhames@gmail.com>2016-08-29 00:54:29 +0000
commit6b21751ba9f40dcc553b0d48033edec0f44ef32c (patch)
tree66ece2f0dff487d9e17899d2b3677a9c32752f63 /llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
parent850feaf3b7d9e8ce60a2148a266fda20d9dc96c8 (diff)
downloadllvm-6b21751ba9f40dcc553b0d48033edec0f44ef32c.zip
llvm-6b21751ba9f40dcc553b0d48033edec0f44ef32c.tar.gz
llvm-6b21751ba9f40dcc553b0d48033edec0f44ef32c.tar.bz2
[Orc] Simplify LogicalDylib and move it back inside CompileOnDemandLayer. Also
switch to using one indirect stub manager per logical dylib rather than one per input module. LogicalDylib is a helper class used by the CompileOnDemandLayer to manage symbol resolution between modules during lazy compilation. In particular, it ensures that internal symbols resolve correctly even in the case where multiple input modules contain the same internal symbol name (which must to be promoted to external hidden linkage so that functions in any given module can be split out by lazy compilation). LogicalDylib's resolution scheme (before this commit) required one stub-manager per input module. This made recompilation of functions (by adding a module containing a new definition) difficult, as the stub manager for any given symbol was bound to the module that supplied the original definition. By using one stubs manager for the whole logical dylib symbols can be more easily replaced, although support for doing this is not included in this patch (it will be implemented in a follow up). llvm-svn: 279952
Diffstat (limited to 'llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp')
0 files changed, 0 insertions, 0 deletions