From: Richard Biener <rguenther@suse.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>,Bill Schmidt
<wschmidt@linux.ibm.com>,gcc-patches@gcc.gnu.org,Jeff Law
<law@redhat.com>,bin.cheng@linux.alibaba.com,jakub@redhat.com,Kugan
Vivekanandarajah <kugan.vivekanandarajah@linaro.org>
Subject: Re: [PATCH v4 2/3] Add predict_doloop_p target hook
Date: Mon, 17 Jun 2019 12:08:00 -0000 [thread overview]
Message-ID: <1021295E-F884-469F-B3A2-B005007C7656@suse.de> (raw)
In-Reply-To: <20190617095930.GY31586@gate.crashing.org>
On June 17, 2019 11:59:30 AM GMT+02:00, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>On Mon, Jun 17, 2019 at 10:51:49AM +0200, Richard Biener wrote:
>> On Mon, 17 Jun 2019, Kewen.Lin wrote:
>>
>> > Hi Segher and Bill,
>> >
>> > Thanks a lot for your review comments! I've updated the patch
>accordingly.
>> >
>> > The updated one attached.
>>
>> OK. I suppose all low-overhead loop instructions use a decrement to
>zero
>> style iterator?
>
>The documentation says decrement to 0, decrement to -1, and decrement
>to
>any negative are all supported. But all are decrement, yes.
Hmm, so I wonder if we should tell IVOPTS the kind because the IV generated has to match RTL doloops expectations? Thus return an enum value from the hook?
Richard.
>
>Segher
next prev parent reply other threads:[~2019-06-17 12:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 3:37 [PATCH v3 " linkw
2019-05-17 5:31 ` Kugan Vivekanandarajah
2019-05-17 6:15 ` Kewen.Lin
2019-05-17 6:57 ` Segher Boessenkool
2019-05-17 6:49 ` Segher Boessenkool
2019-05-17 7:20 ` Kewen.Lin
2019-05-20 9:28 ` Richard Biener
2019-05-20 10:24 ` Segher Boessenkool
2019-05-20 14:44 ` Jeff Law
2019-05-20 16:38 ` Segher Boessenkool
2019-05-21 6:03 ` Kewen.Lin
2019-05-21 10:20 ` Richard Biener
2019-05-21 12:42 ` Segher Boessenkool
2019-05-21 15:22 ` Jeff Law
2019-05-22 2:07 ` Kewen.Lin
2019-06-11 2:39 ` Kewen.Lin
2019-06-11 12:17 ` Richard Biener
2019-06-13 5:50 ` [PATCH v4 " Kewen.Lin
2019-06-14 21:53 ` Segher Boessenkool
2019-06-14 23:46 ` Bill Schmidt
2019-06-17 2:08 ` Kewen.Lin
2019-06-17 8:51 ` Richard Biener
2019-06-17 9:39 ` Kewen.Lin
2019-06-17 9:59 ` Segher Boessenkool
2019-06-17 12:08 ` Richard Biener [this message]
2019-06-17 13:39 ` Kewen.Lin
2019-06-17 13:44 ` Richard Biener
2019-06-17 14:24 ` Kewen.Lin
2019-05-21 11:09 ` [PATCH v3 " Segher Boessenkool
2019-05-21 9:58 ` Richard Biener
2019-05-21 5:50 ` Kewen.Lin
2019-05-21 6:32 ` Bin.Cheng
2019-05-21 10:36 ` Segher Boessenkool
2019-05-21 3:48 ` Kewen.Lin
2019-05-21 5:28 ` Kewen.Lin
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=1021295E-F884-469F-B3A2-B005007C7656@suse.de \
--to=rguenther@suse.de \
--cc=bin.cheng@linux.alibaba.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=kugan.vivekanandarajah@linaro.org \
--cc=law@redhat.com \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).