Re: [PATCH] Assuage ICE in VRP with [1, X] + UINT_MAX (PR tree-optimization/71031)

On May 19, 2016 5:14:24 PM GMT+02:00, Marek Polacek wrote: >On Thu, May 19, 2016 at 03:54:05PM +0200, Richard Biener wrote: >> On Thu, 19 May 2016, Marek Polacek wrote: >> >> > Since Bin's changes to the niter analysis in r231097, we find >ourselves in >> > a situation where

Re: [PATCH] Assuage ICE in VRP with [1, X] + UINT_MAX (PR tree-optimization/71031)

On Thu, May 19, 2016 at 03:54:05PM +0200, Richard Biener wrote: > On Thu, 19 May 2016, Marek Polacek wrote: > > > Since Bin's changes to the niter analysis in r231097, we find ourselves in > > a situation where extract_range_from_binary_expr is given [1, od_5] + > > UINT_MAX > > on type

Re: [PATCH] Assuage ICE in VRP with [1, X] + UINT_MAX (PR tree-optimization/71031)

On Thu, 19 May 2016, Marek Polacek wrote: > Since Bin's changes to the niter analysis in r231097, we find ourselves in > a situation where extract_range_from_binary_expr is given [1, od_5] + UINT_MAX > on type unsigned. We combine the lower bounds, which is 1 + UINT_MAX = > 0(OVF). > We then

[PATCH] Assuage ICE in VRP with [1, X] + UINT_MAX (PR tree-optimization/71031)

Since Bin's changes to the niter analysis in r231097, we find ourselves in a situation where extract_range_from_binary_expr is given [1, od_5] + UINT_MAX on type unsigned. We combine the lower bounds, which is 1 + UINT_MAX = 0(OVF). We then combine the upper bounds, because the max_op0 is not a