forked from OSchip/llvm-project
c5800f68bd
Add API for specifying which `LLVMContext` each `lto_module_t` and
`lto_code_gen_t` is in.
In particular, this enables the following flow:
for (auto &File : Files) {
lto_module_t M = lto_module_create_in_local_context(File...);
querySymbols(M);
lto_module_dispose(M);
}
lto_code_gen_t CG = lto_codegen_create_in_local_context();
for (auto &File : FilesToLink) {
lto_module_t M = lto_module_create_in_codegen_context(File..., CG);
lto_codegen_add_module(CG, M);
lto_module_dispose(M);
}
lto_codegen_compile(CG);
lto_codegen_write_merged_modules(CG, ...);
lto_codegen_dispose(CG);
This flow has a few benefits.
- Only one module (two if you count the combined module in the code
generator) is in memory at a time.
- Metadata (and constants) from files that are parsed to query symbols
but not linked into the code generator don't pollute the global
context.
- The first for loop can be parallelized, since each module is in its
own context.
- When the code generator is disposed, the memory from LTO gets freed.
rdar://problem/18767512
llvm-svn: 221733
|
||
|---|---|---|
| .. | ||
| Transforms | ||
| Analysis.h | ||
| BitReader.h | ||
| BitWriter.h | ||
| Core.h | ||
| Disassembler.h | ||
| ExecutionEngine.h | ||
| IRReader.h | ||
| Initialization.h | ||
| LinkTimeOptimizer.h | ||
| Linker.h | ||
| Object.h | ||
| Support.h | ||
| Target.h | ||
| TargetMachine.h | ||
| lto.h | ||
| module.modulemap | ||