From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118837 invoked by alias); 14 Aug 2015 18:28:26 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 118824 invoked by uid 89); 14 Aug 2015 18:28:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 14 Aug 2015 18:28:24 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id E4D4C19CB83; Fri, 14 Aug 2015 18:28:22 +0000 (UTC) Received: from localhost.localdomain (ovpn-113-104.phx2.redhat.com [10.3.113.104]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t7EISMk6020077; Fri, 14 Aug 2015 14:28:22 -0400 Subject: Re: [PATCH GCC]Improve bound information in loop niter analysis To: "Bin.Cheng" References: <000401d0c918$d7a2e780$86e8b680$@arm.com> <55CD156B.3030506@redhat.com> Cc: Bin Cheng , gcc-patches List From: Jeff Law Message-ID: <55CE3346.4000406@redhat.com> Date: Fri, 14 Aug 2015 18:32:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00823.txt.bz2 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