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/51684] New: [4.7 Regression]: ICE in gfortran.dg/maxloc_bounds_5 on ia64
Date: Tue, 27 Dec 2011 11:39:00 -0000	[thread overview]
Message-ID: <bug-51684-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51684
           Summary: [4.7 Regression]: ICE in gfortran.dg/maxloc_bounds_5
                    on ia64
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ubizjak@gmail.com


A problem in SLP vectorizer, can be triggered with a cross:

$ ~/gcc-build-xxx/gcc/f951 -O3 -quiet maxloc_bounds_5.f90
maxloc_bounds_5.f90: In function ‘foo’:
maxloc_bounds_5.f90:6:0: internal compiler error: in gsi_for_stmt, at
gimple-iterator.c:560
Please submit a full bug report,
[...]

(gdb) bt
#0  internal_error (gmsgid=0xdfea45 "in %s, at %s:%d") at
../../gcc-svn/trunk/gcc/diagnostic.c:839
#1  0x0000000000c462f4 in fancy_abort (file=<optimized out>, line=560,
function=0xcf3913 "gsi_for_stmt")
    at ../../gcc-svn/trunk/gcc/diagnostic.c:899
#2  0x000000000074885c in gsi_for_stmt (stmt=0x7ffff14724b0) at
../../gcc-svn/trunk/gcc/gimple-iterator.c:560
#3  0x0000000000a62372 in vect_schedule_slp_instance (node=0x13ad400,
instance=0x13b71e0, vectorization_factor=<optimized out>)
    at ../../gcc-svn/trunk/gcc/tree-vect-slp.c:2888
#4  0x0000000000a68fa9 in vect_schedule_slp (loop_vinfo=<optimized out>,
bb_vinfo=<optimized out>)
    at ../../gcc-svn/trunk/gcc/tree-vect-slp.c:2970
#5  0x0000000000a5bc24 in vect_transform_loop (loop_vinfo=0x13b97d0) at
../../gcc-svn/trunk/gcc/tree-vect-loop.c:5395
#6  0x0000000000a69acb in vectorize_loops () at
../../gcc-svn/trunk/gcc/tree-vectorizer.c:214
#7  0x000000000081f8a7 in execute_one_pass (pass=0x10dad40) at
../../gcc-svn/trunk/gcc/passes.c:2080

(gdb) f 2
#2  0x000000000074885c in gsi_for_stmt (stmt=0x7ffff14724b0) at
../../gcc-svn/trunk/gcc/gimple-iterator.c:560
560       gcc_unreachable ();
(gdb) p debug_gimple_stmt (stmt)
VIEW_CONVERT_EXPR<<unnamed-unsigned:8>>(MEM[(logical(kind=1)[0:]
*)D.900_81][D.987_168]) = patt.40_106;

$3 = void


             reply	other threads:[~2011-12-27 11:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 11:39 ubizjak at gmail dot com [this message]
2011-12-27 11:56 ` [Bug tree-optimization/51684] " jakub at gcc dot gnu.org
2011-12-27 13:55 ` irar at il dot ibm.com
2011-12-28  9:09 ` ubizjak at gmail dot com
2011-12-28  9:38 ` irar at gcc dot gnu.org
2011-12-28 10:33 ` irar at il dot ibm.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-51684-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).