public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49220] ICE in create_pre_exit, at mode-switching.c:401
Date: Sun, 29 May 2011 13:02:00 -0000 [thread overview]
Message-ID: <bug-49220-4-Bs3zWS8PYE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49220-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49220
Kazumoto Kojima <kkojima at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
CC| |kkojima at gcc dot gnu.org
--- Comment #1 from Kazumoto Kojima <kkojima at gcc dot gnu.org> 2011-05-29 12:39:21 UTC ---
I think that create_pre_exit is used by SH target only.
I'm testing the patch below.
--- ORIG/trunk/gcc/mode-switching.c 2010-11-20 09:24:49.000000000 +0900
+++ trunk/gcc/mode-switching.c 2011-05-29 21:24:18.000000000 +0900
@@ -324,7 +324,14 @@ create_pre_exit (int n_entities, int *en
&& GET_CODE (SUBREG_REG (copy_reg)) == REG)
copy_start = REGNO (SUBREG_REG (copy_reg));
else
- break;
+ {
+ /* When control reaches end of non-void function,
+ there are no return copy insns at all. This
+ avoids an ice on that invalid function. */
+ if (ret_start + nregs == ret_end)
+ short_block = 1;
+ break;
+ }
if (copy_start >= FIRST_PSEUDO_REGISTER)
break;
copy_num
next prev parent reply other threads:[~2011-05-29 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 8:06 [Bug middle-end/49220] New: " rmansfield at qnx dot com
2011-05-29 13:02 ` kkojima at gcc dot gnu.org [this message]
2012-07-15 22:20 ` [Bug middle-end/49220] " olegendo at gcc dot gnu.org
2012-11-06 4:35 ` amylaar at gcc dot gnu.org
2012-11-06 9:51 ` ubizjak at gmail dot com
2012-11-06 14:47 ` ubizjak at gmail dot com
2012-11-06 23:22 ` kkojima at gcc dot gnu.org
2012-11-07 10:48 ` kkojima at gcc dot gnu.org
2012-11-07 23:23 ` kkojima at gcc dot gnu.org
2012-11-08 7:22 ` ubizjak at gmail dot com
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-49220-4-Bs3zWS8PYE@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).