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/102138] t = a==0 and a = PHI<0, t> should be done earlier than PRE Date: Tue, 31 Aug 2021 07:34:17 +0000 [thread overview] Message-ID: <bug-102138-4-McgzD8M12D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102138-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102138 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2021-08-31 Status|UNCONFIRMED |NEW --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. I attached some propagation through PHI folding for forwprop (WIP) to the spaceship PR. There's also tree-ssa-phiprop.c which does sth like PHI-translation for loads that could be generalized. In general it opens the same issues as PRE - possibly extra copies due to the constants in PHIs and possibly less optimized code because readily available constants (in registers) are explicitely represented and need to be re-materialized.
next prev parent reply other threads:[~2021-08-31 7:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-30 23:52 [Bug tree-optimization/102138] New: " pinskia at gcc dot gnu.org 2021-08-30 23:57 ` [Bug tree-optimization/102138] " pinskia at gcc dot gnu.org 2021-08-31 7:34 ` rguenth at gcc dot gnu.org [this message] 2023-11-02 18:55 ` pinskia at gcc dot gnu.org 2023-11-02 19:00 ` 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-102138-4-McgzD8M12D@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).