public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/56131] New: [4.8 regression] gcc.dg/pr56035.c ICEs gcc on sparc-linux
Date: Mon, 28 Jan 2013 17:42:00 -0000 [thread overview]
Message-ID: <bug-56131-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56131
Bug #: 56131
Summary: [4.8 regression] gcc.dg/pr56035.c ICEs gcc on
sparc-linux
Classification: Unclassified
Product: gcc
Version: 4.7.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: regression
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: mikpe@it.uu.se
The recently added gcc.dg/pr56035.c test case fails on sparc-linux:
+FAIL: gcc.dg/pr56035.c (internal compiler error)
+FAIL: gcc.dg/pr56035.c (test for excess errors)
Compiling it with an x86_64-linux to sparc-linux cross-compiler shows:
> /tmp/objdir/gcc/xgcc -B/tmp/objdir/gcc/ -O1 -ftree-vectorize -fcse-follow-jumps -fstrict-overflow -S pr56035.c
pr56035.c: In function 'f':
pr56035.c:35:1: internal compiler error: Segmentation fault
}
^
0x70fa9f crash_signal
/tmp/gcc-4.8-20130127/gcc/toplev.c:332
0x4cdc96 delete_insn(rtx_def*)
/tmp/gcc-4.8-20130127/gcc/cfgrtl.c:151
0x6210a8 delete_related_insns(rtx_def*)
/tmp/gcc-4.8-20130127/gcc/jump.c:1243
0x6215e7 redirect_jump_2(rtx_def*, rtx_def*, rtx_def*, int, int)
/tmp/gcc-4.8-20130127/gcc/jump.c:1574
0x6216b2 redirect_jump(rtx_def*, rtx_def*, int)
/tmp/gcc-4.8-20130127/gcc/jump.c:1533
0x6c4464 dbr_schedule(rtx_def*)
/tmp/gcc-4.8-20130127/gcc/reorg.c:3722
0x6c52bf rest_of_handle_delay_slots
/tmp/gcc-4.8-20130127/gcc/reorg.c:3891
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.
This ICE is different from the one in PR56035.
Reverting the PR56035 fix in r195462 makes no difference.
gcc-4.7 does not ICE on this test case.
next reply other threads:[~2013-01-28 17:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 17:42 mikpe at it dot uu.se [this message]
2013-01-28 21:59 ` [Bug regression/56131] " mikpe at it dot uu.se
2013-01-28 23:16 ` vries at gcc dot gnu.org
2013-01-29 0:28 ` vries at gcc dot gnu.org
2013-01-29 10:12 ` [Bug rtl-optimization/56131] " rguenth at gcc dot gnu.org
2013-01-29 17:01 ` danglin at gcc dot gnu.org
2013-01-29 19:34 ` vries at gcc dot gnu.org
2013-01-30 22:20 ` mikpe at it dot uu.se
2013-02-04 13:08 ` ro at gcc dot gnu.org
2013-02-04 15:19 ` vries at gcc dot gnu.org
2013-02-04 15:39 ` mikpe at it dot uu.se
2013-02-04 17:35 ` vries at gcc dot gnu.org
2013-02-06 8:54 ` vries at gcc dot gnu.org
2013-02-06 12:24 ` vries at gcc dot gnu.org
2013-02-21 10:30 ` steven at gcc dot gnu.org
2013-02-22 10:30 ` vries at gcc dot gnu.org
2013-02-22 13:18 ` jakub at gcc dot gnu.org
2013-02-22 16:34 ` steven at gcc dot gnu.org
2013-02-22 22:37 ` vries at gcc dot gnu.org
2013-02-25 9:31 ` vries at gcc dot gnu.org
2013-02-25 10:34 ` jakub at gcc dot gnu.org
2013-02-25 11:50 ` vries at gcc dot gnu.org
2013-02-25 11:51 ` vries at gcc dot gnu.org
2013-02-25 19:55 ` stevenb.gcc at gmail dot com
2013-02-25 19:59 ` stevenb.gcc at gmail dot com
2013-02-25 22:29 ` ebotcazou 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-56131-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).