Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08 - V3

2017-08-18 Thread Richard Biener
On Mon, Jul 31, 2017 at 7:41 AM, Jeff Law wrote: > This patch introduces some routines for logging of stack clash > protection actions. > > I don't think this patch changed at all relative to V2. Ok. Richard. > > Jeff > > > * function.c (dump_stack_clash_frame_info):

[PATCH][RFA/RFC] Stack clash mitigation patch 03/08 - V3

2017-07-30 Thread Jeff Law
This patch introduces some routines for logging of stack clash protection actions. I don't think this patch changed at all relative to V2. Jeff * function.c (dump_stack_clash_frame_info): New function. * function.h (dump_stack_clash_frame_info): Prototype. (enum

Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08 V2

2017-07-20 Thread Segher Boessenkool
On Tue, Jul 18, 2017 at 11:17:39PM -0600, Jeff Law wrote: > I don't think this patch changed in any significant way since V1. Except the first time you attached the correct patch ;-) Segher

[PATCH][RFA/RFC] Stack clash mitigation patch 03/08 V2 -- right patch attached

2017-07-18 Thread Jeff Law
Opps, I clearly attached the wrong file. -- I don't think this patch changed in any significant way since V1. -- One of the painful aspects of all this code is the amount of target dependent bits that have to be written and tested. I didn't want to be scanning assembly code or RTL for

[PATCH][RFA/RFC] Stack clash mitigation patch 03/08 V2

2017-07-18 Thread Jeff Law
I don't think this patch changed in any significant way since V1. -- One of the painful aspects of all this code is the amount of target dependent bits that have to be written and tested. I didn't want to be scanning assembly code or RTL for prologues. Each target would have to have its own

Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08

2017-07-17 Thread Jeff Law
On 07/17/2017 10:28 AM, Segher Boessenkool wrote: > Hi, > > Just some typos: > > On Tue, Jul 11, 2017 at 03:20:38PM -0600, Jeff Law wrote: >> +/* If debugging dumps are requested, dump infomation about how the > > Typo ("information"). > >> + target handled -fstack-check=clash for the

Re: [PATCH][RFA/RFC] Stack clash mitigation patch 03/08

2017-07-17 Thread Segher Boessenkool
Hi, Just some typos: On Tue, Jul 11, 2017 at 03:20:38PM -0600, Jeff Law wrote: > +/* If debugging dumps are requested, dump infomation about how the Typo ("information"). > + target handled -fstack-check=clash for the prologue. > + > + PROBES describes what if any probes were emitted. > +

[PATCH][RFA/RFC] Stack clash mitigation patch 03/08

2017-07-11 Thread Jeff Law
One of the painful aspects of all this code is the amount of target dependent bits that have to be written and tested. I didn't want to be scanning assembly code or RTL for prologues. Each target would have to have its own scanner which was too painful to contemplate. So instead I settled on