From c6fbaa97016beb90a7508dd6442c83565c27c241 Mon Sep 17 00:00:00 2001 From: Bill Wendling Date: Mon, 8 Jul 2013 23:23:03 +0000 Subject: Don't run internalize if we're outputing bit-code and not an object file. The problem with running internalize before we're ready to output an object file is that it may change a 'weak' symbol into an internal one, but that symbol could be needed by an external object file --- e.g. with arclite. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@185882 91177308-0d34-0410-b5e6-96231b3b80d8 --- tools/lto/LTOCodeGenerator.cpp | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'tools/lto') diff --git a/tools/lto/LTOCodeGenerator.cpp b/tools/lto/LTOCodeGenerator.cpp index 022a04c..7616aa3 100644 --- a/tools/lto/LTOCodeGenerator.cpp +++ b/tools/lto/LTOCodeGenerator.cpp @@ -130,8 +130,10 @@ bool LTOCodeGenerator::writeMergedModules(const char *path, if (determineTarget(errMsg)) return true; - // mark which symbols can not be internalized - applyScopeRestrictions(); + // Run the verifier on the merged modules. + PassManager passes; + passes.add(createVerifierPass()); + passes.run(*_linker.getModule()); // create output file std::string ErrInfo; -- cgit v1.1