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.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34267 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner
2007-02-14 06:20:04 +00:00
parent d2b7cec527
commit 64f150fa92
4 changed files with 5 additions and 5 deletions

View File

@@ -292,7 +292,7 @@ void *ExecutionEngine::getPointerToGlobal(const GlobalValue *GV) {
const_cast<GlobalVariable *>(dyn_cast<GlobalVariable>(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<ConstantInt>(C)->getZExtValue();
else
assert("Integers with > 64-bits not implemented");
assert(0 && "Integers with > 64-bits not implemented");
break;
}