On 08/14/2015 02:17 AM, Richard Biener wrote:
On Tue, Jul 28, 2015 at 11:36 AM, Bin Cheng <bin.ch...@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.
+ c0 = fold_convert (type, c0);
+ c1 = fold_convert (type, c1);
+
+ if (operand_equal_p (var, c0, 0))
I believe if c0 is not already of type type operand-equal_p will never succeed.
It's a bit looser than that. Given two user defined types with the same
signedness & precision operand_equal_p will consider the types OK. One
could argue that it ought to be using the useless type conversion check.
jeff
