public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53185] New: segmentation fault in vectorizable_load
Date: Wed, 02 May 2012 06:10:00 -0000	[thread overview]
Message-ID: <bug-53185-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53185
           Summary: segmentation fault in vectorizable_load
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gary@intrepid.com
                CC: nenad@intrepid.com
            Target: x86_64


Created attachment 27280
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27280
script to demonstrate compiler segfault

GCC 4.8 trunk revision r187034 encounters a segfault when compiling the
attached test case.  This appears to be a relatively recent regression.

Here's the back trace.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000d93153 in vectorizable_load (stmt=0x7ffff1889460,
    gsi=0x7fffffffd680, vec_stmt=0x7fffffffd5a0, slp_node=0x0,
    slp_node_instance=0x0)
    at gcc/tree-vect-stmts.c:4563
4563          ivstep = fold_build2 (MULT_EXPR, TREE_TYPE (ivstep), ivstep,
(gdb) where
#0  0x0000000000d93153 in vectorizable_load (stmt=0x7ffff1889460,
    gsi=0x7fffffffd680, vec_stmt=0x7fffffffd5a0, slp_node=0x0,
    slp_node_instance=0x0)
    at gcc/tree-vect-stmts.c:4563
#1  0x0000000000d978e4 in vect_transform_stmt (stmt=0x7ffff1889460,
    gsi=0x7fffffffd680, grouped_store=0x7fffffffd677 "", slp_node=0x0,
    slp_node_instance=0x0)
    at gcc/tree-vect-stmts.c:5639
#2  0x0000000000dac324 in vect_transform_loop (loop_vinfo=0x1cd0630)
    at gcc/tree-vect-loop.c:5461
#3  0x0000000000dbfd08 in vectorize_loops ()
    at gcc/tree-vectorizer.c:214
#4  0x0000000000cbf6b4 in tree_vectorize ()
    at gcc/tree-ssa-loop.c:218
#5  0x0000000000a22eb0 in execute_one_pass (pass=0x19fdc40)
    at gcc/passes.c:2181
#6  0x0000000000a23096 in execute_pass_list (pass=0x19fdc40)
    at gcc/passes.c:2236
#7  0x0000000000a230b7 in execute_pass_list (pass=0x19fda60)
    at gcc/passes.c:2237

To reproduce, copy the attached do-fail script and gasnet_core.i file to the
gcc build directory, and run do-fail.

The compiler was configured with --disable-bootstrap --disable-multilib and
--enable-checking, however, the failure occurred after a full bootstrap and
with various other configure switches as well.


             reply	other threads:[~2012-05-02  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  6:10 gary at intrepid dot com [this message]
2012-05-02  6:11 ` [Bug tree-optimization/53185] " gary at intrepid dot com
2012-05-02  6:43 ` markus at trippelsdorf dot de
2012-05-02 10:47 ` markus at trippelsdorf dot de
2012-05-02 11:28 ` [Bug tree-optimization/53185] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-05-03 10:59 ` markus at trippelsdorf dot de
2012-05-08 16:03 ` gary at intrepid dot com
2012-05-09 16:21 ` matz at gcc dot gnu.org
2012-05-09 16:44 ` matz at gcc dot gnu.org
2012-05-09 22:17 ` gary at intrepid dot com
2013-02-05 15:34 ` 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-53185-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).