From: Jeff Law <law@redhat.com>
To: Magnus Granberg <zorry@gentoo.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PING] Re: [PATCH] New configure option to default enable Smart Stack Protection
Date: Wed, 19 Aug 2015 22:11:00 -0000 [thread overview]
Message-ID: <55D4FE1E.2080207@redhat.com> (raw)
In-Reply-To: <1924864.DoOlOdAJp4@laptop1.gw.ume.nu>
On 07/13/2015 07:20 AM, Magnus Granberg wrote:
> Patch updated and tested on x86_64-unknown-linux-gnu (Gentoo)
>
> Changlogs
> /gcc
> 2015-07-05 Magnus Granberg<zorry@gentoo.org>
>
> * common.opt (fstack-protector): Initialize to -1.
> (fstack-protector-all): Likewise.
> (fstack-protector-strong): Likewise.
> (fstack-protector-explicit): Likewise.
> * configure.ac: Add --enable-default-ssp.
> * defaults.h (DEFAULT_FLAG_SSP): New. Default SSP to strong.
> * opts.c (finish_options): Update opts->x_flag_stack_protect if it is -1.
> * doc/install.texi: Document --enable-default-ssp.
> * config.in: Regenerated.
> * configure: Likewise.
>
> /testsuite
> 2015-07-13 Magnus Granberg<zorry@gentoo.org>
>
> * lib/target-supports.exp
> (check_effective_target_fstack_protector_enabled): New test.
> * gcc.target/i386/ssp-default.c: New test.
Sorry for the delay, it seems nobody picked this up.
It's a nit, but the feature is "Stack Smashing Protection", not "Smart
Stack Protection". I'll fix that nit and install your change.
Thanks!
Jeff
prev parent reply other threads:[~2015-08-19 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 23:02 Magnus Granberg
2015-07-05 22:22 ` Magnus Granberg
2015-07-13 13:21 ` [PING] " Magnus Granberg
2015-07-20 14:47 ` Magnus Granberg
2015-07-28 19:00 ` Magnus Granberg
2015-08-19 22:11 ` Jeff Law [this message]
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=55D4FE1E.2080207@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zorry@gentoo.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).