From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH 0/3] Clean up stack-protector-all build
Date: Tue, 9 Mar 2021 23:42:56 +0530 [thread overview]
Message-ID: <20210309181259.2603144-1-siddhesh@sourceware.org> (raw)
This series of patches cleans up state for when glibc is configured with
--enable-stack-protector=all. Now tests for this build configuration
runs clean with the exception of tst-reload2, which is an unrelated
issue:
https://sourceware.org/bugzilla/show_bug.cgi?id=27537
Siddhesh Poyarekar (3):
Build get-cpuid-feature-leaf.c without stack-protector
Disable stack protector for ifunc resolvers in tests
Build libc-start with stack protector for SHARED
Makeconfig | 4 ++++
csu/Makefile | 22 ++++++++++++----------
elf/Makefile | 4 ----
elf/ifuncmain9.c | 1 +
sysdeps/x86/Makefile | 2 ++
sysdeps/x86/tst-ifunc-isa.h | 2 ++
6 files changed, 21 insertions(+), 14 deletions(-)
--
2.29.2
next reply other threads:[~2021-03-09 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 18:12 Siddhesh Poyarekar [this message]
2021-03-09 18:12 ` [PATCH 1/3] Build get-cpuid-feature-leaf.c without stack-protector Siddhesh Poyarekar
2021-03-10 7:58 ` Florian Weimer
2021-03-09 18:12 ` [PATCH 2/3] Disable stack protector for ifunc resolvers in tests Siddhesh Poyarekar
2021-03-10 7:59 ` Florian Weimer
2021-03-10 9:38 ` Siddhesh Poyarekar
2021-03-10 9:39 ` Florian Weimer
2021-03-10 9:57 ` Siddhesh Poyarekar
2021-03-09 18:12 ` [PATCH 3/3] Build libc-start with stack protector for SHARED Siddhesh Poyarekar
2021-03-10 8:00 ` Florian Weimer
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=20210309181259.2603144-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).