Re: [RFC: Patch 1/6 v2] New target hook: max_noce_ifcvt_seq_cost

2016-07-13 Thread Jeff Law
On 06/21/2016 09:50 AM, James Greenhalgh wrote: On Fri, Jun 03, 2016 at 12:39:42PM +0200, Richard Biener wrote: On Thu, Jun 2, 2016 at 6:53 PM, James Greenhalgh wrote: Hi, This patch introduces a new target hook, to be used like BRANCH_COST but with a guaranteed unit of measurement. We want

Re: [RFC: Patch 1/6 v2] New target hook: max_noce_ifcvt_seq_cost

2016-06-30 Thread Bernd Schmidt
On 06/21/2016 05:50 PM, James Greenhalgh wrote: For the default implementation, if the parameters are not set, I just multiply BRANCH_COST through by COSTS_N_INSNS (1) for size and COSTS_N_INSNS (3) for speed. I know this is not ideal, but I'm still short of ideas on how best to form the default

Re: [RFC: Patch 1/6 v2] New target hook: max_noce_ifcvt_seq_cost

2016-06-21 Thread Bernhard Reutner-Fischer
On June 21, 2016 5:50:26 PM GMT+02:00, James Greenhalgh wrote: > >On Fri, Jun 03, 2016 at 12:39:42PM +0200, Richard Biener wrote: >> On Thu, Jun 2, 2016 at 6:53 PM, James Greenhalgh >> wrote: >> > >> > Hi, >> > >> > This patch introduces a new target hook, to be used like >BRANCH_COST but >> > w

[RFC: Patch 1/6 v2] New target hook: max_noce_ifcvt_seq_cost

2016-06-21 Thread James Greenhalgh
On Fri, Jun 03, 2016 at 12:39:42PM +0200, Richard Biener wrote: > On Thu, Jun 2, 2016 at 6:53 PM, James Greenhalgh > wrote: > > > > Hi, > > > > This patch introduces a new target hook, to be used like BRANCH_COST but > > with a guaranteed unit of measurement. We want this to break away from > > t