Re: Reinstate generic stack checking warning with LRA

2016-03-03 Thread Eric Botcazou
> This works though, ok for trunk? > > 2016-03-03 Jakub Jelinek > > PR ada/70017 > * gcc.dg/pr70017.c (foo): Store 0 to first element of each array. Sure, thanks. -- Eric Botcazou

Re: Reinstate generic stack checking warning with LRA

2016-03-03 Thread Jakub Jelinek
On Thu, Mar 03, 2016 at 12:31:52PM +0100, Eric Botcazou wrote: > > Anyway, looking at pro_and_epilogue dumps, with additional > > -fstack-protector-strong we decrease sp only by 4176, while without it by > > 8224 (on x86_64; the testcase fails on all targets I've tried so far > > ({x86_64,i686,powe

Re: Reinstate generic stack checking warning with LRA

2016-03-03 Thread Eric Botcazou
> Anyway, looking at pro_and_epilogue dumps, with additional > -fstack-protector-strong we decrease sp only by 4176, while without it by > 8224 (on x86_64; the testcase fails on all targets I've tried so far > ({x86_64,i686,powerpc64{,le},s390{,x},aarch64,armv7hl}-linux). Yeah, the threshold is ar

Re: Reinstate generic stack checking warning with LRA

2016-03-02 Thread Jakub Jelinek
On Thu, Mar 03, 2016 at 07:46:49AM +0100, Jakub Jelinek wrote: > On Tue, Mar 01, 2016 at 09:04:54PM +0100, Eric Botcazou wrote: > > When stack checking is entirely done by the middle-end (default if no > > specific > > back-end support or forced by -fstack-check=generic), the checking for the >

Re: Reinstate generic stack checking warning with LRA

2016-03-02 Thread Jakub Jelinek
On Tue, Mar 01, 2016 at 09:04:54PM +0100, Eric Botcazou wrote: > When stack checking is entirely done by the middle-end (default if no > specific > back-end support or forced by -fstack-check=generic), the checking for the > prologue is actually done in the caller with a default range and the ho