From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: richard.sandiford@arm.com
Subject: [PATCH] Reduce multiple_of_p uses
Date: Mon, 24 Jan 2022 15:45:33 +0100 (CET) [thread overview]
Message-ID: <20220124144534.28ADC13BA5@imap2.suse-dmz.suse.de> (raw)
There are a few cases where we know we're dealing with (poly-)integer
constants, so remove the use of multiple_of_p in those cases to make
the PR100499 fix less impactful.
Bootstrapped and tested on x86_64-unknown-linux-gnu.
OK?
Thanks,
Richard.
2022-01-24 Richard Biener <rguenther@suse.de>
PR tree-optimization/100499
* tree-cfg.cc (verify_gimple_assign_ternary): Use multiple_p
on poly-ints instead of multiple_of_p.
* tree-ssa.cc (maybe_rewrite_mem_ref_base): Likewise.
(non_rewritable_mem_ref_base): Likewise.
(non_rewritable_lvalue_p): Likewise.
(execute_update_addresses_taken): Likewise.
---
gcc/tree-cfg.cc | 3 ++-
gcc/tree-ssa.cc | 18 +++++++++---------
2 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/gcc/tree-cfg.cc b/gcc/tree-cfg.cc
index 77178a6bf69..2340cd7cef0 100644
--- a/gcc/tree-cfg.cc
+++ b/gcc/tree-cfg.cc
@@ -4410,7 +4410,8 @@ verify_gimple_assign_ternary (gassign *stmt)
TREE_TYPE (rhs2_type))
&& multiple_p (TYPE_VECTOR_SUBPARTS (rhs1_type),
TYPE_VECTOR_SUBPARTS (rhs2_type))
- && multiple_of_p (bitsizetype, rhs3, TYPE_SIZE (rhs2_type)))))
+ && multiple_p (wi::to_poly_offset (rhs3),
+ wi::to_poly_offset (TYPE_SIZE (rhs2_type))))))
{
error ("not allowed type combination in %qs", code_name);
debug_generic_expr (rhs1_type);
diff --git a/gcc/tree-ssa.cc b/gcc/tree-ssa.cc
index 613ab05d557..8fe0682981d 100644
--- a/gcc/tree-ssa.cc
+++ b/gcc/tree-ssa.cc
@@ -1417,8 +1417,8 @@ maybe_rewrite_mem_ref_base (tree *tp, bitmap suitable_for_renaming)
if (TREE_CODE (TREE_TYPE (sym)) == VECTOR_TYPE
&& useless_type_conversion_p (TREE_TYPE (*tp),
TREE_TYPE (TREE_TYPE (sym)))
- && multiple_of_p (sizetype, TREE_OPERAND (*tp, 1),
- TYPE_SIZE_UNIT (TREE_TYPE (*tp))))
+ && multiple_p (mem_ref_offset (*tp),
+ wi::to_poly_offset (TYPE_SIZE_UNIT (TREE_TYPE (*tp)))))
{
*tp = build3 (BIT_FIELD_REF, TREE_TYPE (*tp), sym,
TYPE_SIZE (TREE_TYPE (*tp)),
@@ -1504,8 +1504,8 @@ non_rewritable_mem_ref_base (tree ref)
&& known_ge (mem_ref_offset (base), 0)
&& known_gt (wi::to_poly_offset (TYPE_SIZE_UNIT (TREE_TYPE (decl))),
mem_ref_offset (base))
- && multiple_of_p (sizetype, TREE_OPERAND (base, 1),
- TYPE_SIZE_UNIT (TREE_TYPE (base))))
+ && multiple_p (mem_ref_offset (base),
+ wi::to_poly_offset (TYPE_SIZE_UNIT (TREE_TYPE (base)))))
return NULL_TREE;
/* For same sizes and zero offset we can use a VIEW_CONVERT_EXPR. */
if (integer_zerop (TREE_OPERAND (base, 1))
@@ -1596,8 +1596,8 @@ non_rewritable_lvalue_p (tree lhs)
&& known_ge (mem_ref_offset (lhs), 0)
&& known_gt (wi::to_poly_offset (TYPE_SIZE_UNIT (TREE_TYPE (decl))),
mem_ref_offset (lhs))
- && multiple_of_p (sizetype, TREE_OPERAND (lhs, 1),
- TYPE_SIZE_UNIT (TREE_TYPE (lhs)))
+ && multiple_p (mem_ref_offset (lhs),
+ wi::to_poly_offset (TYPE_SIZE_UNIT (TREE_TYPE (lhs))))
&& known_ge (wi::to_poly_offset (TYPE_SIZE (TREE_TYPE (decl))),
wi::to_poly_offset (TYPE_SIZE (TREE_TYPE (lhs)))))
{
@@ -1969,9 +1969,9 @@ execute_update_addresses_taken (void)
&& known_gt (wi::to_poly_offset
(TYPE_SIZE_UNIT (TREE_TYPE (sym))),
mem_ref_offset (lhs))
- && multiple_of_p (sizetype,
- TREE_OPERAND (lhs, 1),
- TYPE_SIZE_UNIT (TREE_TYPE (lhs))))
+ && multiple_p (mem_ref_offset (lhs),
+ wi::to_poly_offset
+ (TYPE_SIZE_UNIT (TREE_TYPE (lhs)))))
{
tree val = gimple_assign_rhs1 (stmt);
if (! types_compatible_p (TREE_TYPE (val),
--
2.31.1
next reply other threads:[~2022-01-24 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 14:45 Richard Biener [this message]
2022-01-28 18:03 ` Jeff Law
2022-01-31 8:08 ` Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220124144534.28ADC13BA5@imap2.suse-dmz.suse.de \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).