From: Jakub Jelinek <jakub@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org,
Richard Sandiford <rdsandiford@googlemail.com>,
Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: [PATCH v2, rtl-optimization]: Fix PR54457, [x32] Fail to combine 64bit index + constant
Date: Thu, 27 Sep 2012 20:33:00 -0000 [thread overview]
Message-ID: <20120927182008.GZ1787@tucnak.redhat.com> (raw)
In-Reply-To: <CAFULd4YiqSJPDNzg3XTyWx=mBphzCWSpuaQiQ7SbO17Bgc7SSA@mail.gmail.com>
On Thu, Sep 27, 2012 at 08:04:58PM +0200, Uros Bizjak wrote:
> After some off-line discussion with Richard, attached is v2 of the patch.
>
> 2012-09-27 Uros Bizjak <ubizjak@gmail.com>
>
> PR rtl-optimization/54457
> * simplify-rtx.c (simplify_subreg):
> Simplify (subreg:SI (op:DI ((x:DI) (y:DI)), 0)
> to (op:SI (subreg:SI (x:DI) 0) (subreg:SI (x:DI) 0)).
Is that a good idea even for WORD_REGISTER_OPERATIONS targets?
> --- simplify-rtx.c (revision 191808)
> +++ simplify-rtx.c (working copy)
> @@ -5689,6 +5689,28 @@ simplify_subreg (enum machine_mode outermode, rtx
> return CONST0_RTX (outermode);
> }
>
> + /* Simplify (subreg:SI (op:DI ((x:DI) (y:DI)), 0)
> + to (op:SI (subreg:SI (x:DI) 0) (subreg:SI (x:DI) 0)), where
> + the outer subreg is effectively a truncation to the original mode. */
> + if ((GET_CODE (op) == PLUS
> + || GET_CODE (op) == MINUS
> + || GET_CODE (op) == MULT)
> + && SCALAR_INT_MODE_P (outermode)
> + && SCALAR_INT_MODE_P (innermode)
> + && GET_MODE_PRECISION (outermode) < GET_MODE_PRECISION (innermode)
> + && byte == subreg_lowpart_offset (outermode, innermode))
> + {
> + rtx op0 = simplify_gen_subreg (outermode, XEXP (op, 0),
> + innermode, byte);
> + if (op0)
> + {
> + rtx op1 = simplify_gen_subreg (outermode, XEXP (op, 1),
> + innermode, byte);
> + if (op1)
> + return simplify_gen_binary (GET_CODE (op), outermode, op0, op1);
> + }
> + }
> +
> /* Simplify (subreg:QI (lshiftrt:SI (sign_extend:SI (x:QI)) C), 0) into
> to (ashiftrt:QI (x:QI) C), where C is a suitable small constant and
> the outer subreg is effectively a truncation to the original mode. */
Jakub
next prev parent reply other threads:[~2012-09-27 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 8:04 [PATCH, " Uros Bizjak
2012-09-26 18:17 ` Richard Sandiford
2012-09-26 21:38 ` Eric Botcazou
2012-09-27 14:25 ` Uros Bizjak
2012-09-27 16:10 ` Richard Sandiford
2012-09-27 18:20 ` [PATCH v2, " Uros Bizjak
2012-09-27 18:35 ` Paul_Koning
2012-09-27 19:21 ` Uros Bizjak
2012-10-02 2:13 ` Andrew Pinski
2012-10-02 19:32 ` Richard Sandiford
2012-10-06 10:22 ` RFA: Simplifying truncation and integer lowpart subregs Richard Sandiford
2012-10-06 11:13 ` Eric Botcazou
2012-10-06 12:39 ` Richard Sandiford
2012-10-06 13:05 ` Eric Botcazou
2012-10-07 8:56 ` Richard Sandiford
2012-10-07 12:36 ` Eric Botcazou
2012-11-28 2:27 ` Ramana Radhakrishnan
2012-11-28 21:45 ` Richard Sandiford
2012-09-27 20:33 ` Jakub Jelinek [this message]
2012-09-27 22:37 ` [PATCH v2, rtl-optimization]: Fix PR54457, [x32] Fail to combine 64bit index + constant Richard Sandiford
2012-09-28 15:39 ` Uros Bizjak
2012-09-30 11:40 ` Richard Sandiford
2012-10-03 11:07 ` Paolo Bonzini
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=20120927182008.GZ1787@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.com \
--cc=ubizjak@gmail.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).