Split the Add, Sub, and Mul instruction opcodes into separate
integer and floating-point opcodes, introducing FAdd, FSub, and FMul. For now, the AsmParser, BitcodeReader, and IRBuilder all preserve backwards compatability, and the Core LLVM APIs preserve backwards compatibility for IR producers. Most front-ends won't need to change immediately. This implements the first step of the plan outlined here: http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt llvm-svn: 72897
This commit is contained in:
@@ -104,9 +104,12 @@ static int GetDecodedCastOpcode(unsigned Val) {
|
||||
static int GetDecodedBinaryOpcode(unsigned Val, const Type *Ty) {
|
||||
switch (Val) {
|
||||
default: return -1;
|
||||
case bitc::BINOP_ADD: return Instruction::Add;
|
||||
case bitc::BINOP_SUB: return Instruction::Sub;
|
||||
case bitc::BINOP_MUL: return Instruction::Mul;
|
||||
case bitc::BINOP_ADD:
|
||||
return Ty->isFPOrFPVector() ? Instruction::FAdd : Instruction::Add;
|
||||
case bitc::BINOP_SUB:
|
||||
return Ty->isFPOrFPVector() ? Instruction::FSub : Instruction::Sub;
|
||||
case bitc::BINOP_MUL:
|
||||
return Ty->isFPOrFPVector() ? Instruction::FMul : Instruction::Mul;
|
||||
case bitc::BINOP_UDIV: return Instruction::UDiv;
|
||||
case bitc::BINOP_SDIV:
|
||||
return Ty->isFPOrFPVector() ? Instruction::FDiv : Instruction::SDiv;
|
||||
|
||||
Reference in New Issue
Block a user