Re: [RFC][IPA-VRP] splits out the update_value_range calls from vrp_visit_stmt

2016-08-17 Thread Richard Biener
On Wed, Aug 17, 2016 at 4:27 AM, kugan wrote: > Hi, > > > On 16/08/16 20:58, Richard Biener wrote: >> >> On Tue, Aug 16, 2016 at 9:39 AM, kugan >> wrote: >>> >>> Hi, >>> as said the refactoring that would be appreciated is to split out the update_value_range calls from the worker f

Re: [RFC][IPA-VRP] splits out the update_value_range calls from vrp_visit_stmt

2016-08-16 Thread kugan
Hi, On 16/08/16 20:58, Richard Biener wrote: On Tue, Aug 16, 2016 at 9:39 AM, kugan wrote: Hi, as said the refactoring that would be appreciated is to split out the update_value_range calls from the worker functions so you can call the respective functions from the DOM implementations. That

Re: [RFC][IPA-VRP] splits out the update_value_range calls from vrp_visit_stmt

2016-08-16 Thread Richard Biener
On Tue, Aug 16, 2016 at 9:39 AM, kugan wrote: > Hi, > >> as said the refactoring that would be appreciated is to split out the >> update_value_range calls >> from the worker functions so you can call the respective functions >> from the DOM implementations. >> That they are globbed in vrp_visit_st

[RFC][IPA-VRP] splits out the update_value_range calls from vrp_visit_stmt

2016-08-16 Thread kugan
Hi, as said the refactoring that would be appreciated is to split out the update_value_range calls from the worker functions so you can call the respective functions from the DOM implementations. That they are globbed in vrp_visit_stmt currently is due to the API of the SSA propagator. Here is