public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: gcc@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: [cft] subreg validation patch
Date: Sun, 14 Nov 2004 04:41:00 -0000	[thread overview]
Message-ID: <20041114002100.GA23493@redhat.com> (raw)
In-Reply-To: <200411140104.42157.ebotcazou@libertysurf.fr>

On Sun, Nov 14, 2004 at 01:07:34AM +0100, Eric Botcazou wrote:
> As far as I can see, almost all splitters in sparc.md use gen_lowpart and 
> gen_highpart, disregarding their post-reloadness.  I'll fix them tomorrow.

Except that I would think that gen_lowpart/highpart should be creating
a new hard register rtx when given an input hard register rtx.

I'll look into it later tonight.


r~

  reply	other threads:[~2004-11-14  0:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 13:17 Non-representable subregs of subword pseudoregs Eric Botcazou
2004-11-13 13:45 ` Jan Hubicka
2004-11-13 22:55 ` Richard Sandiford
2004-11-13 23:31   ` Eric Botcazou
2004-11-13 23:06 ` [cft] subreg validation patch Richard Henderson
2004-11-13 23:50   ` Eric Botcazou
2004-11-14  0:02     ` Richard Henderson
2004-11-14  0:21       ` Eric Botcazou
2004-11-14  4:41         ` Richard Henderson [this message]
2004-11-14  5:12     ` Richard Henderson
2004-11-14  6:14       ` Geert Bosch
2004-11-14  7:46       ` Richard Henderson
2004-11-14 10:50         ` Eric Botcazou
2004-11-14 18:03 Ulrich Weigand
2004-11-15 20:12 ` Richard Henderson
2004-11-15 22:02   ` Ulrich Weigand
2004-11-15 22:08     ` Richard Henderson
2004-11-15 23:22       ` Ulrich Weigand
2004-11-16 14:03 Ulrich Weigand
2004-11-16 21:02 ` Richard Henderson
2004-11-17  1:01 ` 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=20041114002100.GA23493@redhat.com \
    --to=rth@redhat.com \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).