search for: compile_to_fil

...mark a visited MDNode used when traversing the module. After done traversing all modules, we can delete MDNodes in MDNodeSet that are not marked. In LTOCodeGenerator, add a vector of source modules that are added (these source modules will be linked with DestroySource mode). In LTOCodeGenerator:: compile_to_file, delete all source modules that are linked in, then call LLVMContext::removeUnusedMDNodes —> I can’t find a better place to call the function. When we call compile_to_file, we should have done linking in all source modules. Another possibility is to add a lto API so the linker can delete the so...

...hen traversing the > module. After done traversing all modules, we can delete MDNodes in > MDNodeSet that are not marked. > > In LTOCodeGenerator, add a vector of source modules that are added (these > source modules will be linked with DestroySource mode). > In LTOCodeGenerator:: compile_to_file, delete all source modules that are > linked in, then call LLVMContext::removeUnusedMDNodes > —> I can’t find a better place to call the function. When we > call compile_to_file, we should have done linking in all source modules. > Another possibility is to add a lto API so the link...

...gt; module. After done traversing all modules, we can delete MDNodes in >> MDNodeSet that are not marked. >> >> In LTOCodeGenerator, add a vector of source modules that are added (these >> source modules will be linked with DestroySource mode). >> In LTOCodeGenerator:: compile_to_file, delete all source modules that are >> linked in, then call LLVMContext::removeUnusedMDNodes >> —> I can’t find a better place to call the function. When we >> call compile_to_file, we should have done linking in all source modules. >> Another possibility is to add a lto...

...ne traversing all modules, we can delete MDNodes in >>> MDNodeSet that are not marked. >>> >>> In LTOCodeGenerator, add a vector of source modules that are added >>> (these source modules will be linked with DestroySource mode). >>> In LTOCodeGenerator:: compile_to_file, delete all source modules that >>> are linked in, then call LLVMContext::removeUnusedMDNodes >>> —> I can’t find a better place to call the function. When we >>> call compile_to_file, we should have done linking in all source modules. >>> Another possibility...

...dules, we can delete MDNodes in >>>> MDNodeSet that are not marked. >>>> >>>> In LTOCodeGenerator, add a vector of source modules that are added >>>> (these source modules will be linked with DestroySource mode). >>>> In LTOCodeGenerator:: compile_to_file, delete all source modules that >>>> are linked in, then call LLVMContext::removeUnusedMDNodes >>>> —> I can’t find a better place to call the function. When we >>>> call compile_to_file, we should have done linking in all source modules. >>>> Ano...

...rictionsDone(false), _codeModel(LTO_CODEGEN_PIC_MODEL_DYNAMIC), - _nativeObjectFile(NULL) { + _nativeObjectFile(NULL), + _IPOPartMgr(_IPOFileMgr) { InitializeAllTargets(); InitializeAllTargetMCs(); InitializeAllAsmPrinters(); @@ -161,34 +311,42 @@ } bool LTOCodeGenerator::compile_to_file(const char** name, std::string& errMsg) { - // make unique temp .o file to put generated object file - SmallString<128> Filename; - int FD; - error_code EC = sys::fs::createTemporaryFile("lto-llvm", "o", FD, Filename); - if (EC) { - errMsg = EC.message(); + i...