mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-06-25 00:24:26 +00:00
assert(0) -> LLVM_UNREACHABLE.
Make llvm_unreachable take an optional string, thus moving the cerr<< out of line. LLVM_UNREACHABLE is now a simple wrapper that makes the message go away for NDEBUG builds. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@75379 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@ -410,7 +410,7 @@ GenericValue JIT::runFunction(Function *F,
|
||||
if (ArgValues.empty()) {
|
||||
GenericValue rv;
|
||||
switch (RetTy->getTypeID()) {
|
||||
default: assert(0 && "Unknown return type for function call!");
|
||||
default: LLVM_UNREACHABLE("Unknown return type for function call!");
|
||||
case Type::IntegerTyID: {
|
||||
unsigned BitWidth = cast<IntegerType>(RetTy)->getBitWidth();
|
||||
if (BitWidth == 1)
|
||||
@ -424,7 +424,7 @@ GenericValue JIT::runFunction(Function *F,
|
||||
else if (BitWidth <= 64)
|
||||
rv.IntVal = APInt(BitWidth, ((int64_t(*)())(intptr_t)FPtr)());
|
||||
else
|
||||
assert(0 && "Integer types > 64 bits not supported");
|
||||
LLVM_UNREACHABLE("Integer types > 64 bits not supported");
|
||||
return rv;
|
||||
}
|
||||
case Type::VoidTyID:
|
||||
@ -439,7 +439,7 @@ GenericValue JIT::runFunction(Function *F,
|
||||
case Type::X86_FP80TyID:
|
||||
case Type::FP128TyID:
|
||||
case Type::PPC_FP128TyID:
|
||||
assert(0 && "long double not supported yet");
|
||||
LLVM_UNREACHABLE("long double not supported yet");
|
||||
return rv;
|
||||
case Type::PointerTyID:
|
||||
return PTOGV(((void*(*)())(intptr_t)FPtr)());
|
||||
@ -467,7 +467,7 @@ GenericValue JIT::runFunction(Function *F,
|
||||
const Type *ArgTy = FTy->getParamType(i);
|
||||
const GenericValue &AV = ArgValues[i];
|
||||
switch (ArgTy->getTypeID()) {
|
||||
default: assert(0 && "Unknown argument type for function call!");
|
||||
default: LLVM_UNREACHABLE("Unknown argument type for function call!");
|
||||
case Type::IntegerTyID:
|
||||
C = ConstantInt::get(AV.IntVal);
|
||||
break;
|
||||
|
Reference in New Issue
Block a user