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][1/6]Move compare_tree to tree.c and expose the interface.
Date: Fri, 26 May 2017 11:15:00 -0000 [thread overview]
Message-ID: <CAFiYyc3=CfmmCzySvncYoWbgMkbRqb0bO6y=Oh2e+xy_w8-N2g@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0802MB2176E33A1C87830AC120CB86E7F90@VI1PR0802MB2176.eurprd08.prod.outlook.com>
On Tue, May 23, 2017 at 6:22 PM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This patch set factors out runtime alias check code from tree-vect-data-refs.c
> and tree-vect-loop-manip.c as general interfaces in tree-data-ref.c. With this
> change other optimizers like tree loop distribution could version loop wrto the
> runtime alias checks. During this work, I also found current code has issues
> with negative DR_STEP. This patch set fixes the issue as tracked in PR80815.
>
> This is the first patch simply moves compare_tree to tree.c and exposes it.
> Bootstrap and test on x86_64 and AArch64, is it OK?
I think the name is quite bad for an exported function given for INTEGER_CSTs
it doesn't return anything resembling a comparison result. Also (not
your fault)
it doesn't seem to handle hash collisions nor have a suitable fallback for
trees it doesn't handle.
I don't have a good suggestion for the name but tree.c exported fns should
have higher standards regarding their implementation...
Richard.
> Thanks,
> bin
>
> 2017-05-22 Bin Cheng <bin.cheng@arm.com>
>
> * tree-vect-data-refs.c (compare_tree): Move ...
> * tree.c (compare_tree): ... to here.
> * tree.h (compare_tree): New decalaration.
next prev parent reply other threads:[~2017-05-26 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 16:23 Bin Cheng
2017-05-26 11:15 ` Richard Biener [this message]
2017-05-26 11:31 ` Bin.Cheng
2017-05-26 11:51 ` Richard Biener
2017-05-26 14:12 ` 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='CAFiYyc3=CfmmCzySvncYoWbgMkbRqb0bO6y=Oh2e+xy_w8-N2g@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).