public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-2041] Use element_precision for match.pd arith conversion optimization
@ 2023-06-23 9:23 Richard Biener
0 siblings, 0 replies; only message in thread
From: Richard Biener @ 2023-06-23 9:23 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:1fe09b90f856ba27c3e44dda156b28adb5d4d8ea
commit r14-2041-g1fe09b90f856ba27c3e44dda156b28adb5d4d8ea
Author: Richard Biener <rguenther@suse.de>
Date: Fri Jun 23 10:20:45 2023 +0200
Use element_precision for match.pd arith conversion optimization
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.
Diff:
---
gcc/match.pd | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/match.pd b/gcc/match.pd
index 85d562a531d..48b76e6a051 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -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)))
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-23 9:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-23 9:23 [gcc r14-2041] Use element_precision for match.pd arith conversion optimization Richard Biener
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).