Mehdi Amini 1a6d8014ee Stop always creating and running an LTO compilation if there is not a single LTO object ... Summary: I assume there was a use case, so maybe this strawman patch will help clarifying if it is legit. In any case the current situation is not legit: a ThinLTO compilation should not trigger an unexpected full LTO compilation. Right now, adding a --save-temps option triggers this and makes the number of output differs. Reviewers: tejohnson Subscribers: pcc, llvm-commits, mehdi_amini Differential Revision: https://reviews.llvm.org/D23600 llvm-svn: 279550		2016-08-23 18:39:12 +00:00
..
CMakeLists.txt	Restore "Resolution-based LTO API."	2016-08-11 14:58:12 +00:00
LLVMBuild.txt	Restore "Resolution-based LTO API."	2016-08-11 14:58:12 +00:00
LTO.cpp	Stop always creating and running an LTO compilation if there is not a single LTO object	2016-08-23 18:39:12 +00:00
LTOBackend.cpp	[ThinLTO] Make sure the Context used for the ThinLTO backend has all the appropriate options	2016-08-23 16:53:34 +00:00
LTOCodeGenerator.cpp	[LTOCodeGenerator] Reduce code duplication. NFCI.	2016-08-23 12:32:57 +00:00
LTOModule.cpp	Move legacy LTO interface headers to legacy/ directory.	2016-07-14 21:21:16 +00:00
ThinLTOCodeGenerator.cpp	[PM] Rework the new PM support for building the ModuleSummaryIndex to	2016-08-19 07:49:19 +00:00
UpdateCompilerUsed.cpp	Move legacy LTO interface headers to legacy/ directory.	2016-07-14 21:21:16 +00:00