From: Richard Biener <richard.guenther@gmail.com>
To: Bin Cheng <Bin.Cheng@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH branch/gimple-interchange]obvious cleanup
Date: Tue, 05 Dec 2017 11:24:00 -0000 [thread overview]
Message-ID: <CAFiYyc3RnnhZ43uwsKnOyAoaSiKmJjJLzOe1wqoAUEmvsPoMjg@mail.gmail.com> (raw)
In-Reply-To: <DB5PR0801MB2742BB78C52B18F0CD9FEDC9E73D0@DB5PR0801MB2742.eurprd08.prod.outlook.com>
On Tue, Dec 5, 2017 at 11:07 AM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This is an obvious cleanup patch doing variable renaming, function inlining.
> Is it OK?
Yes.
Thanks,
Richard.
> Thanks,
> bin
> 2017-12-05 Bin Cheng <bin.cheng@arm.com>
>
> * gimple-loop-interchange.cc (struct induction): Rename fields.
> (dump_induction, loop_cand::analyze_induction_var): Update uses.
> (loop_cand::undo_simple_reduction): Ditto.
> (tree_loop_interchange::map_inductions_to_loop): Ditto.
> (tree_loop_interchange::can_interchange_loops): Delete.
> (tree_loop_interchange::interchange): Inline can_interchange_loops.
prev parent reply other threads:[~2017-12-05 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:07 Bin Cheng
2017-12-05 11:24 ` Richard Biener [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=CAFiYyc3RnnhZ43uwsKnOyAoaSiKmJjJLzOe1wqoAUEmvsPoMjg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=Bin.Cheng@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.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).