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/111679] New: `(~a) | (a ^ b)` is not simplified to `~(a & b)` Date: Tue, 03 Oct 2023 16:11:40 +0000 [thread overview] Message-ID: <bug-111679-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111679 Bug ID: 111679 Summary: `(~a) | (a ^ b)` is not simplified to `~(a & b)` Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization Assignee: pinskia at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Take: ``` int f(int a, int b) { return a | ((~a) ^ b); } int f1(int a, int b) { return (~a) | (a ^ b); // ~(a & b) or (~a) | (~b) } ``` The only difference between these 2 functions is a is bitwise inversed. f is able to be detected and simplified but not f1. I Noticed this while working on PR 111282.
next reply other threads:[~2023-10-03 16:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 16:11 pinskia at gcc dot gnu.org [this message] 2023-10-03 16:11 ` [Bug tree-optimization/111679] " pinskia at gcc dot gnu.org 2023-10-05 4:15 ` pinskia at gcc dot gnu.org 2023-10-09 21:28 ` pinskia at gcc dot gnu.org 2023-10-10 17:27 ` cvs-commit at gcc dot gnu.org 2023-10-10 17:29 ` 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-111679-4@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).