Revert the 'EnableInitializing' flag. There is debate on whether we should run that...
authorBill Wendling <isanbard@gmail.com>
Mon, 9 Apr 2012 23:16:51 +0000 (23:16 +0000)
committerBill Wendling <isanbard@gmail.com>
Mon, 9 Apr 2012 23:16:51 +0000 (23:16 +0000)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154356 91177308-0d34-0410-b5e6-96231b3b80d8

tools/lto/LTOCodeGenerator.cpp

index 28ede86f212b4bf7f2565830a2e3cd9f989e774b..77c06a655b18ebfc3dec6b7fa11f78a625fbbf86 100644 (file)
@@ -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();