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 middle-end/64394] New: ICE: in build_linearized_memory_access, at graphite-interchange.c:121 (isl_constraint.c:558: expecting integer value) with -floop-interchange
Date: Tue, 23 Dec 2014 20:09:00 -0000	[thread overview]
Message-ID: <bug-64394-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64394
           Summary: ICE: in build_linearized_memory_access, at
                    graphite-interchange.c:121 (isl_constraint.c:558:
                    expecting integer value) with -floop-interchange
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

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

Compiler output:
$ gcc -O2 -floop-interchange testcase.c         
/var/tmp/portage/dev-libs/isl-0.12.2/work/isl-0.12.2/isl_constraint.c:558:
expecting integer value
testcase.c: In function 'foo':
testcase.c:10:1: internal compiler error: Aborted
 foo (void)
 ^
0xc5819f crash_signal
        /mnt/svn/gcc-trunk/gcc/toplev.c:359
0x1757f91 build_linearized_memory_access
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:121
0x1757f91 pdr_stride_in_loop
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:207
0x1757f91 memory_strides_in_loop_1
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:293
0x17627d4 lst_interchange_profitable_p
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:410
0x17627d4 lst_try_interchange_loops
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:547
0x17627d4 lst_interchange_select_inner
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:610
0x17655bf lst_interchange_select_outer
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:636
0x176560d lst_interchange_select_outer
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:646
0x176567b scop_do_interchange(scop*)
        /mnt/svn/gcc-trunk/gcc/graphite-interchange.c:658
0x168c65a apply_poly_transforms(scop*)
        /mnt/svn/gcc-trunk/gcc/graphite-poly.c:272
0x1687783 graphite_transform_loops()
        /mnt/svn/gcc-trunk/gcc/graphite.c:302
0x1687db0 graphite_transforms
        /mnt/svn/gcc-trunk/gcc/graphite.c:331
0x1687db0 execute
        /mnt/svn/gcc-trunk/gcc/graphite.c:412
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:
r219043 - ICE


             reply	other threads:[~2014-12-23 20:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 20:09 zsojka at seznam dot cz [this message]
2015-01-29 15:47 ` [Bug middle-end/64394] " jana at saout dot de
2015-02-26  7:43 ` asolokha at gmx dot com
2015-07-17 21:00 ` hiraditya at msn dot com
2015-10-09 14:47 ` spop 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-64394-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).