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 target/48031] New: [4,4, 4.5 regression] gcc.c-torture/compile/pr42956.c ICEs gcc on m68k-linux, ivopts related?
Date: Tue, 08 Mar 2011 10:01:00 -0000 [thread overview]
Message-ID: <bug-48031-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48031
Summary: [4,4, 4.5 regression] gcc.c-torture/compile/pr42956.c
ICEs gcc on m68k-linux, ivopts related?
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: mikpe@it.uu.se
The pr42956.c test case ICEs gcc 4.5 and 4.4 on m68k-linux:
> gcc/xgcc -Bgcc -O1 -S /.../gcc/testsuite/gcc.c-torture/compile/pr42956.c
/.../gcc/testsuite/gcc.c-torture/compile/pr42956.c: In function 'Split':
/.../gcc/testsuite/gcc.c-torture/compile/pr42956.c:10:6: error: expected an
SSA_NAME object
/.../gcc/testsuite/gcc.c-torture/compile/pr42956.c:10:6: error: in statement
D.2041_132 = D.1987 /[ex] 2;
/.../gcc/testsuite/gcc.c-torture/compile/pr42956.c:10:6: internal compiler
error: verify_ssa failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
This is with a cross to m68k-linux and --enable-checking=yes, with
--enable-checking=release the compiler segfaults instead.
Compiling with -O1 -fno-ivopts or -O0 eliminates the ICE.
This bug occurs with gcc-4.4.5 and gcc-4.5.2. It does not occur with
gcc-4.3.5. For gcc-4.6 it stopped occurring after the big MEM_REF update in
r161655.
next reply other threads:[~2011-03-08 10:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 10:01 mikpe at it dot uu.se [this message]
2011-03-08 11:02 ` [Bug tree-optimization/48031] [4.4/4.5 Regression] " rguenth at gcc dot gnu.org
2011-03-08 14:23 ` mikpe at it dot uu.se
2011-03-08 21:40 ` mikpe at it dot uu.se
2011-03-09 9:22 ` rguenther at suse dot de
2011-03-09 23:37 ` mikpe at it dot uu.se
2011-03-10 9:22 ` mikpe at it dot uu.se
2011-03-10 9:34 ` rguenther at suse dot de
2011-03-10 11:03 ` rguenth at gcc dot gnu.org
2011-03-10 12:35 ` ebotcazou at gcc dot gnu.org
2011-03-10 12:36 ` rguenther at suse dot de
2011-03-10 12:46 ` ebotcazou at gcc dot gnu.org
2011-03-10 12:58 ` rguenther at suse dot de
2011-03-10 13:04 ` ebotcazou at gcc dot gnu.org
2011-03-10 13:07 ` rguenther at suse dot de
2011-03-10 13:10 ` rguenth at gcc dot gnu.org
2011-03-10 14:03 ` mikpe at it dot uu.se
2011-03-15 8:53 ` mikpe at it dot uu.se
2011-03-15 10:06 ` rguenth at gcc dot gnu.org
2011-03-28 10:22 ` rguenth at gcc dot gnu.org
2011-04-10 10:38 ` rguenth at gcc dot gnu.org
2011-04-16 11:18 ` jakub at gcc dot gnu.org
2011-04-18 14:15 ` [Bug tree-optimization/48031] [4.4 " rguenth at gcc dot gnu.org
2011-04-18 14:42 ` [Bug tree-optimization/48031] [4.4/4.5 " rguenth at gcc dot gnu.org
2011-04-18 14:55 ` [Bug tree-optimization/48031] [4.4 " rguenth at gcc dot gnu.org
2012-03-13 16:57 ` jakub 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-48031-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).