public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: Bob Wilson <bwilson@tensilica.com>, gcc@gcc.gnu.org
Subject: Re: [cft] subreg validation round 2
Date: Thu, 18 Nov 2004 16:23:00 -0000	[thread overview]
Message-ID: <wvnk6sjb8ks.fsf@talisman.cambridge.redhat.com> (raw)
In-Reply-To: <20041117194553.GA12418@redhat.com> (Richard Henderson's message of "Wed, 17 Nov 2004 11:45:53 -0800")

Richard Henderson <rth@redhat.com> writes:
> On Wed, Nov 17, 2004 at 11:18:41AM -0800, Bob Wilson wrote:
>> Is this my bug?
>
> Yes.  BLKmode REGs are illegal.

I realise that they are in general, but it's fairly clear that,
for example, FUNCTION_VALUE is allowed to return BLKmode REGs.
Routines like hard_function_value have code that specifically
handles such cases.  I'd always thought that FUNCTION_ARG was
in the same boat, and that the argument handling code interpreted
(reg:BLK X) as meaning "as many consecutive registers as necessary,
starting at X".

MIPS's FUNCTION_ARG has returned (reg:BLK reg) for as long as I've
been working on it and it always seems to have been interpreted in
the right way.

Are you saying that FUNCTION_ARG isn't an exception, and that it can
never return a BLKmode REG?  If so, what's the correct mode for, say,
a 33 byte value passed in 5 consecutive 64-bit registers?  I suppose
the answer is probably "there isn't one, use a PARALLEL", but like I
say, returning BLKmode REGs has worked fine until now, so this does
seem like an interface change.

Richard

  parent reply	other threads:[~2004-11-18 13:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 18:58 Richard Henderson
2004-11-17 19:20 ` Bob Wilson
2004-11-17 19:58   ` Richard Henderson
2004-11-18  1:06     ` Alan Modra
2004-11-18  2:43       ` Bob Wilson
2004-11-18 16:23     ` Richard Sandiford [this message]
2004-11-19 21:39       ` Richard Henderson
2004-11-22 20:40         ` Richard Henderson
2004-11-17 22:32   ` Janis Johnson
2004-11-17 23:05     ` Andrew Pinski
2004-11-18 11:40     ` Alan Modra
2004-11-17 19:46 ` Eric Botcazou
2004-11-19 21:50   ` Richard Henderson
2004-11-19 22:43     ` Eric Botcazou
2004-11-19 22:46       ` Richard Henderson
2004-11-18 23:43 ` Kaz Kojima
2004-11-19  0:08 ` Janis Johnson
2004-11-17 19:19 Ulrich Weigand
     [not found] <OF12E4E5CC.BDFB0F1C-ON41256F4F.0067F055-41256F4F.00682968@LocalDomain>
2004-11-17 21:42 ` Ulrich Weigand

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=wvnk6sjb8ks.fsf@talisman.cambridge.redhat.com \
    --to=rsandifo@redhat.com \
    --cc=bwilson@tensilica.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@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).