public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Steve Ellcey <sje@cup.hp.com>, gcc@gcc.gnu.org, dave@hiauly1.hia.nrc.ca
Subject: Re: Vector modes under hppa64-hpu
Date: Sat, 27 Jul 2002 07:35:00 -0000	[thread overview]
Message-ID: <m31y9px05s.fsf@flamingo.sfbay.redhat.com> (raw)
In-Reply-To: <3D406473.5E2DF7AA@superh.com>

>>>>> "Joern" == Joern Rennecke <joern.rennecke@superh.com> writes:

 >   	  else
 >   	    t = simplify_gen_subreg (submode, target, mode, i * subsize);
 > ! 	  if (CONSTANT_P (op0) || GET_CODE (op0) == REG)
 >   	    a = simplify_gen_subreg (submode, op0, mode, i * subsize);
 >   	  else
 >   	    a = extract_bit_field (op0, subbitsize, i * subbitsize, unsignedp,
 >   				   NULL_RTX, submode, submode, size);
 > ! 	  if (CONSTANT_P (op1) || GET_CODE (op1) == REG)
 >   	    b = simplify_gen_subreg (submode, op1, mode, i * subsize);
 >   	  else
 >   	    b = extract_bit_field (op1, subbitsize, i * subbitsize, unsignedp,


 > That doesn't work when submode is smaller than a word.  At register allocation
 > time, every subreg of a single hard register is assumed to be a low part,
 > even if its not.

Joern.  Could we keep the above code and add a check for the submode
being >= word?  It seems like the extract_bit_field is a bit of
overkill when the submode is just the word size.

What do you think?

Aldy

  parent reply	other threads:[~2002-07-27  4:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 20:57 Joern Rennecke
2002-07-25 21:21 ` Aldy Hernandez
2002-07-26  3:20   ` Joern Rennecke
2002-07-27  5:54     ` John David Anglin
2002-07-27  7:35 ` Aldy Hernandez [this message]
2002-07-28  9:52   ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 22:07 Joern Rennecke
2002-07-26  1:56 ` John David Anglin
2002-07-25 15:19 Steve Ellcey
2002-07-25 15:28 ` Aldy Hernandez
2002-07-25 11:40 Steve Ellcey
2002-07-25 14:52 ` Aldy Hernandez
2002-07-25  3:53 Steve Ellcey
2002-07-25  2:02 Steve Ellcey
2002-07-25  2:36 ` Aldy Hernandez
2002-07-25  2:54   ` John David Anglin
2002-07-25  2:56     ` Aldy Hernandez
2002-07-25 11:22       ` John David Anglin
2002-07-25  0:09 Steve Ellcey
2002-07-25  1:01 ` Aldy Hernandez
2002-07-24 17:42 Steve Ellcey
2002-07-24 18:12 ` Aldy Hernandez
2002-07-24 15:22 Steve Ellcey
2002-07-24 16:30 ` Aldy Hernandez
2002-07-24 14:11 Steve Ellcey
2002-07-14 23:15 Aldy Hernandez

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=m31y9px05s.fsf@flamingo.sfbay.redhat.com \
    --to=aldyh@redhat.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=joern.rennecke@superh.com \
    --cc=sje@cup.hp.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).