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/101139] Unable to remove double byteswap in fast path Date: Sun, 20 Jun 2021 09:41:21 +0000 [thread overview] Message-ID: <bug-101139-4-EudYCJY3BL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101139-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101139 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-06-20 Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org Depends on| |13563 Status|UNCONFIRMED |ASSIGNED Keywords| |missed-optimization Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- if (b_13 < h.0_15) goto <bb 4>; [51.12%] else goto <bb 5>; [48.88%] <bb 4> [local count: 548896825]: _16 = (short unsigned int) f$ab_14; _17 = (int) _16; _18 = __builtin_bswap16 (_17); goto <bb 6>; [100.00%] <bb 5> [local count: 524845000]: k_22 = i (); c.1_23 = (short unsigned int) k_22; _24 = (int) c.1_23; _25 = __builtin_bswap16 (_24); <bb 6> [local count: 1073741824]: # prephitmp_32 = PHI <_18(4), _25(5)> Basically the same issue as PR 13563. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13563 [Bug 13563] if-conversion not agressive enough
next prev parent reply other threads:[~2021-06-20 9:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-20 9:37 [Bug tree-optimization/101139] New: " steinar+gcc at gunderson dot no 2021-06-20 9:41 ` pinskia at gcc dot gnu.org [this message] 2021-06-20 9:48 ` [Bug tree-optimization/101139] " pinskia at gcc dot gnu.org 2021-06-21 6:37 ` rguenth at gcc dot gnu.org 2021-06-26 16:51 ` steinar+gcc at gunderson dot no 2024-04-20 7:25 ` 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-101139-4-EudYCJY3BL@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).