public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/21829] [4.1/4.2 Regression] missed jump threading after unroller
Date: Wed, 22 Mar 2006 14:01:00 -0000 [thread overview]
Message-ID: <20060322140127.7109.qmail@sourceware.org> (raw)
In-Reply-To: <bug-21829-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from law at redhat dot com 2006-03-22 14:01 -------
Subject: Re: [4.1/4.2 Regression] missed jump
threading after unroller
On Wed, 2006-03-22 at 12:14 +0100, Richard Guenther wrote:
> On 3/21/06, Jeffrey A Law <law@redhat.com> wrote:
> > It turns out this specialized PHI optimization pass is as effective
> > as running copy-prop and CCP on PHI nodes after DOM. Better yet, it
> > is a teeny tiny slowdown compared to just running the stripped down
> > copyprop. ie, for an almost unmeasurable slowdown we can do both
> > constant and copy propagation instead of just copy propagation.
>
> This patch caused a compile-time regression from 139s to 143s, resp.
> 192s to 197s (leafify) accounted by increases of operand scan / SSA incremental
> and tree CCP times for compiling tramp3d. Also memory usage during compiling
> went up from 655494 kB to 660626kB (this may be due to the VRP patch, though).
>
> Runtime of tramp3d did not improve but regress slightly (but that
> might be in the
> noise - we'll see).
>
> For this simple cleanup pass can you try updating SSA form manually please?
I'm more than happy to look at it; however, be aware that if you're
seeing increased time in CCP then either you're seeing some truly
bizzarre secondary effect or your testing methodology is suspect.
The patch did not affect CCP. In fact, the changes only affect
passes which run *after* CCP in the optimization pipeline.
Jeff
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21829
next prev parent reply other threads:[~2006-03-22 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-21829-6528@http.gcc.gnu.org/bugzilla/>
2005-10-29 15:52 ` [Bug tree-optimization/21829] [4.1 " pinskia at gcc dot gnu dot org
2005-10-30 23:32 ` pinskia at gcc dot gnu dot org
2006-02-09 3:20 ` [Bug tree-optimization/21829] [4.1/4.2 " law at redhat dot com
2006-02-11 0:59 ` pinskia at gcc dot gnu dot org
2006-02-28 20:39 ` mmitchel at gcc dot gnu dot org
2006-03-21 5:09 ` law at redhat dot com
2006-03-21 5:10 ` law at redhat dot com
2006-03-22 11:14 ` richard dot guenther at gmail dot com
2006-03-22 14:01 ` law at redhat dot com [this message]
2006-03-22 15:06 ` richard dot guenther at gmail dot com
2006-03-22 15:36 ` law at redhat dot com
2006-03-28 19:14 ` law at redhat dot com
2006-03-30 17:15 ` law at redhat dot com
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=20060322140127.7109.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: link
Be 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).