public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/96928] Failure to optimize one's complement abs pattern Date: Sun, 16 May 2021 22:10:17 +0000 [thread overview] Message-ID: <bug-96928-4-QZDrMER6JX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96928-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96928 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note while moving this optimization to match-and-simplify I noticed that the gimple produced is: (~a) ^ b But this get changed around to: ~(a ^ b) By PRE latter on. I only noticed this because the testcase is failing as it depends being that.
prev parent reply other threads:[~2021-05-16 22:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-03 18:25 [Bug tree-optimization/96928] New: " gabravier at gmail dot com 2021-01-04 14:55 ` [Bug tree-optimization/96928] " jakub at gcc dot gnu.org 2021-01-05 15:36 ` cvs-commit at gcc dot gnu.org 2021-01-05 15:37 ` jakub at gcc dot gnu.org 2021-05-16 22:10 ` pinskia at gcc dot gnu.org [this message]
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-96928-4-QZDrMER6JX@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).