public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64036] [SH] Evaluate re-enabling scheduling before RA
Date: Sat, 25 Jul 2015 11:21:00 -0000	[thread overview]
Message-ID: <bug-64036-4-OQ9MUQFaox@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64036-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Oleg Endo <olegendo at gcc dot gnu.org> ---
For this test case

static volatile int* const g_0 = (volatile int*)0x1240;
static volatile int* const g_1 = (volatile int*)0x1244;
static volatile int* const g_2 = (volatile int*)0x1248;
static volatile int* const g_3 = (volatile int*)0x124C;

int fun (void)
{
  return *g_0 + *g_1 + *g_2 + *g_3;
}

I'm getting the following with -O2 with AMS (without sched1):
        mov.w   .L2,r1
        mov.l   @r1,r0
        mov.l   @(4,r1),r3
        mov.l   @(8,r1),r2
        mov.l   @(12,r1),r1
        add     r3,r0
        add     r2,r0
        rts     
        add     r1,r0
        .align 1
.L2:
        .short  4672

And with sched1:
        mov.w   .L2,r1
        mov.w   .L3,r2
        mov.l   @r1+,r0
        mov.l   @r1,r1
        mov.l   @r2,r2
        add     r1,r0
        mov.w   .L4,r1
        add     r2,r0
        mov.l   @r1,r1
        rts     
        add     r1,r0
        .align 1
.L2:
        .short  4672
.L3:
        .short  4680
.L4:
        .short  4684

This is one of the cases where sched1 makes things worse.


      parent reply	other threads:[~2015-07-25 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 22:12 [Bug target/64036] New: " olegendo at gcc dot gnu.org
2014-12-21 13:33 ` [Bug target/64036] " olegendo at gcc dot gnu.org
2014-12-21 14:23 ` olegendo at gcc dot gnu.org
2015-07-07 12:44 ` olegendo at gcc dot gnu.org
2015-07-07 12:55 ` olegendo at gcc dot gnu.org
2015-07-07 20:46 ` kkojima at gcc dot gnu.org
2015-07-25 11:21 ` olegendo at gcc dot gnu.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=bug-64036-4-OQ9MUQFaox@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).