From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Mention _FORTIFY_SOURCE=3 for gcc12 in NEWS
Date: Thu, 27 Jan 2022 00:59:29 -0500 [thread overview]
Message-ID: <241a1e71-1749-7ec2-4a12-9cf9e4864f8d@redhat.com> (raw)
In-Reply-To: <20220127053645.1173238-1-siddhesh@sourceware.org>
On 1/27/22 00:36, Siddhesh Poyarekar wrote:
> 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.
Suggest:
* Source fortification (_FORTIFY_SOURCE) level 3 is now available for applications
compiling with glibc and gcc 12 and later. Level 3 leverages __builtin_dynamic_object_size()
to deliver additional fortification balanced against additional runtime cost (checking
non-constant bounds).
Please post v2.
> +
> Deprecated and removed features, and other changes affecting compatibility:
>
> * On x86-64, the LD_PREFER_MAP_32BIT_EXEC environment variable support
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-01-27 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 5:36 Siddhesh Poyarekar
2022-01-27 5:59 ` Carlos O'Donell [this message]
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=241a1e71-1749-7ec2-4a12-9cf9e4864f8d@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).