public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar 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: Sun, 08 Mar 2009 16:35:00 -0000 [thread overview]
Message-ID: <20090308163509.29348.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37633-5208@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from amylaar at gcc dot gnu dot org 2009-03-08 16:35 -------
(In reply to comment #3)
> I've checked the old RA. It does not assigned partially clobbered hard
> register because it is done only when non partially clobbered hard regs were
> tried first. Sh has a lot of such registers therefore the chance to generate
> wrong code is small.
>
> I can simulate the same behaviour for IRA by increasing costs for partially
> clobbered hard registers. Currently rs6000 and sh define
> HARD_REGNO_CALL_PART_CLOBBERED. So even the problem is solved for sh in
> different way, the patch increasing cost would be useful for rs6000.
>
> Still, as I wrote, the complete solution (the mentioned cost increase will be
> still necessary in any case) would be save and restore partially clobbered
> hard-registers in caller-saves.c.
To avoid pessimizing code where partially clobbered registers are used
to allocate pseudos which are not affected by the partial clobbers, the
register allocator will have to provide caller_save.c with more information.
It needs to know which registers are live across a call in excess of the part
that is saved.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37633
next prev parent reply other threads:[~2009-03-08 16:35 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
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 [this message]
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=20090308163509.29348.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).