From: Dale Johannesen <dalej@apple.com>
To: Richard Henderson <rth@redhat.com>
Cc: Dale Johannesen <dalej@apple.com>,
gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Another performance regression
Date: Fri, 27 Sep 2002 16:09:00 -0000 [thread overview]
Message-ID: <0840120E-D266-11D6-BBCF-000393D76DAA@apple.com> (raw)
In-Reply-To: <20020926222640.GF7332@redhat.com>
On Thursday, September 26, 2002, at 03:26 PM, Richard Henderson wrote:
> On Thu, Sep 26, 2002 at 12:01:38PM -0700, Dale Johannesen wrote:
>> So should I fix this by making the unrolling code smarter, in effect
>> doing cse's job?
>
> I think so, since the change to loop unrolling order was
> also done to get around a performance regression. :-/
>
>> It seems likely Roger Sayle's approach of running
>> gcse after loop opts would Just Work. Is that going to go in?
>
> Not for 3.3.
>
> The following appears to do the job. Would you see if this
> causes any other problems?
Thanks!
Bootstrapped and tested on Darwin (C, C++, ObjC, f77), no regressions.
prev parent reply other threads:[~2002-09-27 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 12:16 Dale Johannesen
2002-09-26 16:07 ` Richard Henderson
2002-09-27 16:09 ` Dale Johannesen [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=0840120E-D266-11D6-BBCF-000393D76DAA@apple.com \
--to=dalej@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/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).