]> git.ipfire.org Git - thirdparty/gcc.git/commitdiff
Use element_precision for match.pd arith conversion optimization
authorRichard Biener <rguenther@suse.de>
Fri, 23 Jun 2023 08:20:45 +0000 (10:20 +0200)
committerRichard Biener <rguenther@suse.de>
Fri, 23 Jun 2023 09:22:38 +0000 (11:22 +0200)
The simplification (outertype)((innertype0)a+(innertype1)b) to
((newtype)a+(newtype)b) ends up using TYPE_PRECISION to check
whether it can elide a conversion but in some paths there can
be VECTOR_TYPEs where this instead compares the number of lanes.
The following fixes the missed optimizations and uses
element_precision in those places.

* match.pd ((outertype)((innertype0)a+(innertype1)b)
-> ((newtype)a+(newtype)b)): Use element_precision
where appropriate.

gcc/match.pd

index 85d562a531d2af2f019eb78a926424e1c3880435..48b76e6a05105accf752479f741eac2e5a044d41 100644 (file)
@@ -7428,9 +7428,9 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
              && newtype == type
              && types_match (newtype, type))
            (op (convert:newtype @1) (convert:newtype @2))
-           (with { if (TYPE_PRECISION (ty1) > TYPE_PRECISION (newtype))
+           (with { if (element_precision (ty1) > element_precision (newtype))
                      newtype = ty1;
-                   if (TYPE_PRECISION (ty2) > TYPE_PRECISION (newtype))
+                   if (element_precision (ty2) > element_precision (newtype))
                      newtype = ty2; }
               /* Sometimes this transformation is safe (cannot
                  change results through affecting double rounding
@@ -7453,9 +7453,9 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
                  exponent range for the product or ratio of two
                  values representable in the TYPE to be within the
                  range of normal values of ITYPE.  */
-             (if (TYPE_PRECISION (newtype) < TYPE_PRECISION (itype)
+             (if (element_precision (newtype) < element_precision (itype)
                   && (flag_unsafe_math_optimizations
-                      || (TYPE_PRECISION (newtype) == TYPE_PRECISION (type)
+                      || (element_precision (newtype) == element_precision (type)
                           && real_can_shorten_arithmetic (TYPE_MODE (itype),
                                                           TYPE_MODE (type))
                           && !excess_precision_type (newtype)))