From: Alexandre Oliva <oliva@gnu.org>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: Joseph Myers <joseph@codesourcery.com>, Jeff Law <law@redhat.com>,
"gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
nd <nd@arm.com>, "bonzini\@gnu.org" <bonzini@gnu.org>,
"dj\@redhat.com" <dj@redhat.com>,
"neroden\@gcc.gnu.org" <neroden@gcc.gnu.org>,
"Ralf.Wildenhues\@gmx.de" <Ralf.Wildenhues@gmx.de>
Subject: Re: [PATCH][GCC][front-end][build-machinery][opt-framework] Allow setting of stack-clash via configure options. [Patch (4/6)]
Date: Thu, 26 Jul 2018 07:46:00 -0000 [thread overview]
Message-ID: <orfu067833.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <HE1SPR8PMB3137D4835A66F38117CD378FF540@HE1SPR8PMB313.eurprd08.prod.outlook.com> (Tamar Christina's message of "Wed, 25 Jul 2018 11:08:59 +0000")
On Jul 25, 2018, Tamar Christina <Tamar.Christina@arm.com> wrote:
> gcc/
> 2018-07-25 Tamar Christina <tamar.christina@arm.com>
> 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 comment for guard-size.
> (PARAM_STACK_CLASH_PROTECTION_GUARD_SIZE,
> PARAM_STACK_CLASH_PROTECTION_PROBE_INTERVAL): Update description.
> * configure: Regenerate.
Thanks. No objections from me. I don't see any use of the new config
knob, though; assuming it's in a subsequent patch, I guess this one is
fine, but I'm not sure I'm entitled to approve it.
--
Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo
Be the change, be Free! FSF Latin America board member
GNU Toolchain Engineer Free Software Evangelist
next prev parent reply other threads:[~2018-07-26 7:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 11:22 Tamar Christina
2018-07-11 19:21 ` Jeff Law
2018-07-12 17:45 ` Tamar Christina
2018-07-19 12:56 ` Tamar Christina
2018-07-19 17:31 ` Jeff Law
2018-07-20 11:03 ` Tamar Christina
2018-07-20 15:16 ` Jeff Law
2018-07-20 15:39 ` Tamar Christina
2018-07-23 22:18 ` Jeff Law
2018-07-24 10:26 ` tamar.christina
2018-07-24 10:34 ` Joseph Myers
2018-07-24 14:14 ` Tamar Christina
2018-07-24 19:24 ` Alexandre Oliva
2018-07-25 11:09 ` Tamar Christina
2018-07-26 7:46 ` Alexandre Oliva [this message]
2018-07-26 11:08 ` Tamar Christina
2018-08-03 18:03 ` Jeff Law
2018-10-09 6:38 ` Tamar Christina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=orfu067833.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=Tamar.Christina@arm.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--cc=nd@arm.com \
--cc=neroden@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).