public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18316] Missed IV optimization
Date: Thu, 08 Nov 2012 23:00:00 -0000	[thread overview]
Message-ID: <bug-18316-4-nW9ZDPueWq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-18316-4@http.gcc.gnu.org/bugzilla/>


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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2010-02-12 21:46:26         |2012-11-08 21:46:26

--- Comment #15 from Steven Bosscher <steven at gcc dot gnu.org> 2012-11-08 22:59:49 UTC ---
Still a missed optimization as of trunk r193340:

strength_test2:
        movl    (%rdi), %ecx
        movl    %ecx, %eax
        .p2align 4,,10
        .p2align 3
.L3:
        movslq  8(%rdi), %rdx
        movl    $2, (%rdi,%rdx,4)
        movl    %eax, %edx
        addl    %ecx, %eax
        cmpl    4(%rdi), %edx
        jl      .L3
        rep ret

strength_result2:
        movl    (%rdi), %ecx
        xorl    %eax, %eax
        .p2align 4,,10
        .p2align 3
.L7:
        movslq  8(%rdi), %rdx
        addl    %ecx, %eax
        movl    $2, (%rdi,%rdx,4)
        cmpl    4(%rdi), %eax
        jl      .L7
        rep ret


       reply	other threads:[~2012-11-08 23:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18316-4@http.gcc.gnu.org/bugzilla/>
2012-11-08 23:00 ` steven at gcc dot gnu.org [this message]
     [not found] <bug-18316-280@http.gcc.gnu.org/bugzilla/>
2007-12-17  8:14 ` steven at gcc dot gnu dot org
2008-09-14  4:03 ` pinskia at gcc dot gnu dot org
2010-02-12 21:46 ` steven at gcc dot gnu dot org
2004-11-06 16:39 [Bug tree-optimization/18316] New: " steven at gcc dot gnu dot org
2004-11-06 17:00 ` [Bug tree-optimization/18316] " pinskia at gcc dot gnu dot org
2005-01-23 14:37 ` steven at gcc dot gnu dot org
2005-01-23 14:58 ` rakdver at gcc dot gnu dot org
2005-01-24  9:12 ` stevenb at suse dot de
2005-01-25 11:35 ` rakdver at gcc dot gnu dot org
2005-01-30 14:41 ` pinskia at gcc dot gnu dot org
2005-02-02  8:56 ` rakdver at gcc dot gnu dot org
2005-02-13  0:11 ` pinskia at gcc dot gnu dot org
2005-04-18  9:33 ` rakdver at gcc dot gnu dot org
2005-05-01  8:08 ` cvs-commit at gcc dot gnu dot org
2005-05-01 13:49 ` pinskia at gcc dot gnu dot org
2005-05-01 13:49 ` pinskia at gcc dot gnu dot org
2005-07-08 18:19 ` pinskia at gcc dot gnu 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-18316-4-nW9ZDPueWq@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).