From: Richard Biener <richard.guenther@gmail.com>
To: Andrew Pinski <apinski@marvell.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] Move `~X & X` and `~X | X` over to use bitwise_inverted_equal_p
Date: Wed, 2 Aug 2023 10:04:26 +0200 [thread overview]
Message-ID: <CAFiYyc07Vr9hL5HHakoAYJuGo16VtHaD8sYg_5cLfOdoU4StvQ@mail.gmail.com> (raw)
In-Reply-To: <20230731174606.2132534-1-apinski@marvell.com>
On Mon, Jul 31, 2023 at 7:47 PM Andrew Pinski via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> This is a simple patch to move these 2 patterns over to use
> bitwise_inverted_equal_p. It also allows us to remove 2 other patterns
> which were used on comparisons as they are now handled by
> the original pattern.
>
> OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.
OK.
> gcc/ChangeLog:
>
> * match.pd (`~X & X`, `~X | X`): Move over to
> use bitwise_inverted_equal_p, removing :c as bitwise_inverted_equal_p
> handles that already.
> Remove range test simplifications to true/false as they
> are now handled by these patterns.
> ---
> gcc/match.pd | 28 ++++++----------------------
> 1 file changed, 6 insertions(+), 22 deletions(-)
>
> diff --git a/gcc/match.pd b/gcc/match.pd
> index 74f0a84f31d..7d030262698 100644
> --- a/gcc/match.pd
> +++ b/gcc/match.pd
> @@ -1157,8 +1157,9 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
>
> /* Simplify ~X & X as zero. */
> (simplify
> - (bit_and:c (convert? @0) (convert? (bit_not @0)))
> - { build_zero_cst (type); })
> + (bit_and (convert? @0) (convert? @1))
> + (if (bitwise_inverted_equal_p (@0, @1))
> + { build_zero_cst (type); }))
>
> /* PR71636: Transform x & ((1U << b) - 1) -> x & ~(~0U << b); */
> (simplify
> @@ -1395,8 +1396,9 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
> /* ~x ^ x -> -1 */
> (for op (bit_ior bit_xor)
> (simplify
> - (op:c (convert? @0) (convert? (bit_not @0)))
> - (convert { build_all_ones_cst (TREE_TYPE (@0)); })))
> + (op (convert? @0) (convert? @1))
> + (if (bitwise_inverted_equal_p (@0, @1))
> + (convert { build_all_ones_cst (TREE_TYPE (@0)); }))))
>
> /* x ^ x -> 0 */
> (simplify
> @@ -5994,24 +5996,6 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
> (bit_and:c (ordered @0 @0) (ordered:c@2 @0 @1))
> @2)
>
> -/* Simple range test simplifications. */
> -/* A < B || A >= B -> true. */
> -(for test1 (lt le le le ne ge)
> - test2 (ge gt ge ne eq ne)
> - (simplify
> - (bit_ior:c (test1 @0 @1) (test2 @0 @1))
> - (if (INTEGRAL_TYPE_P (TREE_TYPE (@0))
> - || VECTOR_INTEGER_TYPE_P (TREE_TYPE (@0)))
> - { constant_boolean_node (true, type); })))
> -/* A < B && A >= B -> false. */
> -(for test1 (lt lt lt le ne eq)
> - test2 (ge gt eq gt eq gt)
> - (simplify
> - (bit_and:c (test1 @0 @1) (test2 @0 @1))
> - (if (INTEGRAL_TYPE_P (TREE_TYPE (@0))
> - || VECTOR_INTEGER_TYPE_P (TREE_TYPE (@0)))
> - { constant_boolean_node (false, type); })))
> -
> /* A & (2**N - 1) <= 2**K - 1 -> A & (2**N - 2**K) == 0
> A & (2**N - 1) > 2**K - 1 -> A & (2**N - 2**K) != 0
>
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-08-02 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:46 Andrew Pinski
2023-07-31 17:46 ` [PATCH 2/2] Slightly improve bitwise_inverted_equal_p comparisons Andrew Pinski
2023-08-02 8:04 ` Richard Biener
2023-08-02 8:04 ` Richard Biener [this message]
2023-08-02 8:24 ` [PATCH 1/2] Move `~X & X` and `~X | X` over to use bitwise_inverted_equal_p Jakub Jelinek
2023-08-02 22:11 ` Andrew Pinski
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=CAFiYyc07Vr9hL5HHakoAYJuGo16VtHaD8sYg_5cLfOdoU4StvQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=apinski@marvell.com \
--cc=gcc-patches@gcc.gnu.org \
/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).