public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/38204] PRE for post dominating expressions Date: Mon, 01 Dec 2008 22:14:00 -0000 [thread overview] Message-ID: <20081201221258.8669.qmail@sourceware.org> (raw) In-Reply-To: <bug-38204-1008@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from steven at gcc dot gnu dot org 2008-12-01 22:12 ------- davidxl, my latest patch to bug 23286 (tree-hoist_v3.diff) makes PRE in tree-ssa-pre.c code-size aware. I have tested this with CSiBE on mips-unknown-elf. Without the patch, code size at -Os with PRE enabled is ~17% larger than -Os without PRE. With the patch, the code size increase with -Os and PRE enabled is 0.2%. With the patch and with tree hoisting enabled at -Os, code size is reduced by just a little less than 1%. With the patch and with tree hoisting enabled at -Os but RTL code hoisting disabled (i.e. the pass in gcse.c), code size is reduced by just a little less than 0.6%. (The RTL pass will be necessary mostly to hoist copies from out-of-ssa, and frame/stack pointer adjustments.) davidxl, if you have some time or someone else with time to play with this further, that'd be much appreciated. I've done my part, but having done the trick, the fun is gone and I have no intention to persue code-size aware PRE further ;-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38204
prev parent reply other threads:[~2008-12-01 22:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-20 17:00 [Bug middle-end/38204] New: " dann at godzilla dot ics dot uci dot edu 2008-11-21 6:43 ` [Bug middle-end/38204] " steven at gcc dot gnu dot org 2008-11-21 16:57 ` dberlin at gcc dot gnu dot org 2008-11-22 0:36 ` davidxl at gcc dot gnu dot org 2008-12-01 22:14 ` steven at gcc dot gnu dot 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=20081201221258.8669.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).