public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65063] New: gcc.dg/vect/vect-double-reduc-6.c FAILs with -O3 -fno-tree-loop-ivcanon -fno-tree-vectorize
Date: Sat, 14 Feb 2015 09:22:00 -0000	[thread overview]
Message-ID: <bug-65063-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65063

            Bug ID: 65063
           Summary: gcc.dg/vect/vect-double-reduc-6.c FAILs with -O3
                    -fno-tree-loop-ivcanon -fno-tree-vectorize
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

Created attachment 34754
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34754&action=edit
reduced testcase

Output (on reduced testcase):
$ gcc -Wall -W testcase.c -O3 -fno-tree-loop-ivcanon -fno-tree-vectorize
$ ./a.out 
Aborted

The assembly code shows:
...
    mov    DWORD PTR out[rip], 0    # out,
    mov    DWORD PTR out[rip+4], 16    # out,
    mov    DWORD PTR out[rip+8], 256    # out,
    mov    DWORD PTR out[rip+12], 16384    # out,
    call    abort    #

out[] = {0, 16, 256, 16384}
but should be
out[] = {0, 16, 256, 4096}

(gdb) p in
$1 = {{0, 0, 0, 0}, {1, 1, 1, 1}, {1, 1, 1, 1}, {1, 1, 1, 1}, {2, 2, 2, 2}, {2,
2, 2, 2}, {2, 2, 2, 2}, {3, 3, 3, 3}}
(gdb) p out
$2 = {0, 16, 256, 16384}

in[] looks fine, also in the assembly

The first dump where "16384" appears is 191r.cse1. This might be the same as
PR63593.

Tested revisions:
r220676 - fail


             reply	other threads:[~2015-02-14  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14  9:22 zsojka at seznam dot cz [this message]
2015-02-14 19:47 ` [Bug tree-optimization/65063] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org
2015-02-16 10:58 ` rguenth at gcc dot gnu.org
2015-02-17 12:03 ` rguenth at gcc dot gnu.org
2015-02-18 13:09 ` rguenth at gcc dot gnu.org
2015-02-18 13:11 ` [Bug tree-optimization/65063] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-02-20  7:32 ` [Bug tree-optimization/65063] [4.8 " rguenth at gcc dot gnu.org
2015-02-25 10:41 ` rguenth at gcc dot gnu.org
2015-02-25 11:13 ` rguenth at gcc dot gnu.org
2015-02-25 11:22 ` rguenth 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-65063-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).