public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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/6]Factor out code pruning runtime alias checks
Date: Fri, 26 May 2017 11:16:00 -0000	[thread overview]
Message-ID: <CAFiYyc2Uf4nQB+G6ajkofFgLhnDBKDWHMFgYJtv-eviNNsAM1w@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0802MB2176425F7CDF0ED8B680D7DFE7F90@VI1PR0802MB2176.eurprd08.prod.outlook.com>

On Tue, May 23, 2017 at 6:22 PM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This is the second patch in the set, it factors out code pruning runtime alias
> checks from file tree-vect-data-refs.c to tree-data-ref.c.  It also introduces
> new interface prune_runtime_alias_test_list so that we can use it in pass like
> loop distribution.
> Bootstrap and test on x86_64 and AArch64, is it OK?

Ok.
Richard.

> Thanks,
> bin
> 2017-05-22  Bin Cheng  <bin.cheng@arm.com>
>
>         * tree-vect-data-refs.c (Operator==, comp_dr_with_seg_len_pair):
>         Move from ...
>         * tree-data-ref.c (Operator==, comp_dr_with_seg_len_pair): To here.
>         * tree-vect-data-refs.c (vect_prune_runtime_alias_test_list): Factor
>         out code pruning runtime alias checks.
>         * tree-data-ref.c (prune_runtime_alias_test_list): New function
>         factored out from above.
>         * tree-vectorizer.h (struct dr_with_seg_len, dr_with_seg_len_pair_t):
>         Move from ...
>         * tree-data-ref.h (struct dr_with_seg_len, dr_with_seg_len_pair_t):
>         ... to here.
>         (prune_runtime_alias_test_list): New decalaration.

  reply	other threads:[~2017-05-26 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 16:23 Bin Cheng
2017-05-26 11:16 ` Richard Biener [this message]
2017-05-26 14:19   ` Bin.Cheng

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=CAFiYyc2Uf4nQB+G6ajkofFgLhnDBKDWHMFgYJtv-eviNNsAM1w@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).