public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: A few simple DImode improvements
Date: Tue, 29 Jun 2010 00:27:00 -0000	[thread overview]
Message-ID: <4C29297F.9090402@redhat.com> (raw)
In-Reply-To: <4C28EB04.6040106@redhat.com>

On 06/28/2010 11:33 AM, Jeff Law wrote:
> On 06/28/10 12:05, Ian Lance Taylor wrote:
>> 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 would expect that unless the target explicitly forbids such an
> allocation via CANNOT_CHANGE_MODE_CLASS, then it ought to work.  In
> fact, this is a normal code generation situation for the PA family to
> support xmpyu -- if it had been broken I suspect we would have heard
> about it by now as anything doing an integer multiply would suddenly be
> using libcalls instead of xmpyu.

CANNOT_CHANGE_MODE_CLASS is the normal state of affairs for several
ports doing int<->fp conversion.  Where DImode is the only valid
integer mode, and the single-precision load instruction does some
bit swizzling (to place the SFmode value into register format) so
that 32-bit integer values cannot be loaded or manipulated.

This is true of some ppc variants and alpha, at least.  As such,
this is sort-of a non-answer, Jeff.  


r~

      reply	other threads:[~2010-06-28 23:00 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
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 [this message]

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=4C29297F.9090402@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@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).