public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53346] [4.6/4.7/4.8 Regression] Bad vectorization in the proc cptrf2 of rnflow.f90
Date: Thu, 17 May 2012 20:47:00 -0000	[thread overview]
Message-ID: <bug-53346-4-WjdmbboQio@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53346-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Uros Bizjak <ubizjak at gmail dot com> 2012-05-17 20:09:42 UTC ---
Instead of this:

.L228:
    movl    $0, -4(%rdx,%rax,4)
    addq    $1, %rax
    cmpq    %rax, %rsi
    jge    .L228

vectorization generates following:

    movq    %rdx, %rax
    movq    %r9, %r8
    andl    $15, %eax
    shrq    $2, %rax
    negq    %rax
    andl    $3, %eax
    cmpq    %r9, %rax
    cmovbe    %rax, %r8
    cmpq    $6, %r9
    cmovbe    %r9, %r8
    testq    %r8, %r8
    je    .L233
    leaq    1(%r8), %rsi
    movl    $1, %eax
    .p2align 4,,10
    .p2align 3
.L176:
    movl    $0, -4(%rdx,%rax,4)
    addq    $1, %rax
    cmpq    %rsi, %rax
    jne    .L176
    cmpq    %r9, %r8
    je    .L182
.L174:
    movq    %r9, %rbp
    subq    %r8, %rbp
    movq    %rbp, %r11
    shrq    $2, %r11
    leaq    0(,%r11,4), %rbx
    testq    %rbx, %rbx
    je    .L181
    pxor    %xmm0, %xmm0
    leaq    (%rdx,%r8,4), %r8
    xorl    %esi, %esi
    .p2align 4,,10
    .p2align 3
.L183:
    addq    $1, %rsi
    movdqa    %xmm0, (%r8)
    addq    $16, %r8
    cmpq    %rsi, %r11
    ja    .L183
    addq    %rbx, %rax
    cmpq    %rbx, %rbp
    je    .L182
    .p2align 4,,10
    .p2align 3
.L181:
    movl    $0, -4(%rdx,%rax,4)
    addq    $1, %rax
    cmpq    %rax, %r9
    jge    .L181

Whoa.


  parent reply	other threads:[~2012-05-17 20:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 15:44 [Bug tree-optimization/53346] New: " dominiq at lps dot ens.fr
2012-05-15  9:54 ` [Bug tree-optimization/53346] " rguenth at gcc dot gnu.org
2012-05-15 12:55 ` dominiq at lps dot ens.fr
2012-05-17 18:35 ` ubizjak at gmail dot com
2012-05-17 20:47 ` ubizjak at gmail dot com [this message]
2012-05-18 11:49 ` rguenth at gcc dot gnu.org
2012-05-18 14:28 ` rguenth at gcc dot gnu.org
2012-05-18 14:32 ` rguenth at gcc dot gnu.org
2012-05-18 14:49 ` ubizjak at gmail dot com
2012-05-18 14:52 ` dominiq at lps dot ens.fr
2012-05-18 15:13 ` ubizjak at gmail dot com
2012-05-18 17:32 ` ubizjak at gmail dot com
2012-05-18 17:34 ` ubizjak at gmail dot com
2012-05-18 17:46 ` ubizjak at gmail dot com
2012-05-18 17:48 ` ubizjak at gmail dot com
2012-05-18 17:56 ` pinskia at gcc dot gnu.org
2012-05-18 18:27 ` hjl.tools at gmail dot com
2012-05-18 18:27 ` ubizjak at gmail dot com
2012-05-18 19:45 ` dominiq at lps dot ens.fr
2012-05-19 23:50 ` dominiq at lps dot ens.fr
2012-09-07 11:59 ` [Bug target/53346] " rguenth at gcc dot gnu.org
2012-11-14 22:19 ` hubicka at gcc dot gnu.org
2012-11-14 22:38 ` hubicka at gcc dot gnu.org
2012-12-31  9:20 ` [Bug target/53346] [4.6/4.7/4.8 Regression] Bad if conversion in " pinskia at gcc dot gnu.org
2012-12-31  9:41 ` pinskia at gcc dot gnu.org
2022-09-26  3:22 ` cvs-commit at gcc dot gnu.org
2022-09-26  3:24 ` crazylht at gmail dot com

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-53346-4-WjdmbboQio@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).