Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-31 Thread Tamar Christina
gen; Maxim Kuvyrkov; GCC Patches; nd Subject: Re: [PATCH] Fix computation of register limit for -fsched-pressure On Fri, Oct 28, 2016 at 12:27 PM, Tamar Christina wrote: > Looking at it again, > > it seems to be that the testcase should be adjusted. > There's no actual spilling. It ju

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-28 Thread Pat Haugen
On 10/28/2016 06:38 AM, Bin.Cheng wrote: > On Fri, Oct 28, 2016 at 12:27 PM, Tamar Christina > wrote: >> > Looking at it again, >> > >> > it seems to be that the testcase should be adjusted. >> > There's no actual spilling. It just uses more registers than before due to >> > the scheduling. > Sor

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-28 Thread Bin.Cheng
ina > Sent: Friday, October 28, 2016 10:53:20 AM > To: Pat Haugen; Maxim Kuvyrkov > Cc: GCC Patches; nd > Subject: Re: [PATCH] Fix computation of register limit for -fsched-pressure > > Forwarding to list as well. > > From: Tamar

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-28 Thread Tamar Christina
f of Tamar Christina Sent: Friday, October 28, 2016 10:53:20 AM To: Pat Haugen; Maxim Kuvyrkov Cc: GCC Patches; nd Subject: Re: [PATCH] Fix computation of register limit for -fsched-pressure Forwarding to list as well. From: Tamar Christina Sent: Friday, Oc

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-28 Thread Tamar Christina
Forwarding to list as well. From: Tamar Christina Sent: Friday, October 28, 2016 10:52:17 AM To: Pat Haugen; Maxim Kuvyrkov Cc: GCC Patches Subject: Re: [PATCH] Fix computation of register limit for -fsched-pressure Hi Pat, The commit seems to be causing

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-18 Thread Pat Haugen
On 10/18/2016 05:31 AM, Maxim Kuvyrkov wrote: >> > I see your point and agree that current code isn't optimal. However, I >> > don't think your patch is accurate either. Consider >> > https://gcc.gnu.org/onlinedocs/gccint/Register-Basics.html and let's >> > assume that FIXED_REGISTERS in class

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-18 Thread Maxim Kuvyrkov
> On Oct 18, 2016, at 1:27 PM, Maxim Kuvyrkov wrote: > >> >> On Oct 17, 2016, at 7:21 PM, Pat Haugen wrote: >> >> On 10/17/2016 08:17 AM, Maxim Kuvyrkov wrote: The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html, attempted to scale down the register limit used b

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-18 Thread Maxim Kuvyrkov
> On Oct 17, 2016, at 7:21 PM, Pat Haugen wrote: > > On 10/17/2016 08:17 AM, Maxim Kuvyrkov wrote: >>> The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html, >>> attempted to scale down the register limit used by -fsched-pressure for the >>> case where the block in question

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-17 Thread Pat Haugen
On 10/17/2016 08:17 AM, Maxim Kuvyrkov wrote: >> The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html, >> attempted to scale down the register limit used by -fsched-pressure for the >> case where the block in question executes as frequently as the entry block >> to just the c

Re: [PATCH] Fix computation of register limit for -fsched-pressure

2016-10-17 Thread Maxim Kuvyrkov
> On Oct 7, 2016, at 6:08 PM, Pat Haugen wrote: > > The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html, > attempted to scale down the register limit used by -fsched-pressure for the > case where the block in question executes as frequently as the entry block to > just the

[PATCH] Fix computation of register limit for -fsched-pressure

2016-10-07 Thread Pat Haugen
The patch here, https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01872.html, attempted to scale down the register limit used by -fsched-pressure for the case where the block in question executes as frequently as the entry block to just the call_clobbered (i.e. call_used) regs. But the code is actua