public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-2091] Fix TYPE_PRECISION use in hashable_expr_equal_p
@ 2023-06-26 11:05 Richard Biener
  0 siblings, 0 replies; only message in thread
From: Richard Biener @ 2023-06-26 11:05 UTC (permalink / raw)
  To: gcc-cvs

https://gcc.gnu.org/g:c3bdee86183b3d84f269e9775b2603f8f8221417

commit r14-2091-gc3bdee86183b3d84f269e9775b2603f8f8221417
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Jun 23 10:06:08 2023 +0200

    Fix TYPE_PRECISION use in hashable_expr_equal_p
    
    While the checks look unnecessary they probably are quick and
    thus done early.  The following avoids using TYPE_PRECISION
    on VECTOR_TYPEs by making the code match the comment which
    talks about precision and signedness.  An alternative would
    be to only retain the ERROR_MARK and TYPE_MODE checks or
    use TYPE_PRECISION_RAW (but I like that least).
    
            * tree-ssa-scopedtables.cc (hashable_expr_equal_p):
            Use element_precision.

Diff:
---
 gcc/tree-ssa-scopedtables.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/tree-ssa-scopedtables.cc b/gcc/tree-ssa-scopedtables.cc
index 528ddf2a2ab..e698ef97343 100644
--- a/gcc/tree-ssa-scopedtables.cc
+++ b/gcc/tree-ssa-scopedtables.cc
@@ -574,7 +574,7 @@ hashable_expr_equal_p (const struct hashable_expr *expr0,
       && (TREE_CODE (type0) == ERROR_MARK
 	  || TREE_CODE (type1) == ERROR_MARK
 	  || TYPE_UNSIGNED (type0) != TYPE_UNSIGNED (type1)
-	  || TYPE_PRECISION (type0) != TYPE_PRECISION (type1)
+	  || element_precision (type0) != element_precision (type1)
 	  || TYPE_MODE (type0) != TYPE_MODE (type1)))
     return false;

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-06-26 11:05 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-26 11:05 [gcc r14-2091] Fix TYPE_PRECISION use in hashable_expr_equal_p 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).