From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] Mention _FORTIFY_SOURCE=3 for gcc12 in NEWS
Date: Thu, 27 Jan 2022 11:06:45 +0530 [thread overview]
Message-ID: <20220127053645.1173238-1-siddhesh@sourceware.org> (raw)
Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
---
NEWS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/NEWS b/NEWS
index a9f25d3225..58fb1f148d 100644
--- a/NEWS
+++ b/NEWS
@@ -134,6 +134,8 @@ Major new features:
controlling terminal in the new process in a race free manner. These
functions are GNU extensions.
+* _FORTIFY_SOURCE=3 is now enabled for gcc 12 and later.
+
Deprecated and removed features, and other changes affecting compatibility:
* On x86-64, the LD_PREFER_MAP_32BIT_EXEC environment variable support
--
2.34.1
next reply other threads:[~2022-01-27 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 5:36 Siddhesh Poyarekar [this message]
2022-01-27 5:59 ` Carlos O'Donell
2022-01-27 7:24 ` [PATCH v2] " Siddhesh Poyarekar
2022-01-27 8:51 ` Andreas Schwab
2022-01-27 9:04 ` [PATCH v3] " Siddhesh Poyarekar
2022-01-30 5:12 ` Siddhesh Poyarekar
2022-01-31 14:29 ` Siddhesh Poyarekar
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=20220127053645.1173238-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@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).