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/64700] Sink common code through PHI Date: Wed, 21 Jan 2015 09:43:00 -0000 [thread overview] Message-ID: <bug-64700-4-ohCTUa78z8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64700-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64700 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2015-01-21 CC| |rguenth at gcc dot gnu.org Version|unknown |5.0 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Thanks for splitting out ;) Btw, there is also the corresponding PR23286 for code hoisting with a patch implementing that ontop of PRE. I'd say the sinking part should be part of a partial dead code elimination pass (aka SSU-PRE). Note that in some cases you have the choice of sinking or hoisting so pass ordering will then determine what we do in that case.
next prev parent reply other threads:[~2015-01-21 9:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-20 22:01 [Bug tree-optimization/64700] New: " law at redhat dot com 2015-01-21 9:43 ` rguenth at gcc dot gnu.org [this message] 2015-01-21 20:42 ` [Bug tree-optimization/64700] " law at redhat dot com 2021-07-20 2:52 ` pinskia at gcc dot gnu.org 2023-05-08 7:38 ` cvs-commit at gcc dot gnu.org 2023-05-08 7:40 ` pinskia at gcc dot gnu.org 2023-05-15 0:27 ` 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-64700-4-ohCTUa78z8@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).