public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/16447] out of ssa generates bloated code Date: Wed, 29 Sep 2004 20:21:00 -0000 [thread overview] Message-ID: <20040929202130.3688.qmail@sourceware.org> (raw) In-Reply-To: <20040709032906.16447.dann@godzilla.ics.uci.edu> ------- Additional Comments From amacleod at redhat dot com 2004-09-29 20:21 ------- I think the best way to do this is to add a short analysis pass in the out of ssa pass, immediately before we commit the final edge insertions. Take a look at the predecessors of each basic block, and find any edges which have the same set of stmts on it. Commit one of these edges, if it generates a new basic block, simply redirect all the other matching edges to that block, and remove the PENDING_STMTS list for those edges. I've started a basic implementation. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Last reconfirmed|2004-07-09 04:02:25 |2004-09-29 20:21:29 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16447
next prev parent reply other threads:[~2004-09-29 20:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-09 3:29 [Bug tree-optimization/16447] New: " dann at godzilla dot ics dot uci dot edu 2004-07-09 3:30 ` [Bug tree-optimization/16447] " dann at godzilla dot ics dot uci dot edu 2004-07-09 3:57 ` pinskia at gcc dot gnu dot org 2004-07-09 4:02 ` pinskia at gcc dot gnu dot org 2004-09-28 20:12 ` pinskia at gcc dot gnu dot org 2004-09-29 20:21 ` amacleod at redhat dot com [this message] 2004-10-06 12:46 ` cvs-commit at gcc dot gnu dot org 2004-10-06 13:03 ` pinskia at gcc dot gnu dot org 2004-11-02 0:23 ` cvs-commit at gcc dot gnu dot org 2004-11-02 1:29 ` pinskia at gcc dot gnu dot 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=20040929202130.3688.qmail@sourceware.org \ --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).