public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/29256] [4.3/4.4/4.5/4.6 regression] loop performance regression
Date: Wed, 21 Jul 2010 21:51:00 -0000	[thread overview]
Message-ID: <20100721215103.28194.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29256-12262@http.gcc.gnu.org/bugzilla/>



------- Comment #39 from pthaugen at gcc dot gnu dot org  2010-07-21 21:51 -------
(In reply to comment #38)
> 
> .L2:
>         addi 11,8,9216
>         ldx 0,10,9
>         stdx 0,11,9
>         addi 9,9,8
>         bdnz .L2
> 
> and in r161844:
> 
> .L2:
>         ldu 0,8(11)
>         stdu 0,8(9)
>         bdnz .L2
> 
> I'm no expert on powerpc architecture, but 3 instructions versus 5 looks like a
> win to me.  Bit-rotten test case?
> 

The 'addi 11,8,9216' in the first loop is invariant and should be hoisted out
of the loop. Separate issue?

As for the issue of indexed ld/st+addi vs. update-form ld/st. The update forms
are cracked into ld/st+addi which imposes a scheduling restriction on them
(cracked insns start a dispatch group). May not make any difference in this
simple loop, but indexed ld/st+addi may have better scheduling opportunities
were there more insns in the loop.

This testcase also appears to be dependent on -mcpu value. Specifying
-mcpu=power7 the testcase passes (although there's still the issue of invariant
addi in the loop).  And if I change to use -m32, then it only fails for
-mcpu=power6.


-- 


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


      parent reply	other threads:[~2010-07-21 21:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 18:29 [Bug c/29256] New: [4.2.0 performance regression] edmar at freescale dot com
2006-09-27 18:30 ` [Bug c/29256] " edmar at freescale dot com
2006-09-27 18:30 ` edmar at freescale dot com
2006-09-28  3:00 ` [Bug middle-end/29256] [4.2 regression] loop unrolling performance regression pinskia at gcc dot gnu dot org
2006-09-28 11:08 ` rguenth at gcc dot gnu dot org
2006-09-28 11:34 ` rakdver at gcc dot gnu dot org
2006-09-28 13:47 ` pinskia at gcc dot gnu dot org
2006-09-28 14:03 ` rguenth at gcc dot gnu dot org
2006-09-28 14:08 ` pinskia at gcc dot gnu dot org
2006-09-28 14:11 ` rguenth at gcc dot gnu dot org
2006-09-28 14:15 ` rakdver at gcc dot gnu dot org
2006-09-28 14:16 ` [Bug middle-end/29256] [4.2 regression] loop " pinskia at gcc dot gnu dot org
2006-09-28 14:21 ` rakdver at gcc dot gnu dot org
2006-09-28 14:35 ` pinskia at gcc dot gnu dot org
2006-09-28 14:40 ` rakdver at gcc dot gnu dot org
2006-09-28 14:44 ` rakdver at gcc dot gnu dot org
2006-09-28 14:50 ` rakdver at gcc dot gnu dot org
2006-09-28 23:48 ` rakdver at gcc dot gnu dot org
2006-10-01 23:04 ` mmitchel at gcc dot gnu dot org
2006-10-06 19:32 ` rakdver at gcc dot gnu dot org
2007-05-14 21:37 ` [Bug middle-end/29256] [4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-07-20  3:50 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:25 ` mmitchel at gcc dot gnu dot org
2008-01-11  5:16 ` ghazi at gcc dot gnu dot org
2008-01-11  6:04 ` rakdver at kam dot mff dot cuni dot cz
2008-01-12  8:43 ` ghazi at gcc dot gnu dot org
2008-02-01 17:00 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:35 ` [Bug middle-end/29256] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-08-06  6:58 ` cnstar9988 at gmail dot com
2008-08-06 21:52 ` rakdver at gcc dot gnu dot org
2008-08-06 21:55 ` rakdver at gcc dot gnu dot org
2008-08-06 21:57 ` rakdver at gcc dot gnu dot org
2008-08-07  5:03 ` bonzini at gnu dot org
2008-10-29 17:05 ` janis at gcc dot gnu dot org
2009-03-31 19:46 ` [Bug middle-end/29256] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:35 ` rguenth at gcc dot gnu dot org
2010-05-22 18:23 ` [Bug middle-end/29256] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org
2010-07-16 19:14 ` pthaugen at gcc dot gnu dot org
2010-07-18 17:49 ` rguenth at gcc dot gnu dot org
2010-07-21  4:16 ` sandra at codesourcery dot com
2010-07-21  4:17 ` sandra at codesourcery dot com
2010-07-21  4:21 ` sandra at codesourcery dot com
2010-07-21 16:10 ` sandra at codesourcery dot com
2010-07-21 21:51 ` pthaugen 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=20100721215103.28194.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).