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 GCC][2/7]Don't rename variables for deleted new preheader
Date: Mon, 09 Oct 2017 13:30:00 -0000 [thread overview]
Message-ID: <CAFiYyc129O62ZJkwuKHi04Z-Y4Ljtk9HdK6Ja723hNJWS14r9Q@mail.gmail.com> (raw)
In-Reply-To: <DB5PR0801MB2742950F0306DB51E23F334FE7700@DB5PR0801MB2742.eurprd08.prod.outlook.com>
On Thu, Oct 5, 2017 at 3:15 PM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> I noticed that new_preheader basic block could be deleted if the copied
> loop is added at entry in function slpeel_tree_duplicate_loop_to_edge_cfg.
> This simple patch skips new_preheader during variable renaming if it is
> deleted.
> Bootstrap and test in patch set on x86_64 and AArch64, is it OK?
Ok.
Richard.
> Thanks,
> bin
> 2017-10-04 Bin Cheng <bin.cheng@arm.com>
>
> * tree-vect-loop-manip.c (slpeel_tree_duplicate_loop_to_edge_cfg): Skip
> renaming variables in new preheader if it's deleted.
prev parent reply other threads:[~2017-10-09 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 13:16 Bin Cheng
2017-10-09 13:30 ` 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=CAFiYyc129O62ZJkwuKHi04Z-Y4Ljtk9HdK6Ja723hNJWS14r9Q@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).