forked from OSchip/llvm-project
8b94274f22
MaterializationResponsibility. VModuleKeys are intended to enable selective removal of modules from a JIT session, however for a wide variety of use cases selective removal is not needed and introduces unnecessary overhead. As of this commit, the default constructed VModuleKey value is reserved as a "do not track" value, and becomes the default when adding a new module to the JIT. This commit also changes the propagation of VModuleKeys. They were passed alongside the MaterializationResponsibity instance in XXLayer::emit methods, but are now propagated as part of the MaterializationResponsibility instance itself (and as part of MaterializationUnit when stored in a JITDylib). Associating VModuleKeys with MaterializationUnits in this way should allow for a thread-safe module removal mechanism in the future, even when a module is in the process of being compiled, by having the MaterializationResponsibility object check in on its VModuleKey's state before commiting its results to the JITDylib. llvm-svn: 344643 |
||
|---|---|---|
| .. | ||
| IntelJITEvents | ||
| Interpreter | ||
| MCJIT | ||
| OProfileJIT | ||
| Orc | ||
| PerfJITEvents | ||
| RuntimeDyld | ||
| CMakeLists.txt | ||
| ExecutionEngine.cpp | ||
| ExecutionEngineBindings.cpp | ||
| GDBRegistrationListener.cpp | ||
| LLVMBuild.txt | ||
| SectionMemoryManager.cpp | ||
| TargetSelect.cpp | ||