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 tree-optimization/96688] Failure to optimize shift-right/add+bitwise not of constant to avoid bitwise not Date: Thu, 14 Jan 2021 11:51:13 +0000 [thread overview] Message-ID: <bug-96688-4-1vCqD0pJNB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96688 --- Comment #5 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:8f8762a2e8659c1db802ba001869085c1915498f commit r11-6663-g8f8762a2e8659c1db802ba001869085c1915498f Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Jan 14 12:50:33 2021 +0100 match.pd: Optimize ~(X >> Y) to ~X >> Y if ~X can be simplified [PR96688] This patch optimizes two GIMPLE operations into just one. As mentioned in the PR, there is some risk this might create more expensive constants, but sometimes it will make them on the other side less expensive, it really depends on the exact value. And if it is an important issue, we should do it in md or during expansion. 2021-01-14 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/96688 * match.pd (~(X >> Y) -> ~X >> Y): New simplification if ~X can be simplified. * gcc.dg/tree-ssa/pr96688.c: New test. * gcc.dg/tree-ssa/reassoc-37.c: Adjust scan-tree-dump regex. * gcc.target/i386/pr66821.c: Likewise.
next prev parent reply other threads:[~2021-01-14 11:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-18 19:21 [Bug tree-optimization/96688] New: Failure to optimize shift-right+not of constant to avoid not gabravier at gmail dot com 2020-08-18 21:07 ` [Bug tree-optimization/96688] " gabravier at gmail dot com 2020-08-25 10:51 ` [Bug tree-optimization/96688] Failure to optimize shift-right/add+bitwise not of constant to avoid bitwise not rguenth at gcc dot gnu.org 2021-01-13 16:49 ` jakub at gcc dot gnu.org 2021-01-13 18:18 ` jakub at gcc dot gnu.org 2021-01-14 11:51 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-16 8:44 ` jakub at gcc dot gnu.org 2022-11-28 22:04 ` 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-96688-4-1vCqD0pJNB@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).