From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Bin Cheng <bin.cheng@arm.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH GCC]Improve bound information in loop niter analysis
Date: Thu, 13 Aug 2015 08:27:00 -0000 [thread overview]
Message-ID: <CAHFci2-H2i7YPOq2Hrg9XvKfWhJ_uG40kfdQSzWWLd0DF9-+0Q@mail.gmail.com> (raw)
In-Reply-To: <000401d0c918$d7a2e780$86e8b680$@arm.com>
Ping.
Thanks,
bin
On Tue, Jul 28, 2015 at 5:36 PM, Bin Cheng <bin.cheng@arm.com> wrote:
> Hi,
> Loop niter computes inaccurate bound information for different loops. This
> patch is to improve it by using loop initial condition in
> determine_value_range. Generally, loop niter is computed by subtracting
> start var from end var in loop exit condition. Moreover, loop bound is
> computed using value range information of both start and end variables.
> Basic idea of this patch is to check if loop initial condition implies more
> range information for both start/end variables. If yes, we refine range
> information and use that to compute loop bound.
> With this improvement, more accurate loop bound information is computed for
> test cases added by this patch.
>
> Is it OK?
>
> Thanks,
> bin
>
> 2015-07-28 Bin Cheng <bin.cheng@arm.com>
>
> * tree-ssa-loop-niter.c (refine_value_range_using_guard): New.
> (determine_value_range): Call refine_value_range_using_guard for
> each loop initial condition to improve value range.
>
> gcc/testsuite/ChangeLog
> 2015-07-28 Bin Cheng <bin.cheng@arm.com>
>
> * gcc.dg/tree-ssa/loop-bound-1.c: New test.
> * gcc.dg/tree-ssa/loop-bound-3.c: New test.
> * gcc.dg/tree-ssa/loop-bound-5.c: New test.
next prev parent reply other threads:[~2015-08-13 8:26 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 [this message]
2015-08-13 22:10 ` Jeff Law
2015-08-14 3:13 ` Bin.Cheng
2015-08-14 18:32 ` Jeff Law
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=CAHFci2-H2i7YPOq2Hrg9XvKfWhJ_uG40kfdQSzWWLd0DF9-+0Q@mail.gmail.com \
--to=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).