From: Jeff Law <law@redhat.com>
To: Anatoliy Sokolov <aesok@post.ru>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Use lowpart_subreg instead of simplify_gen_subreg
Date: Mon, 27 Jul 2015 16:40:00 -0000 [thread overview]
Message-ID: <55B65D65.1070402@redhat.com> (raw)
In-Reply-To: <55B53CF1.3070108@post.ru>
On 07/26/2015 02:02 PM, Anatoliy Sokolov wrote:
> Hello.
>
> This patch change function call simplify_gen_subreg (omode, x, imode,
> subreg_lowpart_offset (omode, imode)) with lowpart_subreg (omode, x, imode)
> and move lowpart_subreg function from loop-iv.c to simplify-rtx.c.
>
> Bootstrapped and reg-tested on x86_64-unknown-linux-gnu.
>
> OK for trunk?
>
> Anatoliy.
>
> 2015-07-26 Anatoly Sokolov <aesok@post.ru>
>
> * rtl.h (lowpart_subreg): Move in file.
> * loop-iv.c (lowpart_subreg): Move to...
> * simplify-rtx.c (lowpart_subreg): ...here.
> (simplify_binary_operation_1): Use lowpart_subreg instead of
> simplify_gen_subreg.
> * expr.c (expand_expr_real_2): Ditto.
> * emit-rtl.c (gen_lowpart_common): Ditto.
> * combine.c (gen_lowpart_for_combine): Ditto.
> * cfgexpand.c (convert_debug_memory_address, expand_debug_expr,
> expand_debug_source_expr): Ditto.
OK.
jeff
prev parent reply other threads:[~2015-07-27 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 22:34 Anatoliy Sokolov
2015-07-27 16:40 ` Jeff Law [this message]
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=55B65D65.1070402@redhat.com \
--to=law@redhat.com \
--cc=aesok@post.ru \
--cc=gcc-patches@gcc.gnu.org \
/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).