public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41993] [sh] ICE in create_pre_exit, at mode-switching.c:399
Date: Wed, 11 Nov 2009 21:59:00 -0000 [thread overview]
Message-ID: <20091111215946.13158.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41993-18412@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from kkojima at gcc dot gnu dot org 2009-11-11 21:59 -------
All 4.x sh compilers fail with similar way. Looks only when unoptimized.
Does the patch below work for you?
--- ORIG/trunk/gcc/mode-switching.c 2009-02-21 09:26:24.000000000 +0900
+++ trunk/gcc/mode-switching.c 2009-11-11 11:03:04.000000000 +0900
@@ -325,7 +325,14 @@ create_pre_exit (int n_entities, int *en
else
break;
if (copy_start >= FIRST_PSEUDO_REGISTER)
- break;
+ {
+ if (!optimize)
+ {
+ last_insn = return_copy;
+ continue;
+ }
+ break;
+ }
copy_num
= hard_regno_nregs[copy_start][GET_MODE (copy_reg)];
BTW, I guess that __builtin_apply/__builtin_return may be a bit obsolete.
If my memory is correct, there was an argument on the list for dropping
them from the compiler.
--
kkojima at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kkojima at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |ice-on-valid-code
Known to fail| |4.0.4 4.1.3 4.2.4 4.3.4
| |4.4.2 4.5.0
Known to work| |3.4.6
Priority|P3 |P4
Last reconfirmed|0000-00-00 00:00:00 |2009-11-11 21:59:45
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41993
next prev parent reply other threads:[~2009-11-11 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 3:18 [Bug c/41993] New: " iwamatsu at nigauri dot org
2009-11-11 21:59 ` kkojima at gcc dot gnu dot org [this message]
2009-11-17 2:56 ` [Bug target/41993] " iwamatsu at nigauri dot org
2009-11-17 22:24 ` kkojima at gcc dot gnu dot org
[not found] <bug-41993-4@http.gcc.gnu.org/bugzilla/>
2012-11-04 16:46 ` ubizjak at gmail dot com
2012-11-05 9:14 ` kkojima at gcc dot gnu.org
2012-11-05 9:17 ` ubizjak at gmail dot com
2012-11-05 10:19 ` kkojima at gcc dot gnu.org
2012-11-06 9:17 ` kkojima at gcc dot gnu.org
2012-11-06 14:31 ` uros at gcc dot gnu.org
2012-11-07 23:24 ` kkojima at gcc dot gnu.org
2012-11-08 7:24 ` ubizjak at gmail dot com
2012-11-11 22:45 ` ubizjak at gmail dot com
2012-11-12 10:35 ` kkojima at gcc dot gnu.org
2012-11-12 20:21 ` olegendo at gcc dot gnu.org
2012-11-13 17:00 ` uros 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=20091111215946.13158.qmail@sourceware.org \
--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).