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/111432] New: `bool & (a|1)` is not optimized to just `bool` Date: Sat, 16 Sep 2023 04:11:36 +0000 [thread overview] Message-ID: <bug-111432-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111432 Bug ID: 111432 Summary: `bool & (a|1)` is not optimized to just `bool` Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- take: ``` int foo3(int c, int bb) { if ((bb & ~3)!=0) __builtin_unreachable(); return (bb & (c|3)); } int foo_bool(int c, _Bool bb) { return (bb & (c|7)); } ``` foo3 should be optimized to just `return bb`, likewise for foo_bool. Note LLVM does this.
next reply other threads:[~2023-09-16 4:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-16 4:11 pinskia at gcc dot gnu.org [this message] 2023-10-10 21:47 ` [Bug tree-optimization/111432] " pinskia at gcc dot gnu.org 2023-10-14 0:57 ` pinskia at gcc dot gnu.org 2023-10-17 16:04 ` cvs-commit at gcc dot gnu.org 2023-10-17 16: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-111432-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).