Vitaly Buka ef76fcda6e [LTO] Make processing of combined module more consistent ... Summary: 1. Use stream 0 only for combined module. Previously if combined module was not processes ThinLTO used the stream for own output. However small changes in input, could trigger combined module and shuffle outputs making life of llvm::LTO harder. 2. Always process combined module and write output to stream 0. Processing empty combined module is cheap and allows llvm::LTO users to avoid implementing processing which is already done in llvm::LTO. Subscribers: mehdi_amini, inglorion, eraman, hiraditya Differential Revision: https://reviews.llvm.org/D41267 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@320905 91177308-0d34-0410-b5e6-96231b3b80d8		2017-12-16 02:10:00 +00:00
..
Caching.cpp	LTO: clarify why we need to gracefully handle sys::fs::rename failures	2017-11-16 01:16:52 +00:00
CMakeLists.txt
LLVMBuild.txt
LTO.cpp	[LTO] Make processing of combined module more consistent	2017-12-16 02:10:00 +00:00
LTOBackend.cpp
LTOCodeGenerator.cpp	Remove redundant includes from lib/LTO.	2017-12-13 21:30:53 +00:00
LTOModule.cpp	Remove redundant includes from lib/LTO.	2017-12-13 21:30:53 +00:00
ThinLTOCodeGenerator.cpp	Move the stripping of invalid debug info from the Verifier to AutoUpgrade.	2017-10-02 18:31:29 +00:00
UpdateCompilerUsed.cpp	Remove redundant includes from lib/LTO.	2017-12-13 21:30:53 +00:00