public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18557] Inefficient code generated by -ftree-vectorize on Alpha
Date: Fri, 13 Jul 2012 13:53:00 -0000	[thread overview]
Message-ID: <bug-18557-4-PADSC3i5iK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-18557-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #13 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-13 13:52:25 UTC ---
At -O3 we now get calls to memset for the original testcase, changing it to
store 1 instead we get

$f..ng:
f:
        .frame $30,0,$26,0
        .prologue 0
        and $16,4,$1
        cmpult $31,$1,$1
        lda $7,64($31)
        addl $31,$1,$2
        mov $31,$22
        beq $2,$L2
        lda $7,63($31)
        lda $22,1($31)
        lda $3,1($31)
        stl $3,0($16)
$L2:
        lda $3,64($31)
        subl $3,$2,$2
        zapnot $2,15,$8
        lda $5,1($31)
        srl $8,1,$6
        sll $5,32,$5
        addl $6,$6,$2
        s4addq $1,$16,$1
        mov $31,$3
        zapnot $6,15,$6
        lda $5,1($5)
        .align 4
$L6:
        addl $3,1,$3
        stq $5,0($1)
        zapnot $3,15,$4
        lda $1,8($1)
        cmpult $4,$6,$4
        bne $4,$L6
        zapnot $2,15,$3
        addl $22,$2,$1
        cmpeq $8,$3,$8
        cpys $f31,$f31,$f31
        subl $7,$2,$2
        bne $8,$L8
        s4addq $1,0,$1
        lda $4,1($31)
        .align 4
$L5:
        addq $16,$1,$3
        subl $2,1,$2
        stl $4,0($3)
        lda $1,4($1)
        bne $2,$L5
$L8:
        ret $31,($26),1
        .end f

which seems to be reasonable.  We still run into the issue that we do
not recognize that the epilogue loop may at most iterate once.  The
vectorizer makes a mess out of induction variables for the prologue/epilogue
loops.  See PR53355 for where I track this general issue.

*** This bug has been marked as a duplicate of bug 53355 ***


  parent reply	other threads:[~2012-07-13 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18557-4@http.gcc.gnu.org/bugzilla/>
2012-07-13  8:54 ` rguenth at gcc dot gnu.org
2012-07-13 13:53 ` rguenth at gcc dot gnu.org [this message]
     [not found] <bug-18557-2744@http.gcc.gnu.org/bugzilla/>
2009-02-03 12:24 ` ubizjak at gmail dot com
2009-02-03 12:25 ` ubizjak at gmail dot com
2009-02-03 12:31 ` ubizjak at gmail dot com
2009-02-03 12:51 ` falk at debian dot org
2004-11-18 23:54 [Bug tree-optimization/18557] New: " falk at debian dot org
2004-11-19  0:04 ` [Bug tree-optimization/18557] " pinskia at gcc dot gnu dot org
2004-11-19  3:42 ` dberlin at dberlin dot org
2004-11-19 10:50 ` giovannibajo at libero dot it
2004-11-19 11:29 ` falk at debian dot org
2004-11-19 14:21 ` pinskia at gcc dot gnu dot org
2004-11-19 18:24 ` dorit at il dot ibm dot com
2004-11-19 20:16 ` falk at debian 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-18557-4-PADSC3i5iK@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).