public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/51041] g++ strange optimisation behaviour
Date: Tue, 08 Nov 2011 22:31:00 -0000	[thread overview]
Message-ID: <bug-51041-4-hDx4i6hZSE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51041-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization, ra
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-11-08
          Component|other                       |rtl-optimization
     Ever Confirmed|0                           |1

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-11-08 22:31:08 UTC ---
.L10:
    movsd    (%rbx,%rdx,8), %xmm0
    mulsd    0(%rbp,%rdx,8), %xmm0
    addq    $1, %rdx
    cmpq    $10000, %rdx
    addsd    %xmm0, %xmm2
    jne    .L10

vs:
.L10:
    movsd    (%rbx,%rdx,8), %xmm0
    mulsd    0(%rbp,%rdx,8), %xmm0
    addq    $1, %rdx
    cmpq    $10000, %rdx
    addsd    (%rsp), %xmm0
    movsd    %xmm0, (%rsp)
    jne    .L10

With -fno-exceptions I get the RA to act better again.


  parent reply	other threads:[~2011-11-08 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 22:21 [Bug other/51041] New: " fb.programming at gmail dot com
2011-11-08 22:23 ` [Bug other/51041] " fb.programming at gmail dot com
2011-11-08 22:31 ` pinskia at gcc dot gnu.org [this message]
2023-07-07 15:13 ` [Bug rtl-optimization/51041] register allocation of SSE register in loop with across eh edges vmakarov 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-51041-4-hDx4i6hZSE@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).