From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <suzanne.jeff.law@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFA/RFC] Stack clash mitigation patch 02/08
Date: Thu, 13 Jul 2017 01:44:00 -0000 [thread overview]
Message-ID: <20170713014406.GX13471@gate.crashing.org> (raw)
In-Reply-To: <8a9cdbc9-dc96-e793-0147-3f09af2a26fa@gmail.com>
On Tue, Jul 11, 2017 at 03:20:12PM -0600, Jeff Law wrote:
> * conifg/mips/mips.c (mips_expand_prologue): Likewise.
Typo ("conifg").
> --- a/gcc/defaults.h
> +++ b/gcc/defaults.h
> @@ -1408,8 +1408,11 @@ see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
> #endif
>
> /* The default is not to move the stack pointer. */
> +/* The default is not to move the stack pointer, unless we are using
> + stack clash prevention stack checking. */
> #ifndef STACK_CHECK_MOVING_SP
> -#define STACK_CHECK_MOVING_SP 0
> +#define STACK_CHECK_MOVING_SP\
> + (flag_stack_check == STACK_CLASH_BUILTIN_STACK_CHECK)
> #endif
Missing space before that backslash.
The documentation for STACK_CHECK_CONFIG_SP needs updating (its default
is no longer zero, for one).
I don't really see why this is so complicated, and why the rs6000
target changes (a later patch) are so big. Why isn't it just simple
patches to allocate_stack (and the prologue thing), that check the
flag and if it is set do some probes?
I'll go sleep now, maybe I'll see it in the morning :-)
Segher
next prev parent reply other threads:[~2017-07-13 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:20 Jeff Law
2017-07-13 1:44 ` Segher Boessenkool [this message]
2017-07-13 22:54 ` Jeff Law
2017-07-14 16:28 ` Jeff Law
2017-07-17 17:46 ` Jeff Law
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=20170713014406.GX13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=suzanne.jeff.law@gmail.com \
/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).