public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
vitalyb@mailru.com
Subject: Re: optimization/8985: ICE in extract_insn, at recog.c:2148 with -fssa-ccp option
Date: Wed, 18 Dec 2002 05:10:00 -0000 [thread overview]
Message-ID: <20021218131047.11393.qmail@sources.redhat.com> (raw)
Old Synopsis: "Internal compiler error in extract_insn, at recog.c:2148" with -fssa-ccp option
New Synopsis: ICE in extract_insn, at recog.c:2148 with -fssa-ccp option
State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Wed Dec 18 05:10:46 2002
State-Changed-Why:
Confirmed.
The bug is present since gcc 3.1 when the option -fssa-ccp was introduced.
It affects the 3.2 branch and gcc 3.3 as of 20021216.
A shorter testcase is the following:
-------------------------snip here-----------------------------
int foo ()
{
int i=0;
char *p="";
if (p) i|=1;
return i && p;
}
-------------------------snip here-----------------------------
Compiling this with gcc 3.2.1 (gcc -O -fssa -fssa-ccp) I get:
PR8985.cc: In function `int foo()':
PR8985.cc:9: unrecognizable insn:
(insn 27 55 28 (parallel[
(set (reg:SI 64)
(const_int 1 [0x1]))
(clobber (reg:CC 17 flags))
] ) -1 (nil)
(expr_list:REG_UNUSED (reg:CC 17 flags)
(insn_list:REG_WAS_0 11 (expr_list:REG_EQUAL (const_int 1 [0x1])
(nil)))))
PR8985.cc:9: Internal compiler error in extract_insn, at recog.c:2148
Please submit a full bug report, [etc.]
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8985
next reply other threads:[~2002-12-18 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 5:10 reichelt [this message]
2003-01-15 12:36 Volker Reichelt
2003-05-10 5:06 Dara Hazeghi
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=20021218131047.11393.qmail@sources.redhat.com \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
--cc=vitalyb@mailru.com \
/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).