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 middle-end/108992] Regression: Branch direction canonicalization leads to pointless tail duplication / CSE/sinking by inverting branch Date: Thu, 02 Mar 2023 22:54:43 +0000 [thread overview] Message-ID: <bug-108992-4-eVRyAEdVc1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108992-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108992 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note I filed PR 108997 for what seems like the wrong heurstic for the prediction.
next prev parent reply other threads:[~2023-03-02 22:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-02 17:12 [Bug rtl-optimization/108992] New: " nok.raven at gmail dot com 2023-03-02 19:23 ` [Bug rtl-optimization/108992] " pinskia at gcc dot gnu.org 2023-03-02 19:48 ` nok.raven at gmail dot com 2023-03-02 22:37 ` pinskia at gcc dot gnu.org 2023-03-02 22:46 ` [Bug middle-end/108992] " pinskia at gcc dot gnu.org 2023-03-02 22:54 ` pinskia at gcc dot gnu.org [this message] 2023-03-02 23:24 ` nok.raven at gmail dot com 2023-03-02 23:35 ` pinskia at gcc dot gnu.org 2023-03-02 23:39 ` 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-108992-4-eVRyAEdVc1@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).