public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: Peter Bigot <bigotp@acm.org>,  GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Setting precision for a PSImode type
Date: Wed, 11 Apr 2012 19:16:00 -0000	[thread overview]
Message-ID: <87y5q2axls.fsf@talisman.home> (raw)
In-Reply-To: <4F85C8FC.5060902@codesourcery.com> (Bernd Schmidt's message of	"Wed, 11 Apr 2012 20:10:04 +0200")

Bernd Schmidt <bernds@codesourcery.com> writes:
> On 04/11/2012 07:31 PM, Peter Bigot wrote:
>> The biggest one is that widening from 20-bit to 32-bit is an extremely
>> expensive operation: it was a 16-bit ISA, but some newer MCUs support
>> an extension with 20 bits in each register and a set of new
>> instructions that must be used to preserve the upper 4 bits.  Getting
>> bits 19..16 of a 20-bit register down into the low bits of a 16 bit
>> register requires a five-position rotate-through-carry.  The 20-bit
>> enhancement to the ISA was really intended only to support a larger
>> address space; to simplify validation of the machine description I've
>> chosen to allow it to be used for any integer operation, but I have no
>> reason to think that'll be common.
>
> Ok. So these are pointer modes, essentially? For the target I'm working
> on, I'm using the following patch, see if that helps you any. It seems
> to apply to trunk, so I might as well ask for an OK if it bootstraps and
> tests ok (but it has little use while these ports remain out-of-tree).

Not that I can approve this anyway, but: what are the properties of
MODE_POINTER vs. MODE_PARTIAL_INT?

It seems odd on the face of it for POINTER_MODE_P (Pmode) to be false
on the majority of targets.  But that's probably just a naming thing.

Richard

  reply	other threads:[~2012-04-11 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPOJ94Nb9Ub5_746eriWOyP4aK--4d5hL591XnEShEH-4xP+6A@mail.gmail.com>
     [not found] ` <4F54EBFD.4060605@codesourcery.com>
     [not found]   ` <CAPOJ94PfgJ9jg6Xkrftykn6KnO+cu3rfejUTBfPs4Nn=3X24EQ@mail.gmail.com>
     [not found]     ` <4F85B775.1060905@codesourcery.com>
     [not found]       ` <CAPOJ94O9F1Fa9n7_3i1k2hDjAmuHc746UzM3XOq=9w_Aa50cNg@mail.gmail.com>
2012-04-11 18:12         ` Bernd Schmidt
2012-04-11 19:16           ` Richard Sandiford [this message]
2012-04-11 19:25             ` Bernd Schmidt

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=87y5q2axls.fsf@talisman.home \
    --to=rdsandiford@googlemail.com \
    --cc=bernds@codesourcery.com \
    --cc=bigotp@acm.org \
    --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).