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/61051] Duplicated instructions in both conditional branches Date: Sun, 18 Jul 2021 21:09:48 +0000 [thread overview] Message-ID: <bug-61051-4-J5YVl77a9L@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61051-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61051 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |tree-optimization Status|WAITING |RESOLVED Resolution|--- |FIXED Target Milestone|--- |10.0 Keywords| |missed-optimization --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed on the trunk: x.0_4 = x; if (_3 != x.0_4) goto <bb 5>; [66.00%] else goto <bb 4>; [34.00%] <bb 4> [local count: 195204118]: <bb 5> [local count: 574129753]: # prephitmp_24 = PHI <1(3), 2(4)> r.1_5 = r; pretmp_26 = d; if (r.1_5 > 0) goto <bb 6>; [59.00%] else goto <bb 7>; [41.00%] <bb 6> [local count: 338736556]: f_18 = pretmp_26 + 1; <bb 7> [local count: 574129754]: # f_9 = PHI <f_18(6), pretmp_26(5)> I think it has been fixed in since at least GCC 10 even.
next prev parent reply other threads:[~2021-07-18 21:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-04 4:15 [Bug target/61051] New: " carrot at google dot com 2015-03-25 4:24 ` [Bug target/61051] " msebor at gcc dot gnu.org 2015-03-25 8:45 ` steven at gcc dot gnu.org 2021-07-18 21:09 ` pinskia at gcc dot gnu.org [this message] 2021-07-18 21:12 ` [Bug tree-optimization/61051] " 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-61051-4-J5YVl77a9L@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).