From 64fae7587ad7cb8082ca5615fd061a4e4d3f711e Mon Sep 17 00:00:00 2001 From: Bill Wendling Date: Mon, 9 Apr 2012 23:16:51 +0000 Subject: [PATCH] Revert the 'EnableInitializing' flag. There is debate on whether we should run that pass by default in LTO. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154356 91177308-0d34-0410-b5e6-96231b3b80d8 --- tools/lto/LTOCodeGenerator.cpp | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/tools/lto/LTOCodeGenerator.cpp b/tools/lto/LTOCodeGenerator.cpp index 28ede86f212..77c06a655b1 100644 --- a/tools/lto/LTOCodeGenerator.cpp +++ b/tools/lto/LTOCodeGenerator.cpp @@ -46,9 +46,6 @@ #include "llvm/ADT/StringExtras.h" using namespace llvm; -static cl::opt EnableInternalizing("enable-internalizing", cl::init(false), - cl::desc("Internalize functions during LTO")); - static cl::opt 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();