On Wed, Oct 12, 2016 at 8:35 AM, kugan
wrote:
> Hi Richard,
>
>
> On 12/10/16 00:14, Richard Biener wrote:
>>
>> On Tue, Oct 11, 2016 at 2:57 AM, kugan
>> wrote:
>>>
>>> Hi Richard,
>>> Hi Richard,
>>>
>>> On 10/10/16 20:13,
Hi Richard,
On 12/10/16 00:14, Richard Biener wrote:
On Tue, Oct 11, 2016 at 2:57 AM, kugan
wrote:
Hi Richard,
Hi Richard,
On 10/10/16 20:13, Richard Biener wrote:
On Sat, Oct 8, 2016 at 9:38 PM, kugan
wrote:
Hi
On Tue, Oct 11, 2016 at 2:57 AM, kugan
wrote:
> Hi Richard,
>
>
> On 10/10/16 20:13, Richard Biener wrote:
>>
>> On Sat, Oct 8, 2016 at 9:38 PM, kugan
>> wrote:
>>>
>>> Hi Richard,
>>>
>>> Thanks for the review.
>>> On
Hi Richard,
On 10/10/16 20:13, Richard Biener wrote:
On Sat, Oct 8, 2016 at 9:38 PM, kugan wrote:
Hi Richard,
Thanks for the review.
On 07/10/16 20:11, Richard Biener wrote:
On Fri, Oct 7, 2016 at 12:00 AM, kugan
wrote:
On Sat, Oct 8, 2016 at 9:38 PM, kugan wrote:
> Hi Richard,
>
> Thanks for the review.
> On 07/10/16 20:11, Richard Biener wrote:
>>
>> On Fri, Oct 7, 2016 at 12:00 AM, kugan
>> wrote:
>>>
>>> Hi,
>>>
>>> In vrp
Hi Richard,
Thanks for the review.
On 07/10/16 20:11, Richard Biener wrote:
On Fri, Oct 7, 2016 at 12:00 AM, kugan
wrote:
Hi,
In vrp intersect_ranges, Richard recently changed it to create integer value
ranges when it is integer singleton.
Maybe we should
On Fri, Oct 7, 2016 at 12:00 AM, kugan
wrote:
> Hi,
>
> In vrp intersect_ranges, Richard recently changed it to create integer value
> ranges when it is integer singleton.
>
> Maybe we should do the same when the other range is a complex ranges with
> SSA_NAME
Hi,
In vrp intersect_ranges, Richard recently changed it to create integer
value ranges when it is integer singleton.
Maybe we should do the same when the other range is a complex ranges
with SSA_NAME (like [x+2, +INF])?
Attached patch tries to do this. There are cases where it will be