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 target/29256] [4.8/4.9/5/6 regression] loop performance regression
Date: Tue, 19 May 2015 17:51:00 -0000	[thread overview]
Message-ID: <bug-29256-4-004yUiKoUo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29256-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #51 from Jeffrey A. Law <law at redhat dot com> ---
Configure for powerpc-linux-gnuspec target with the --eanble-e500_double
option:


/home/gcc/GIT-2/gcc/configure powerpc-linux-gnuspe --enable-e500_double

Testcase:
# define N      2000000
extern double   a[N],c[N];
void tuned_STREAM_Copy()
{
        int j;
        for (j=0; j<N; j++)
            c[j] = a[j];
}


./cc1 -O3 -funroll-loops -funroll-all-loops -fno-tree-loop-distribute-patterns
j.c -I./ -mspe

Results in:

tuned_STREAM_Copy:
        stwu 1,-16(1)
        lis 7,0x3
        lis 8,c@ha
        lis 10,a@ha
        ori 0,7,0xd090
        evstdd 31,8(1)
        li 9,0
        la 8,c@l(8)
        la 10,a@l(10)
        mtctr 0
.L2:
        evlddx 31,10,9
        addi 7,9,8
        addi 0,9,16
        addi 11,9,24
        addi 3,9,32
        evstddx 31,8,9
        addi 4,9,40
        evlddx 31,10,7
        addi 5,9,48
        addi 6,9,56
        evlddx 12,10,6
        addi 9,9,64
        evstddx 31,8,7
        evlddx 7,10,0
        evstddx 7,8,0
        evlddx 0,10,11
        evstddx 0,8,11
        evlddx 11,10,3
        evstddx 11,8,3
        evlddx 3,10,4
        evstddx 3,8,4
        evlddx 4,10,5
        evstddx 4,8,5
        evstddx 12,8,6
        bdnz .L2
        evldd 31,8(1)
        addi 1,1,16
        blr
        .size   tuned_STREAM_Copy, .-tuned_STREAM_Copy

Which looks to me like ivopts has mucked things up badly.


  parent reply	other threads:[~2015-05-19 17:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29256-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 13:58 ` [Bug middle-end/29256] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-12 12:28 ` [Bug target/29256] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 14:23 ` [Bug target/29256] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 12:25 ` rguenth at gcc dot gnu.org
2013-04-12 15:17 ` [Bug target/29256] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-12-09  4:50 ` law at redhat dot com
2014-06-12 13:45 ` [Bug target/29256] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` [Bug target/29256] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-04-07 17:36 ` law at redhat dot com
2015-04-08  7:20 ` rguenther at suse dot de
2015-05-19 17:51 ` law at redhat dot com [this message]
2015-05-20  2:21 ` [Bug target/29256] [4.8/4.9/5/6 " amker at gcc dot gnu.org
2015-05-20 12:45 ` wschmidt at gcc dot gnu.org
2015-06-23  8:22 ` rguenth at gcc dot gnu.org
2015-06-26 19:59 ` [Bug target/29256] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:29 ` jakub at gcc dot gnu.org
2015-08-11 18:36 ` wschmidt at gcc dot gnu.org
2015-08-12  7:12 ` rguenther at suse dot de
2015-08-12  7:34 ` amker at gcc dot gnu.org
2015-08-12 13:24 ` wschmidt at gcc dot gnu.org
2015-08-13  2:11 ` amker at gcc dot gnu.org
2015-08-13  3:28 ` wschmidt at gcc dot gnu.org
2015-08-13  5:01 ` amker at gcc dot gnu.org
2021-05-14  9:45 ` [Bug target/29256] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:04 ` rguenth at gcc dot gnu.org
2022-05-27  9:33 ` [Bug target/29256] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2023-07-07 10:28 ` [Bug target/29256] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-15  7:57 ` pinskia at gcc dot gnu.org
2023-07-17  8:29 ` rguenth 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-29256-4-004yUiKoUo@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).