public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108370] gcc doesn't merge bitwise-AND if an explicit comparison against 0 is given Date: Wed, 11 Jan 2023 14:04:16 +0000 [thread overview] Message-ID: <bug-108370-4-fwVyL6JnI9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108370-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108370 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-01-11 Ever confirmed|0 |1 Keywords| |missed-optimization Status|UNCONFIRMED |NEW --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- The good case is handled by ifcombine: optimizing bits or bits test to _5 & T != 0 with temporary T = 2 | 1 Merging blocks 2 and 3 <bb 2> [local count: 1073741824]: _5 = bio_4(D)->bi_flags; _8 = _5 & 1; if (_8 != 0) goto <bb 4>; [33.00%] else goto <bb 3>; [67.00%] <bb 3> [local count: 719407025]: _9 = _5 & 2; if (_9 != 0) goto <bb 4>; [50.00%] else goto <bb 5>; [50.00%] <bb 4> [local count: 714038313]: _1 = (int) mark_dirty_6(D); __bio_release_pages (bio_4(D), _1); but the bad case is not handled: <bb 2> [local count: 1073741824]: _6 = bio_4(D)->bi_flags; _5 = (unsigned int) _6; _9 = (_Bool) _6; if (_9 != 0) goto <bb 4>; [33.00%] else goto <bb 3>; [67.00%] <bb 3> [local count: 719407025]: _10 = _5 >> 1; _11 = (_Bool) _10; if (_11 != 0) goto <bb 4>; [50.00%] else goto <bb 5>; [50.00%] <bb 4> [local count: 714038313]: _1 = (int) mark_dirty_7(D); __bio_release_pages (bio_4(D), _1); it looks like some premature optimization triggered (not) there. .original is (good) ;; Function bio_flagged (null) ;; enabled by -tree-original { return ((unsigned int) bio->bi_flags & 1 << bit) != 0; } vs (bad) ;; Function bio_flagged (null) ;; enabled by -tree-original { return ((unsigned int) bio->bi_flags >> bit & 1) != 0; } I suppose one variant is folded after the promotion to bool and one before only.
next prev parent reply other threads:[~2023-01-11 14:04 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-11 13:47 [Bug c/108370] New: " dhowells at redhat dot com 2023-01-11 14:04 ` rguenth at gcc dot gnu.org [this message] 2023-01-11 14:24 ` [Bug c/108370] " rguenth at gcc dot gnu.org 2023-01-11 14:42 ` dhowells at redhat dot com 2023-02-08 20:30 ` [Bug middle-end/108370] " pinskia at gcc dot gnu.org 2023-09-16 22:58 ` pinskia at gcc dot gnu.org 2023-09-16 23:16 ` pinskia at gcc dot gnu.org 2023-09-16 23:48 ` pinskia at gcc dot gnu.org 2023-09-17 0:35 ` 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-108370-4-fwVyL6JnI9@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).