From: Bernd Schmidt <bernds@codesourcery.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org,
"Vladimir N. Makarov" <vmakarov@redhat.com>
Subject: Re: A few simple DImode improvements
Date: Mon, 28 Jun 2010 19:34:00 -0000 [thread overview]
Message-ID: <4C28E7FE.4000806@codesourcery.com> (raw)
In-Reply-To: <mcrwrtjxcbw.fsf@google.com>
On 06/28/2010 08:05 PM, Ian Lance Taylor wrote:
> It's superfluous for a simple example like this one, but it's not
> clearly superfluous in all cases. If register 68 here should wind up
> being allocated to a floating point register which can't be SUBREG'ed,
> then my concern is that taking a SUBREG is going to make it harder to
> allocate the register correctly. In other words, the bitmap is not
> irrelevant; it's a proxy for non-SImode register classes.
That however applies to only one case in which bits can be set in that
bitmap, the SUBREG case in find_decomposable_subregs. The normal case,
I think, is that these bits come from occurrences of the reg that are in
NOT_SIMPLE_MOVE, and I think this is irrelevant here. Do we need to
keep track of two different bitmaps?
> I don't know
> whether this a concern with IRA; can IRA allocate a DImode pseudo to a
> floating point register if there are SImode SUBREGs of it? The old
> register allocator wouldn't, and you could wind up with a bunch of
> reloads.
I don't know whether IRA would do that or whether it can determine the
costs correctly; I can't find anything right now which would deal with
this case.
Bernd
next prev parent reply other threads:[~2010-06-28 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 9:16 Bernd Schmidt
2010-06-27 23:33 ` Eric Botcazou
2010-06-28 19:16 ` Ian Lance Taylor
2010-06-28 19:34 ` Bernd Schmidt [this message]
2010-06-28 19:55 ` Jeff Law
2010-06-28 20:02 ` Ian Lance Taylor
2010-06-28 22:32 ` Bernd Schmidt
2010-06-29 0:30 ` Ian Lance Taylor
2010-06-29 3:44 ` Bernd Schmidt
2010-07-14 14:58 ` Bernd Schmidt
2010-07-14 15:12 ` Ian Lance Taylor
2010-07-14 15:18 ` Bernd Schmidt
2010-06-28 19:48 ` Jeff Law
2010-06-29 0:27 ` Richard Henderson
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=4C28E7FE.4000806@codesourcery.com \
--to=bernds@codesourcery.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=vmakarov@redhat.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).