public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "izamyatin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50962] New: Additional opportunity for AGU stall avoidance optimization for Atom processor
Date: Wed, 02 Nov 2011 12:00:00 -0000	[thread overview]
Message-ID: <bug-50962-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50962
           Summary: Additional opportunity for AGU stall avoidance
                    optimization for Atom processor
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: izamyatin@gmail.com


We have now following code for attached testcase:

foo:
.LFB0:
        .cfi_startproc
        movl    4(%esp), %eax
        testl   %eax, %eax
        je      .L4
        xorl    %ecx, %ecx
        jmp     .L3
        .p2align 4,,7
        .p2align 3
.L5:
        movl    %eax, %ecx
        movl    %edx, %eax
.L3:
        movl    (%eax), %edx <--- AGU stall here on Atom since eax produced on
previous cycle. We should use lea in previous instruction.
        movl    %ecx, (%eax)
        testl   %edx, %edx
        jne     .L5
        ret
.L4:
        xorl    %eax, %eax
        ret
        .cfi_endproc

 So we can use lea before movl (%eax), %edx which is better for Atom.


             reply	other threads:[~2011-11-02 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 12:00 izamyatin at gmail dot com [this message]
2011-11-02 12:01 ` [Bug target/50962] " izamyatin at gmail dot com
2011-11-02 13:06 ` enkovich.gnu at gmail dot com
2011-11-02 13:06 ` enkovich.gnu at gmail dot com
2011-11-07  8:47 ` kyukhin at gcc dot gnu.org
2011-12-15  0:29 ` pinskia at gcc dot gnu.org
2011-12-15  4:53 ` izamyatin at gmail dot com
2013-05-14  2:25 ` dirtyepic at gentoo 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=bug-50962-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).