Re: [PATCH][PR target/84064] Fix assertion with -fstack-clash-protection

2018-01-30 Thread Jeff Law
On 01/30/2018 12:23 AM, Uros Bizjak wrote: > On Tue, Jan 30, 2018 at 5:48 AM, Jeff Law wrote: >> >> >> >> stack-clash-protection will sometimes force a prologue to use pushes to >> save registers. We try to limit how often that happens as it constrains >> options for generating efficient prologue

Re: [PATCH][PR target/84064] Fix assertion with -fstack-clash-protection

2018-01-29 Thread Uros Bizjak
On Tue, Jan 30, 2018 at 5:48 AM, Jeff Law wrote: > > > > stack-clash-protection will sometimes force a prologue to use pushes to > save registers. We try to limit how often that happens as it constrains > options for generating efficient prologue sequences for common cases. > > We check the value

[PATCH][PR target/84064] Fix assertion with -fstack-clash-protection

2018-01-29 Thread Jeff Law
stack-clash-protection will sometimes force a prologue to use pushes to save registers. We try to limit how often that happens as it constrains options for generating efficient prologue sequences for common cases. We check the value of TO_ALLOCATE in ix86_compute_frame_layout and if it's great