public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109986] missing fold (~a | b) ^ a => ~(a & b) Date: Mon, 24 Jul 2023 15:52:13 +0000 [thread overview] Message-ID: <bug-109986-4-ODF8pzdgZ9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109986-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109986 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:2a3556376c69a1fb588dcf25225950575e42784f commit r14-2751-g2a3556376c69a1fb588dcf25225950575e42784f Author: Drew Ross <drross@redhat.com> Date: Mon Jul 24 17:51:28 2023 +0200 match.pd: Implement missed optimization (~X | Y) ^ X -> ~(X & Y) [PR109986] Adds a simplification for (~X | Y) ^ X to be folded into ~(X & Y). Also adds the macro bitwise_equal_p for generic and gimple which returns true iff EXPR1 and EXPR2 have the same value. This helps to reduce the number of nop_converts necessary to match the pattern. PR middle-end/109986 gcc/ChangeLog: * generic-match-head.cc (bitwise_equal_p): New macro. * gimple-match-head.cc (bitwise_equal_p): New macro. (gimple_nop_convert): Declare. (gimple_bitwise_equal_p): Helper for bitwise_equal_p. * match.pd ((~X | Y) ^ X -> ~(X & Y)): New simplification. gcc/testsuite/ChangeLog: * gcc.c-torture/execute/pr109986.c: New test. * gcc.dg/tree-ssa/pr109986.c: New test. Co-authored-by: Jakub Jelinek <jakub@redhat.com>
next prev parent reply other threads:[~2023-07-24 15:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 11:48 [Bug middle-end/109986] New: " vanyacpp at gmail dot com 2023-05-26 11:57 ` [Bug middle-end/109986] " vanyacpp at gmail dot com 2023-05-26 15:12 ` pinskia at gcc dot gnu.org 2023-06-24 22:12 ` vanyacpp at gmail dot com 2023-07-24 15:52 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-28 0:13 ` vanyacpp at gmail dot com 2023-08-01 21:50 ` gabravier at gmail dot com 2023-09-17 6:03 ` pinskia at gcc dot gnu.org
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=bug-109986-4-ODF8pzdgZ9@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).