public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH v3] Mention _FORTIFY_SOURCE=3 for gcc12 in NEWS
Date: Mon, 31 Jan 2022 19:59:46 +0530	[thread overview]
Message-ID: <b44c7b89-cc7a-e0d0-d4b6-c1d08ef64d31@gotplt.org> (raw)
In-Reply-To: <8a689c7f-ab76-ea29-45b9-67af907966d5@gotplt.org>

Pushed after discussing this on the upstream call today.

Thanks,
Siddhesh

On 30/01/2022 10:42, Siddhesh Poyarekar wrote:
> Carlos, may I push this?  This is pretty much exactly what you suggested 
> with Andreas' suggestion incorporated.
> 
> Thanks,
> Siddhesh
> 
> On 27/01/2022 14:34, Siddhesh Poyarekar via Libc-alpha wrote:
>> Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
>> ---
>>   NEWS | 6 ++++++
>>   1 file changed, 6 insertions(+)
>>
>> diff --git a/NEWS b/NEWS
>> index a9f25d3225..02331f0f02 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -134,6 +134,12 @@ Major new features:
>>     controlling terminal in the new process in a race free manner.  These
>>     functions are GNU extensions.
>> +* Source fortification (_FORTIFY_SOURCE) level 3 is now available for
>> +  applications compiling with glibc and gcc 12 and later. Level 3 
>> leverages
>> +  the __builtin_dynamic_object_size function to deliver additional
>> +  fortification balanced against additional runtime cost (checking 
>> non-constant
>> +  bounds).
>> +
>>   Deprecated and removed features, and other changes affecting 
>> compatibility:
>>   * On x86-64, the LD_PREFER_MAP_32BIT_EXEC environment variable support
> 


      reply	other threads:[~2022-01-31 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  5:36 [PATCH] " Siddhesh Poyarekar
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 [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=b44c7b89-cc7a-e0d0-d4b6-c1d08ef64d31@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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).