Revert the 'EnableInitializing' flag. There is debate on whether we should run that pass by default in LTO.

llvm-svn: 154356

1 files changed, 0 insertions, 11 deletions

diff --git a/llvm/tools/lto/LTOCodeGenerator.cpp b/llvm/tools/lto/LTOCodeGenerator.cpp
index 28ede86f212..77c06a655b1 100644
--- a/llvm/tools/lto/LTOCodeGenerator.cpp
+++ b/llvm/tools/lto/LTOCodeGenerator.cpp
@@ -46,9 +46,6 @@
 #include "llvm/ADT/StringExtras.h"
 using namespace llvm;
 
-static cl::opt<bool> EnableInternalizing("enable-internalizing", cl::init(false),
-  cl::desc("Internalize functions during LTO"));
-
 static cl::opt<bool> DisableInline("disable-inlining", cl::init(false),
   cl::desc("Do not run the inliner pass"));
 
@@ -278,14 +275,6 @@ static void findUsedValues(GlobalVariable *LLVMUsed,
 }
 
 void LTOCodeGenerator::applyScopeRestrictions() {
-  // Internalize only if specifically asked for. Otherwise, global symbols which
-  // exist in the final image, but which are used outside of that image
-  // (e.g. bundling) may be removed. This also happens when a function is used
-  // only in inline asm. LLVM doesn't recognize that as a "use", so it could be
-  // stripped.
-  if (!EnableInternalizing)
-    return;
-
   if (_scopeRestrictionsDone) return;
   Module *mergedModule = _linker.getModule();