From: Corinna Vinschen <vinschen@redhat.com>
To: Christian Franke <Christian.Franke@t-online.de>
Cc: newlib@sourceware.org
Subject: Re: [PATCH] ssp: add support for _FORTIFY_SOURCE=3
Date: Mon, 29 Jan 2024 16:29:49 +0100 [thread overview]
Message-ID: <ZbfEbS-SQx9q1lal@calimero.vinschen.de> (raw)
In-Reply-To: <76c5d1ab-b8bb-5347-b39c-f13550555d3f@t-online.de>
On Jan 26 17:29, Christian Franke wrote:
> _FORTIFY_SOURCE=3 is already supported by glibc and MinGW-w64 headers.
>
> Tested on Cygwin with current gcc 13.2.1 test release.
Pushed.
Thanks,
Corinna
prev parent reply other threads:[~2024-01-29 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 16:29 Christian Franke
2024-01-29 15:29 ` Corinna Vinschen [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=ZbfEbS-SQx9q1lal@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=Christian.Franke@t-online.de \
--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).