From: Jeff Law <law@redhat.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: Bin Cheng <bin.cheng@arm.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH GCC]Improve bound information in loop niter analysis
Date: Fri, 14 Aug 2015 18:32:00 -0000 [thread overview]
Message-ID: <55CE3346.4000406@redhat.com> (raw)
In-Reply-To: <CAHFci28-o-htn7TnU4N6bcK5WiusCrcOVB=2r=vqfDHV_PzA9Q@mail.gmail.com>
On 08/13/2015 09:06 PM, Bin.Cheng wrote:
>
> Thanks for the comment.
> IIUC, the niter information in struct tree_niter_desc means the number
> of executions of the latch of the loop, so it's 254, rather than 255.
> And same the bound information. Of course, statements in the loop
> body could execute bound+1 times depending on its position in loop.
> For example, struct nb_iter_bound is to describe number of iterations
> of statements(exit conditions).
Ah, if we go to tree_niter_desc, niter is defined as the # executions of
the loop latch. That's what I was missing. Now back to the real review
work :-)
jeff
next prev parent reply other threads:[~2015-08-14 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 10:11 Bin Cheng
2015-08-13 8:27 ` Bin.Cheng
2015-08-13 22:10 ` Jeff Law
2015-08-14 3:13 ` Bin.Cheng
2015-08-14 18:32 ` Jeff Law [this message]
2015-08-14 8:28 ` Richard Biener
2015-08-14 18:47 ` Jeff Law
2015-08-17 10:06 ` Bin.Cheng
2015-08-17 11:16 ` Ajit Kumar Agarwal
2015-08-17 11:38 ` Ajit Kumar Agarwal
2015-08-18 7:53 ` Bin.Cheng
2015-08-18 8:16 ` Ajit Kumar Agarwal
2015-08-18 8:51 ` Richard Biener
2015-08-18 9:09 ` Bin.Cheng
2015-08-18 18:38 ` Jeff Law
2015-08-19 2:45 ` 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=55CE3346.4000406@redhat.com \
--to=law@redhat.com \
--cc=amker.cheng@gmail.com \
--cc=bin.cheng@arm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).