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): New function.
>
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 stack_cl
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
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 prologue
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 sca
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 prologu
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.
> +
>
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 hav