From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>,
Sergei Trofimovich <slyfox@gentoo.org>
Subject: Re: [PATCH 1/3] Add inhibit_stack_protector to ifuncmain9 [BZ #25680]
Date: Mon, 15 Mar 2021 22:04:28 +0530 [thread overview]
Message-ID: <fa2649b6-31a5-a377-f8f3-385eec8102d5@sourceware.org> (raw)
In-Reply-To: <0f058157-6d2d-0f0c-fc45-ca413283b6e9@linaro.org>
On 3/15/21 7:28 PM, Adhemerval Zanella wrote:
> Ok, they patches itself do look and I don't really want to block them.
> My idea of raising this issues is that besides glibc testsuite we should
> also focus on the consumers and it maybe it would be better to partially
> disable a functionally it is inherent broken in some corner cases.
>
> But if the idea is indeed to get back on this, I am ok with current
> approach.
I've filed #27582 so that I don't forget.
Thanks,
Siddhesh
next prev parent reply other threads:[~2021-03-15 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 10:13 [PATCH v2 0/3] Clean up stack-protector-all build Siddhesh Poyarekar
2021-03-10 10:13 ` [PATCH 1/3] Add inhibit_stack_protector to ifuncmain9 [BZ #25680] Siddhesh Poyarekar
2021-03-10 12:50 ` Adhemerval Zanella
2021-03-12 8:52 ` Siddhesh Poyarekar
2021-03-12 17:34 ` Adhemerval Zanella
2021-03-12 19:55 ` H.J. Lu
2021-03-13 6:01 ` Siddhesh Poyarekar
2021-03-13 13:44 ` H.J. Lu
2021-03-13 6:07 ` Siddhesh Poyarekar
2021-03-15 13:58 ` Adhemerval Zanella
2021-03-15 16:34 ` Siddhesh Poyarekar [this message]
2021-03-15 13:59 ` Adhemerval Zanella
2021-03-10 10:13 ` [PATCH 2/3] Build get-cpuid-feature-leaf.c without stack-protector [BZ #27555] Siddhesh Poyarekar
2021-03-15 13:59 ` Adhemerval Zanella
2021-03-10 10:14 ` [PATCH 3/3] Build libc-start with stack protector for SHARED Siddhesh Poyarekar
2021-03-15 14:00 ` 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=fa2649b6-31a5-a377-f8f3-385eec8102d5@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=slyfox@gentoo.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).