public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chrbr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39423] [4.6/4.7/4.8 Regression] [SH]  performance regression: lost mov @(disp,Rn)
Date: Wed, 11 Jul 2012 15:24:00 -0000	[thread overview]
Message-ID: <bug-39423-4-jb7W0wgIgz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39423-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39423

--- Comment #19 from chrbr at gcc dot gnu.org 2012-07-11 15:24:27 UTC ---
(In reply to comment #18)
> (In reply to comment #17)
> > Created attachment 27775 [details]
> > plus add combine
> > 
> > Here is the patch that I've been running since some time, it also use the same
> > combine pattern matcher, but the goal of this patch was originally to fix up
> > chains of multiple mult-add instructions.
> > Optimizing the cst+reg addressing mode appears as a nice effects. Out of range
> > indexes seems to be handled as afar as I can see.
> > 
> > This brings a EEMBC telecom speedup of 10%.FFMPEG code size reduced to 30% on a
> > few objects. 
> > Validated on whole linux distribution, with only improvements (few regression
> > only bellow noise).
> 
> Interesting.  
> BTW, do you happen to have any (runtime) numbers for GCC 4.7.x vs current GCC
> 4.8?
> 

for now I only track the 4.6 and 4.7 branches. the 4.8 is moving too fast, but
I could easily cheery-pick your the other SH changes (like your fix for
PR53911) 

btw I only bench on the SH4 and SH4A.

> > This patch is only for comments/illustration. Need a few polishing before
> > proposing. I'm having a look at your implementation to see how they compare and
> > possibly combined together. Both approaches look interesting.
> 
> I guess folding the mul-add sequences like you did should be more useful than
> just
> handling one mem:SI pattern.  In any case, if you find my impl useful please
> let me know,
> because then I'd also pop in patterns for mem:QI and mem:HI patterns.

sure. by the way, my patch is not complete to fix the original problem. I need
to extract other chunks that unleash it. Will post.


  parent reply	other threads:[~2012-07-11 15:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-39423-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 13:49 ` [Bug target/39423] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 14:29 ` [Bug target/39423] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 13:58 ` [Bug target/39423] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-07-06 22:04 ` olegendo at gcc dot gnu.org
2012-07-11  9:05 ` chrbr at gcc dot gnu.org
2012-07-11 12:35 ` chrbr at gcc dot gnu.org
2012-07-11 15:09 ` olegendo at gcc dot gnu.org
2012-07-11 15:24 ` chrbr at gcc dot gnu.org [this message]
2012-07-12 15:37 ` chrbr at gcc dot gnu.org
2012-07-13  9:36 ` olegendo at gcc dot gnu.org
2012-07-30  6:48 ` olegendo at gcc dot gnu.org
2012-08-09 15:58 ` olegendo at gcc dot gnu.org
2012-08-09 16:55 ` olegendo at gcc dot gnu.org
2012-08-09 22:44 ` kkojima at gcc dot gnu.org
2012-08-10  8:09 ` chrbr at gcc dot gnu.org
2012-08-10 12:27 ` olegendo at gcc dot gnu.org
2012-08-10 13:15 ` rmansfield at qnx dot com
2012-08-10 13:27 ` olegendo at gcc dot gnu.org
2012-08-10 13:37 ` rmansfield at qnx dot com
2012-08-12 13:23 ` olegendo at gcc dot gnu.org
2012-08-16 23:17 ` olegendo at gcc dot gnu.org
2012-08-21 23:35 ` olegendo at gcc dot gnu.org
2012-08-29 19:06 ` olegendo at gcc dot gnu.org
2013-04-12 15:21 ` [Bug target/39423] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-06-23 14:55 ` olegendo at gcc dot gnu.org
2014-06-12 13:45 ` [Bug target/39423] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:39 ` [Bug target/39423] [4.8/4.9/5 " jakub at gcc dot gnu.org
2014-12-21 17:29 ` olegendo 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-39423-4-jb7W0wgIgz@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: 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).