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/37633] [4.4 Regression] wrong register use on sh64
Date: Fri, 26 Sep 2008 03:32:00 -0000 [thread overview]
Message-ID: <20080926033102.24778.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37633-5208@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from kkojima at gcc dot gnu dot org 2008-09-26 03:31 -------
I've tried
--- ORIG/trunk/gcc/ira-color.c Wed Sep 17 09:48:49 2008
+++ LOCAL/trunk/gcc/ira-color.c Thu Sep 25 12:09:30 2008
@@ -514,7 +514,9 @@ assign_hard_reg (ira_allocno_t allocno,
#endif
if (! ira_hard_reg_not_in_set_p (hard_regno, mode, conflicting_regs)
|| TEST_HARD_REG_BIT (prohibited_class_mode_regs[cover_class][mode],
- hard_regno))
+ hard_regno)
+ || (ALLOCNO_CALLS_CROSSED_NUM (allocno) != 0
+ && HARD_REGNO_CALL_PART_CLOBBERED (hard_regno, mode)))
continue;
cost = costs[i];
full_cost = full_costs[i];
@@ -3064,7 +3066,9 @@ ira_fast_allocation (void)
#endif
if (!ira_hard_reg_not_in_set_p (hard_regno, mode, conflict_hard_regs)
|| (TEST_HARD_REG_BIT
- (prohibited_class_mode_regs[cover_class][mode], hard_regno)))
+ (prohibited_class_mode_regs[cover_class][mode], hard_regno))
+ || (ALLOCNO_CALLS_CROSSED_NUM (a) != 0
+ && HARD_REGNO_CALL_PART_CLOBBERED (hard_regno, mode)))
continue;
ALLOCNO_HARD_REGNO (a) = hard_regno;
for (r = ALLOCNO_LIVE_RANGES (a); r != NULL; r = r->next)
It works for me, though it could be completely wrong.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37633
next prev parent reply other threads:[~2008-09-26 3:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 1:12 [Bug target/37633] New: " kkojima at gcc dot gnu dot org
2008-09-24 1:13 ` [Bug target/37633] " kkojima at gcc dot gnu dot org
2008-09-24 3:11 ` pinskia at gcc dot gnu dot org
2008-09-26 3:32 ` kkojima at gcc dot gnu dot org [this message]
2008-10-08 21:56 ` vmakarov at redhat dot com
2008-10-14 19:43 ` vmakarov at redhat dot com
2008-10-14 22:26 ` hjl at gcc dot gnu dot org
2008-10-15 23:16 ` kkojima at gcc dot gnu dot org
2008-10-16 0:55 ` vmakarov at gcc dot gnu dot org
2008-10-21 23:43 ` kkojima at gcc dot gnu dot org
2009-01-02 17:17 ` andreasmeier80 at gmx dot de
2009-01-02 22:52 ` kkojima at gcc dot gnu dot org
2009-03-08 16:35 ` amylaar at gcc dot gnu dot org
2009-04-21 15:59 ` [Bug target/37633] [4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:34 ` jakub at gcc dot gnu dot org
2009-10-15 12:55 ` jakub at gcc dot gnu dot org
2010-01-21 13:19 ` jakub at gcc dot gnu dot org
2010-04-30 9:25 ` [Bug target/37633] [4.4/4.5/4.6 " jakub at gcc dot gnu dot 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=20080926033102.24778.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).