From 4da5e17cfc5befdfc6f77df2ed8cd3266b73b0e0 Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Wed, 14 Feb 2007 06:20:04 +0000 Subject: From Dan Gohman: While preparing http://llvm.org/PR1198 I noticed several asserts protecting unprepared code from i128 types that weren't actually failing when they should because they were written as assert("foo") instead of something like assert(0 && "foo"). This patch fixes all the cases that a quick grep found. llvm-svn: 34267 --- llvm/lib/ExecutionEngine/ExecutionEngine.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'llvm/lib/ExecutionEngine/ExecutionEngine.cpp') diff --git a/llvm/lib/ExecutionEngine/ExecutionEngine.cpp b/llvm/lib/ExecutionEngine/ExecutionEngine.cpp index 28b515e3faf..f0ba43477df 100644 --- a/llvm/lib/ExecutionEngine/ExecutionEngine.cpp +++ b/llvm/lib/ExecutionEngine/ExecutionEngine.cpp @@ -292,7 +292,7 @@ void *ExecutionEngine::getPointerToGlobal(const GlobalValue *GV) { const_cast(dyn_cast(GV))) EmitGlobalVariable(GVar); else - assert("Global hasn't had an address allocated yet!"); + assert(0 && "Global hasn't had an address allocated yet!"); return state.getGlobalAddressMap(locked)[GV]; } @@ -425,7 +425,7 @@ GenericValue ExecutionEngine::getConstantValue(const Constant *C) { else if (BitWidth <= 64) Result.Int64Val = (uint64_t )cast(C)->getZExtValue(); else - assert("Integers with > 64-bits not implemented"); + assert(0 && "Integers with > 64-bits not implemented"); break; } -- cgit v1.2.3