gnu.org; nd ; bonz...@gnu.org;
> d...@redhat.com; nero...@gcc.gnu.org; aol...@redhat.com;
> ralf.wildenh...@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework]
> Allow setting of stack-clash via configure options. [Patch (4/6)]
>
> On 07/24/2018 08:14 A
On 07/24/2018 08:14 AM, Tamar Christina wrote:
> Hi All,
>
> Here's an updated patch with documentation.
>
>
> Ok for trunk?
>
> Thanks,
> Tamar
>
> gcc/
> 2018-07-24 Tamar Christina
>
> PR target/86486
> * configure.ac: Add stack-clash-protection-guard-size.
> *
com; nero...@gcc.gnu.org;
> ralf.wildenh...@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework]
> Allow setting of stack-clash via configure options. [Patch (4/6)]
>
> On Jul 25, 2018, Tamar Christina wrote:
>
> > gcc/
> > 20
On Jul 25, 2018, Tamar Christina wrote:
> gcc/
> 2018-07-25 Tamar Christina
> PR target/86486
> * configure.ac: Add stack-clash-protection-guard-size.
> * doc/install.texi: Document it.
> * config.in (DEFAULT_STK_CLASH_GUARD_SIZE): New.
> * params.def: Update
Oliva
> Sent: Tuesday, July 24, 2018 20:24
> To: Tamar Christina
> Cc: Joseph Myers ; Jeff Law
> ; gcc-patches@gcc.gnu.org; nd ;
> bonz...@gnu.org; d...@redhat.com; nero...@gcc.gnu.org;
> ralf.wildenh...@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framewor
Hello, Christina,
On Jul 24, 2018, Tamar Christina wrote:
> gcc/
> 2018-07-24 Tamar Christina
> PR target/86486
> * configure.ac: Add stack-clash-protection-guard-size.
> * doc/install.texi: Document it.
> * config.in (DEFAULT_STK_CLASH_GUARD_SIZE): New.
> *
Hi All,
Here's an updated patch with documentation.
Ok for trunk?
Thanks,
Tamar
gcc/
2018-07-24 Tamar Christina
PR target/86486
* configure.ac: Add stack-clash-protection-guard-size.
* doc/install.texi: Document it.
* config.in
On Tue, 24 Jul 2018, tamar.christ...@arm.com wrote:
> This patch defines a configure option to allow the setting of the default
> guard size via configure flags when building the target.
If you add a configure option, you must also add documentation for it in
install.texi.
--
Joseph S. Myers
t: Monday, July 23, 2018 23:19
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ;
> jos...@codesourcery.com; bonz...@gnu.org; d...@redhat.com;
> nero...@gcc.gnu.org; aol...@redhat.com; ralf.wildenh...@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework]
On 07/20/2018 09:39 AM, Tamar Christina wrote:
>>
>> On 07/20/2018 05:03 AM, Tamar Christina wrote:
Understood. Thanks for verifying. I wonder if we could just bury
this entirely in the aarch64 config files and not expose the default into
>> params.def?
>>>
>>> Burying it in
>
> On 07/20/2018 05:03 AM, Tamar Christina wrote:
> >> Understood. Thanks for verifying. I wonder if we could just bury
> >> this entirely in the aarch64 config files and not expose the default into
> params.def?
> >>
> >
> > Burying it in config.gcc isn't ideal because if your C runtime is
>
On 07/20/2018 05:03 AM, Tamar Christina wrote:
>> Understood. Thanks for verifying. I wonder if we could just bury this
>> entirely
>> in the aarch64 config files and not expose the default into params.def?
>>
>
> Burying it in config.gcc isn't ideal because if your C runtime is
>
@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework]
> Allow setting of stack-clash via configure options. [Patch (4/6)]
>
> On 07/19/2018 06:55 AM, Tamar Christina wrote:
> >>>
> >>> What's the purpose of including auto-host in params-lis
On 07/19/2018 06:55 AM, Tamar Christina wrote:
>>>
>>> What's the purpose of including auto-host in params-list and
>>> params-options? It seems like you're putting a property of the target
>>> (guard size) into the wrong place (auto-host.h).
>>>
>>
>> The reason for this is because there's a
@gmx.de
> Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework]
> Allow setting of stack-clash via configure options. [Patch (4/6)]
>
> Hi Jeff,
>
> The 07/11/2018 20:21, Jeff Law wrote:
> > On 07/11/2018 05:22 AM, Tamar Christina wrote:
> > > Hi
Hi Jeff,
The 07/11/2018 20:21, Jeff Law wrote:
> On 07/11/2018 05:22 AM, Tamar Christina wrote:
> > Hi All,
> >
> > This patch defines a configure option to allow the setting of the default
> > guard size via configure flags when building the target.
> >
> > The new flag is:
> >
> > *
On 07/11/2018 05:22 AM, Tamar Christina wrote:
> Hi All,
>
> This patch defines a configure option to allow the setting of the default
> guard size via configure flags when building the target.
>
> The new flag is:
>
> * --with-stack-clash-protection-guard-size=
>
> The value of configured
17 matches
Mail list logo
