public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/56738] New: ICE in c-c++-common/torture/vshuf-v4di.c
Date: Tue, 26 Mar 2013 11:46:00 -0000	[thread overview]
Message-ID: <bug-56738-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 56738
           Summary: ICE in c-c++-common/torture/vshuf-v4di.c
    Classification: Unclassified
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ktkachov@gcc.gnu.org
                CC: stevenb.gcc@gmail.com
            Target: arm-none-eabi


Created attachment 29729
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29729
Preprocessed file

Testcase ICEs on arm-none-eabi when compiled with -O1 (ICEs also with -O2 and
-O3)

In file included from vshuf-v4di.c:19:0:
vshuf-main.inc: In function 'main':
vshuf-main.inc:26:1: internal compiler error: in df_insn_delete, at
df-scan.c:1162
 }
 ^
0x634b9c df_insn_delete(rtx_def*)
    $SOURCE/gcc/gcc/df-scan.c:1162
0x68b98a remove_insn(rtx_def*)
    $SOURCE/gcc/gcc/emit-rtl.c:4036
0x5f83be delete_insn(rtx_def*)
    $SOURCE/gcc/gcc/cfgrtl.c:167
0xd335b6 resolve_simple_move
    $SOURCE/gcc/gcc/lower-subreg.c:1072
0xd338b3 resolve_simple_move
    $SOURCE/gcc/gcc/lower-subreg.c:923
0xd34a13 decompose_multiword_subregs
    $SOURCE/gcc/gcc/lower-subreg.c:1563
0xd3528d rest_of_handle_lower_subreg2
    $SOURCE/gcc/gcc/lower-subreg.c:1682
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.


Bisection shows it started with r196977

Cross compiler configured with:
Target: arm-none-eabi
Configured with: $SOURCE/gcc/configure --target=arm-none-eabi
--prefix=$SOURCE/build/install --with-gmp=$SOURCE/build/host-tools
--with-mpfr=$SOURCE/build/host-tools --with-mpc=$SOURCE/build/host-tools
--with-pkgversion=unknown --disable-shared --disable-nls --disable-threads
--disable-tls --enable-checking=yes --enable-languages=c --with-newlib
--with-fpu=neon --with-float=hard --with-arch=armv7-a
Thread model: single
gcc version 4.9.0 20130322 (experimental) (unknown)


             reply	other threads:[~2013-03-26 11:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 11:46 ktkachov at gcc dot gnu.org [this message]
2013-03-26 11:47 ` [Bug regression/56738] " ktkachov at gcc dot gnu.org
2013-03-26 11:58 ` dominiq at lps dot ens.fr
2013-03-26 12:07 ` ktkachov at gcc dot gnu.org
2013-03-26 12:43 ` [Bug regression/56738] [4.9 Regression] " dominiq at lps dot ens.fr
2013-03-27 23:45 ` steven at gcc dot gnu.org
2013-10-25 12:32 ` [Bug rtl-optimization/56738] " rguenth at gcc dot gnu.org
2013-11-22 10:39 ` 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-56738-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).