Peter Collingbourne 0442bd0563 ThinLTO: Do not take into account whether a definition has multiple copies when promoting. ... We currently do not touch a symbol's linkage in the case where a definition has a single copy. However, this code is effectively unnecessary: either the definition is not exported, in which case the internalize phase sets its linkage to internal, or it is exported, in which case we need to promote linkage to weak. Those two cases are already handled by existing code. I believe that the only real functional change here is in the case where we have a single definition which does not prevail (e.g. because the definition in a native object file prevails). In that case we now lower linkage to available_externally following the existing code path for that case. As a result we can remove the isExported function parameter from the thinLTOResolveWeakForLinkerInIndex function. Differential Revision: http://reviews.llvm.org/D21883 llvm-svn: 274784		2016-07-07 18:31:51 +00:00
..
CMakeLists.txt	[ThinLTO] Refactor module loader handling into new LTO file (NFC)	2016-05-23 22:54:06 +00:00
LLVMBuild.txt	libLTO: add a ThinLTOCodeGenerator on the model of LTOCodeGenerator.	2016-03-09 01:37:22 +00:00
LTO.cpp	ThinLTO: Do not take into account whether a definition has multiple copies when promoting.	2016-07-07 18:31:51 +00:00
LTOCodeGenerator.cpp	[UpdateCompilerUsed] API rename and cleanup, suggested by Rafaael.	2016-06-22 19:50:42 +00:00
LTOModule.cpp	Apply most suggestions of clang-tidy's performance-unnecessary-value-param	2016-06-08 19:09:22 +00:00
ThinLTOCodeGenerator.cpp	ThinLTO: Do not take into account whether a definition has multiple copies when promoting.	2016-07-07 18:31:51 +00:00
UpdateCompilerUsed.cpp	[UpdateCompilerUsed] API rename and cleanup, suggested by Rafaael.	2016-06-22 19:50:42 +00:00