1: use class instead of MVT
2: minor fix for the comments
This commit is contained in:
@@ -3327,9 +3327,9 @@ def : Pat<(i64 (sext i1:$in)),
|
||||
// FIXME: We should choose either a zext or a sext based on other constants
|
||||
// already around.
|
||||
def : Pat<(i32 (anyext i1:$in)),
|
||||
(SELECT_I4 i1:$in, (LI 1), (LI 0))>;
|
||||
(SELECT_I4 crbitrc:$in, (LI 1), (LI 0))>;
|
||||
def : Pat<(i64 (anyext i1:$in)),
|
||||
(SELECT_I8 i1:$in, (LI8 1), (LI8 0))>;
|
||||
(SELECT_I8 crbitrc:$in, (LI8 1), (LI8 0))>;
|
||||
|
||||
// match setcc on i1 variables.
|
||||
// CRANDC is:
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
; RUN: -ppc-vsr-nums-as-vr -ppc-asm-full-reg-names < %s | FileCheck %s
|
||||
|
||||
;; Note that SETUEQ, SETOGE, SETOLE, SETONE, SETULT and SETUGT should be
|
||||
;; expanded by legalize for floating-point types f32 and f64, so there are no.
|
||||
;; patterns defined in PPCInstrInfo.td file for these setcc patterns.
|
||||
;; expanded by DAG legalizer for floating-point types f32 and f64, so there are
|
||||
;; no patterns defined in PPCInstrInfo.td file for these setcc patterns for now.
|
||||
|
||||
define i1 @fcmp_false(float %a, float %b) {
|
||||
; CHECK-LABEL: fcmp_false:
|
||||
|
||||
Reference in New Issue
Block a user