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 tree-optimization/112819] rearrange branches to improve code generation Date: Mon, 04 Dec 2023 06:57:22 +0000 [thread overview] Message-ID: <bug-112819-4-nZ1MVpklwx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112819-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112819 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |fkastl at suse dot cz, | |hubicka at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Last reconfirmed| |2023-12-04 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- We don't "re-associate" branches. But we might want to turn if-to-switch into sth that does (relaxing the restriction on the ifs testing the same var). We should have a PHI node with incoming vals predicated by the ifs, free to re-order otherwise. The *a deref might impose some limitations for re-ordering, but we can always handle it last in this case. Might be also interesting to order branches which are predictable earlier. Related to switch-conversion/if-to-switch IMHO.
prev parent reply other threads:[~2023-12-04 6:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-02 1:10 [Bug tree-optimization/112819] New: " pinskia at gcc dot gnu.org 2023-12-04 6:57 ` rguenth at gcc dot gnu.org [this message]
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-112819-4-nZ1MVpklwx@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).