From: Yaakov Selkowitz <yselkowi@redhat.com>
To: newlib@sourceware.org
Subject: [PATCH v1 06/10] ssp: document _FORTIFY_SOURCE with the feature test macros
Date: Wed, 01 Nov 2017 04:53:00 -0000 [thread overview]
Message-ID: <20171101045246.16596-7-yselkowi@redhat.com> (raw)
In-Reply-To: <20171101045246.16596-1-yselkowi@redhat.com>
Signed-off-by: Yaakov Selkowitz <yselkowi@redhat.com>
---
newlib/libc/include/sys/features.h | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/newlib/libc/include/sys/features.h b/newlib/libc/include/sys/features.h
index c9133af57..53a100d50 100644
--- a/newlib/libc/include/sys/features.h
+++ b/newlib/libc/include/sys/features.h
@@ -100,6 +100,9 @@ extern "C" {
* _SVID_SOURCE (deprecated by _DEFAULT_SOURCE)
* _DEFAULT_SOURCE (or none of the above)
* POSIX-1.2008 with BSD and SVr4 extensions
+ *
+ * _FORTIFY_SOURCE = 1 or 2
+ * Object Size Checking function wrappers
*/
#ifdef _GNU_SOURCE
@@ -233,9 +236,11 @@ extern "C" {
* __GNU_VISIBLE
* GNU extensions; enabled with _GNU_SOURCE.
*
+ * __SSP_FORTIFY_LEVEL
+ * Object Size Checking; defined to 0 (off), 1, or 2 in <ssp/ssp.h>.
+ *
* In all cases above, "enabled by default" means either by defining
* _DEFAULT_SOURCE, or by not defining any of the public feature test macros.
- * Defining _GNU_SOURCE makes all of the above avaliable.
*/
#ifdef _ATFILE_SOURCE
--
2.14.3
next prev parent reply other threads:[~2017-11-01 4:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 4:53 [PATCH v1 00/10] Add Stack Smashing Protection and Object Size Checking Yaakov Selkowitz
2017-11-01 4:53 ` [PATCH v1 10/10] cygwin: create libssp compatibility import library Yaakov Selkowitz
2017-11-01 4:53 ` [PATCH v1 05/10] ssp: add Object Size Checking for basic unistd.h functions Yaakov Selkowitz
2017-11-01 4:53 ` Yaakov Selkowitz [this message]
2017-11-01 4:53 ` [PATCH v1 02/10] ssp: add Object Size Checking for basic string functions Yaakov Selkowitz
2017-11-01 4:53 ` [PATCH v1 03/10] ssp: add Object Size Checking for bcopy, bzero Yaakov Selkowitz
2017-11-01 4:53 ` [PATCH v1 01/10] ssp: add APIs for Stack Smashing Protection (-fstack-protector*) Yaakov Selkowitz
2017-11-01 4:58 ` [PATCH v1 08/10] ssp: install headers Yaakov Selkowitz
2017-11-01 5:04 ` [PATCH v1 09/10] cygwin: export SSP functions Yaakov Selkowitz
2017-11-01 5:05 ` [PATCH v1 07/10] ssp: add build infrastructure Yaakov Selkowitz
2017-11-02 8:28 ` [PATCH v1 04/10] ssp: add Object Size Checking for basic stdio functions Yaakov Selkowitz
2017-11-02 14:28 ` [PATCH v1 00/10] Add Stack Smashing Protection and Object Size Checking Corinna Vinschen
2017-11-06 18:40 ` Yaakov Selkowitz
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=20171101045246.16596-7-yselkowi@redhat.com \
--to=yselkowi@redhat.com \
--cc=newlib@sourceware.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).