From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [cft] subreg validation round 2
Date: Fri, 19 Nov 2004 22:43:00 -0000 [thread overview]
Message-ID: <200411192323.54912.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <20041119210240.GA18341@redhat.com>
> > How did you address the problem with SPARC splitters?
>
> @@ -3674,14 +3676,15 @@ simplify_subreg (enum machine_mode outer
> && subreg_offset_representable_p (REGNO (op), innermode,
> byte, outermode))
> {
> - rtx tem = gen_rtx_SUBREG (outermode, op, byte);
> - int final_regno = subreg_hard_regno (tem, 0);
> + unsigned int regno = REGNO (op);
> + unsigned int final_regno
> + = regno + subreg_regno_offset (regno, innermode, byte, outermode);
Ouch! Pretty deeply buried in the subreg handling stuff.
Would you see any advantage in manually building the hard regs within the
splitters?
--
Eric Botcazou
next prev parent reply other threads:[~2004-11-19 22:24 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
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 [this message]
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=200411192323.54912.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--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).