From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Cc: fweimer@redhat.com
Subject: Re: [PATCH] Enable _FORTIFY_SOURCE=3 for gcc 12 and above
Date: Sat, 18 Dec 2021 01:00:15 +0530 [thread overview]
Message-ID: <9e05190c-1778-4fba-640b-8dac9cc9f758@sourceware.org> (raw)
In-Reply-To: <369f5904-4be8-90e8-0174-1a5f874e48b8@linaro.org>
On 12/18/21 00:34, Adhemerval Zanella wrote:
> I am not sure I am following what is happening here, is the test wrong for
> _FORTIFY_SOURCE=3, our _FORTIFY_SOURCE=3 lacking some hardening, or missing
> upstream gcc support?
It's missing some support upstream. Basically the series is this:
https://patchwork.sourceware.org/project/gcc/list/?series=5387&state=*
where I've committed 1/6 and 2/6, thus adding
__builtin_dynamic_object_size identification to gcc. However, the
actual dynamic expression generation is in patches 3-6, which is why the
tests are failing.
I may not be able to finish updating and pushing all the patches before
glibc freeze.
Siddhesh
next prev parent reply other threads:[~2021-12-17 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 4:07 Siddhesh Poyarekar
2021-12-17 13:17 ` Adhemerval Zanella
2021-12-17 13:54 ` Siddhesh Poyarekar
2021-12-17 15:24 ` Siddhesh Poyarekar
2021-12-17 19:04 ` Adhemerval Zanella
2021-12-17 19:30 ` Siddhesh Poyarekar [this message]
2021-12-17 19:48 ` Adhemerval Zanella
2021-12-17 19:50 ` Siddhesh Poyarekar
2022-01-12 4:14 ` Siddhesh Poyarekar
2022-01-12 12:52 ` Adhemerval Zanella
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=9e05190c-1778-4fba-640b-8dac9cc9f758@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--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).