summaryrefslogtreecommitdiffstats
path: root/llvm/lib
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@gmail.com>2017-01-13 06:26:18 +0000
committerCraig Topper <craig.topper@gmail.com>2017-01-13 06:26:18 +0000
commiteec489034699f45f6ff236e74b27989a0d0d507f (patch)
tree7717ce1f07c679af69f8ba198d195741e787653d /llvm/lib
parentd409411ef195329a24cea00589e9853ab6a5ace8 (diff)
downloadbcm5719-llvm-eec489034699f45f6ff236e74b27989a0d0d507f.tar.gz
bcm5719-llvm-eec489034699f45f6ff236e74b27989a0d0d507f.zip
[IR] Don't call assertModuleIsMaterialized in release builds
Summary: To fix a release vs debug build linking error, r259695 made the body of assertModuleIsMaterialized empty if Value.cpp gets compiled in a release build. This way any code compiled as a debug build can still link against a release version of the function. This patch takes this a step farther and removes all calls to it from Value.h in any code that includes it in a relase build. This shrinks the opt binary on my macbook build by 17240 bytes. Reviewers: rafael Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D28191 llvm-svn: 291883
Diffstat (limited to 'llvm/lib')
-rw-r--r--llvm/lib/IR/Value.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/lib/IR/Value.cpp b/llvm/lib/IR/Value.cpp
index 91a999b5800..d86d7fc1164 100644
--- a/llvm/lib/IR/Value.cpp
+++ b/llvm/lib/IR/Value.cpp
@@ -320,7 +320,7 @@ void Value::takeName(Value *V) {
ST->reinsertValue(this);
}
-void Value::assertModuleIsMaterialized() const {
+void Value::assertModuleIsMaterializedImpl() const {
#ifndef NDEBUG
const GlobalValue *GV = dyn_cast<GlobalValue>(this);
if (!GV)
OpenPOWER on IntegriCloud