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/61511] New: [4.10 Regression] ICE: in vect_can_force_dr_alignment_p, at tree-vect-data-refs.c:5320 with -fno-toplevel-reorder -ftree-slp-vectorize
Date: Sun, 15 Jun 2014 10:18:00 -0000	[thread overview]
Message-ID: <bug-61511-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61511
           Summary: [4.10 Regression] ICE: in
                    vect_can_force_dr_alignment_p, at
                    tree-vect-data-refs.c:5320 with -fno-toplevel-reorder
                    -ftree-slp-vectorize
           Product: gcc
           Version: 4.10.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 32941
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32941&action=edit
reduced testcase

Compiler output:
$ gcc -O -fno-toplevel-reorder -ftree-slp-vectorize testcase.c         
testcase.c: In function 'foo':
testcase.c:8:1: internal compiler error: in vect_can_force_dr_alignment_p, at
tree-vect-data-refs.c:5320
 foo (void)
 ^
0x1408ca1 vect_can_force_dr_alignment_p(tree_node const*, unsigned int)
        /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:5320
0x1409871 vect_compute_data_ref_alignment
        /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:723
0x1409871 vect_compute_data_refs_alignment
        /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:809
0x1409871 vect_analyze_data_refs_alignment(_loop_vec_info*, _bb_vec_info*)
        /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:1978
0xd5c5b8 vect_slp_analyze_bb_1
        /mnt/svn/gcc-trunk/gcc/tree-vect-slp.c:2132
0xd5c5b8 vect_slp_analyze_bb(basic_block_def*)
        /mnt/svn/gcc-trunk/gcc/tree-vect-slp.c:2266
0xd5ea12 execute
        /mnt/svn/gcc-trunk/gcc/tree-vectorizer.c:629
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r211670 - ICE
r211489 - OK
4_9 r211338 - OK


             reply	other threads:[~2014-06-15 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15 10:18 zsojka at seznam dot cz [this message]
2014-06-16  8:14 ` [Bug tree-optimization/61511] " jakub at gcc dot gnu.org
2014-06-16  8:28 ` hubicka at gcc dot gnu.org
2014-09-20  3:44 ` [Bug tree-optimization/61511] [5 " hubicka 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-61511-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).