public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/19580] [3.4/4.0/4.1/4.2 Regression] missed load/store motion
Date: Sat, 04 Feb 2006 13:52:00 -0000	[thread overview]
Message-ID: <20060204135243.25580.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19580-7958@http.gcc.gnu.org/bugzilla/>



------- Comment #25 from rguenth at gcc dot gnu dot org  2006-02-04 13:52 -------
On the mainline now even g() regresses, probably because of the reassoc pass
rewrite.  Of course on the mainline this is also "fixed" by --param
salias-max-array-elements=6, which makes load/store motion work on the tree
level.
It looks like expand only with

<L0>:;
  r[0] = r[0] + r[1];
  r[1] = r[1] + r[2];
  r[2] = r[2] + r[3];
  r[3] = r[3] + r[4];
  r[4] = r[4] + r[5];
  r[5] = r[5] + r[0];
  ivtmp.63 = ivtmp.63 + 1;
  if (ivtmp.63 != (unsigned int) n.68) goto <L0>; else goto <L2>;

produces RTL that we can optimize to

.L13:
        addl    %edi, %esi
        incl    %ebp
        addl    %ebx, %edi
        addl    %ecx, %ebx
        addl    %edx, %ecx
        addl    %eax, %edx
        addl    %esi, %eax
        cmpl    (%esp), %ebp
        jne     .L13

but not for (mainline)

<L0>:;
  D.1544 = r[1] + r[0];
  r[0] = D.1544;
  r[1] = r[2] + r[1];
  r[2] = r[3] + r[2];
  r[3] = r[4] + r[3];
  r[4] = r[5] + r[4];
  r[5] = D.1544 + r[5];
  n.61 = n.61 - 1;
  if (n.61 != 0) goto <L0>; else goto <L2>;


-- 


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


  parent reply	other threads:[~2006-02-04 13:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19580-7958@http.gcc.gnu.org/bugzilla/>
2005-10-16 22:14 ` [Bug rtl-optimization/19580] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-10-17 10:28 ` uros at kss-loka dot si
2005-10-31  2:34 ` mmitchel at gcc dot gnu dot org
2006-02-03 16:44 ` [Bug rtl-optimization/19580] [3.4/4.0/4.1/4.2 " steven at gcc dot gnu dot org
2006-02-04 13:52 ` rguenth at gcc dot gnu dot org [this message]
2006-02-04 21:30 ` dberlin at gcc dot gnu dot org
2006-02-14 16:48 ` rguenth at gcc dot gnu dot org
2006-02-24  0:25 ` mmitchel at gcc dot gnu dot org
2006-05-25  2:34 ` [Bug rtl-optimization/19580] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org
2007-02-14  9:05 ` [Bug rtl-optimization/19580] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org
2007-04-17  5:53 ` dberlin at gcc dot gnu dot org
2007-04-17  8:22 ` rguenth at gcc dot gnu dot org
2007-09-12 14:44 ` rguenth at gcc dot gnu dot org
2007-09-12 14:49 ` rakdver at gcc dot gnu dot org
2007-09-12 15:09 ` eres at il dot ibm dot com
2007-09-13  4:45 ` eres at il dot ibm dot com
2008-01-23  9:28 ` steven at gcc dot gnu dot org
2008-01-23 10:35 ` rguenth at gcc dot gnu dot org
2008-03-28 13:41 ` [Bug rtl-optimization/19580] [4.1/4.2/4.3 " rguenth at gcc dot gnu dot org
2008-03-28 13:46 ` rguenth at gcc dot gnu dot org
2008-07-04 16:49 ` [Bug rtl-optimization/19580] [4.2/4.3 " jsm28 at gcc dot gnu dot org
2009-03-31 16:46 ` [Bug rtl-optimization/19580] [4.3 " jsm28 at gcc dot gnu dot org
2009-04-22 15:09 ` rguenth at gcc dot gnu dot 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=20060204135243.25580.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).