From: Gerald Pfeifer <gerald@pfeifer.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [patch] configure option to override TARGET_LIBC_PROVIDES_SSP
Date: Wed, 11 Oct 2017 14:22:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1710111620070.6885@anthias.pfeifer.com> (raw)
In-Reply-To: <59DBD73C.2030308@codesourcery.com>
On Mon, 9 Oct 2017, Sandra Loosemore wrote:
>> The install.texi documentation for --disable-libssp only says "Specify
> that the run-time libraries for stack smashing protection should not be
>> built.". I think it needs updating to mention these additional effects as
>> well.
> Oops. :") How about this version?
Makes sense to me, thanks. (Though better give Joseph a day or two
to chime in as well, since he spotted this originally.)
Gerald
next prev parent reply other threads:[~2017-10-11 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 7:53 Sandra Loosemore
2017-10-09 15:17 ` Joseph Myers
2017-10-09 20:10 ` Sandra Loosemore
2017-10-11 14:22 ` Gerald Pfeifer [this message]
2017-10-26 17:13 ` PING " Sandra Loosemore
2017-10-30 23:58 ` Joseph Myers
2017-10-31 1:20 ` 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=alpine.LSU.2.21.1710111620070.6885@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=sandra@codesourcery.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).