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/27504] x && (x & y) not optimized to x & y Date: Thu, 03 Jun 2021 02:43:32 +0000 [thread overview] Message-ID: <bug-27504-4-28oV8mQEW1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-27504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27504 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2012-01-04 00:00:00 |2021-6-2 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed again. So looking at the IR, it took until PHI-OPT4 to be able to convert it into: <bb 2> [local count: 1073741824]: if (x_3(D) != 0) goto <bb 3>; [50.00%] else goto <bb 4>; [50.00%] <bb 3> [local count: 536870913]: _1 = x_3(D) & 85; _5 = _1 != 0; _6 = (int) _5; <bb 4> [local count: 1073741824]: # iftmp.0_2 = PHI <_6(3), 0(2)>
next parent reply other threads:[~2021-06-03 2:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-27504-4@http.gcc.gnu.org/bugzilla/> 2021-06-03 2:43 ` pinskia at gcc dot gnu.org [this message] 2023-05-05 8:17 ` pinskia at gcc dot gnu.org 2023-10-12 17:56 ` pinskia at gcc dot gnu.org 2023-10-12 18:00 ` pinskia at gcc dot gnu.org 2006-05-08 19:28 [Bug tree-optimization/27504] New: " falk at debian dot org 2006-05-09 6:20 ` [Bug tree-optimization/27504] " pinskia at gcc dot gnu dot org 2006-05-09 8:36 ` rguenth at gcc dot gnu dot 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-27504-4-28oV8mQEW1@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).