public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57468] New: [4.9 Regression] 26% performance drop on important benchmark after r199298.
Date: Thu, 30 May 2013 10:53:00 -0000	[thread overview]
Message-ID: <bug-57468-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57468
           Summary: [4.9 Regression] 26% performance drop on important
                    benchmark after r199298.
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ysrumyan at gmail dot com

We found significant performance drop after changes in lra phase, which can be
demonstrated on example from 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55342

I will attach test-case.
And we can see that redundant spill/reload was generated for inner loop that
leads to performance degradation:

.L4:
    movl    %esi, %edx
    addl    $4, %eax
    subl    %edx, %ebx
    subl    %edx, %ecx
    movzbl    (%esp), %edx
    movb    %cl, -3(%eax)
    movl    %esi, %ecx
    movl    %esi, (%esp)  <<-- redundant spill
    movb    %bl, -4(%eax)
    movzbl    (%esp), %ebx  <<-- redundant fill
    subl    %ecx, %edx
    movb    %dl, -2(%eax)
    cmpl    %ebp, 4(%esp)
    movb    %bl, -1(%eax)
    je    .L1


             reply	other threads:[~2013-05-30 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 10:53 ysrumyan at gmail dot com [this message]
2013-05-30 10:55 ` [Bug rtl-optimization/57468] " ysrumyan at gmail dot com
2013-06-06 15:14 ` vmakarov at gcc dot gnu.org
2013-06-08 17:17 ` izamyatin at gmail dot com
2013-06-12  8:09 ` jakub 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-57468-4@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).