forked from OSchip/llvm-project
[Constant] remove fdiv and frem from canTrap()
Assuming the default FP env, we should not treat fdiv and frem any differently in terms of trapping behavior than any other FP op. Ie, FP ops do not trap with the default FP env. This matches how we treat the fdiv/frem in IR with isSafeToSpeculativelyExecute() and in the backend after: https://reviews.llvm.org/rL279970 llvm-svn: 279973
This commit is contained in:
parent
20f02b271b
commit
25475bcc0c
|
@ -347,10 +347,8 @@ static bool canTrapImpl(const Constant *C,
|
|||
return false;
|
||||
case Instruction::UDiv:
|
||||
case Instruction::SDiv:
|
||||
case Instruction::FDiv:
|
||||
case Instruction::URem:
|
||||
case Instruction::SRem:
|
||||
case Instruction::FRem:
|
||||
// Div and rem can trap if the RHS is not known to be non-zero.
|
||||
if (!isa<ConstantInt>(CE->getOperand(1)) ||CE->getOperand(1)->isNullValue())
|
||||
return true;
|
||||
|
|
|
@ -48,16 +48,13 @@ bb7:
|
|||
ret i32 927
|
||||
}
|
||||
|
||||
; FIXME: FP ops don't trap by default, so this is safe to hoist.
|
||||
; FP ops don't trap by default, so this is safe to hoist.
|
||||
|
||||
define i32 @tarp(i1 %c) {
|
||||
; CHECK-LABEL: @tarp(
|
||||
; CHECK-NEXT: br i1 %c, label %bb8, label %bb9
|
||||
; CHECK: bb8:
|
||||
; CHECK-NEXT: bb9:
|
||||
; CHECK-NEXT: [[DOT:%.*]] = select i1 fcmp oeq (float fdiv (float 3.000000e+00, float sitofp (i32 ptrtoint (i32* @G to i32) to float)), float 1.000000e+00), i32 42, i32 927
|
||||
; CHECK-NEXT: br label %bb9
|
||||
; CHECK: bb9:
|
||||
; CHECK-NEXT: [[MERGE:%.*]] = phi i32 [ 42, %0 ], [ [[DOT]], %bb8 ]
|
||||
; CHECK-NEXT: [[MERGE:%.*]] = select i1 %c, i32 [[DOT]], i32 42
|
||||
; CHECK-NEXT: ret i32 [[MERGE]]
|
||||
;
|
||||
br i1 %c, label %bb8, label %bb9
|
||||
|
|
Loading…
Reference in New Issue