From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [COMMITTED] [PATCH 00/12] S390: Implement __fentry__
Date: Fri, 10 Aug 2018 07:15:00 -0000 [thread overview]
Message-ID: <c303be35-62a8-2cfc-4fd3-f2e2ed1c4bd4@linux.ibm.com> (raw)
In-Reply-To: <751ed82b-c65c-fa06-b8ba-fc6bc2824539@linux.ibm.com>
On 08/07/2018 10:27 AM, Stefan Liebler wrote:
> On 08/02/2018 09:57 AM, Ilya Leoshkevich wrote:
>> This patch series adds the runtime support in glibc for the -mfentry
>> gcc feature introduced in [1] and [2].
>>
>> Patches 1-9 deal with avoiding clobbering %r0 when calling lazily bound
>> functions, so that the new __fentry__ symbol could be called with return
>> address in that register.
>>
>> Patch 10 removes the assumption that only Intel implements __fentry__.
>>
>> Patch 11 adds __fentry__ implementation.
>>
>> Patch 12 is a cleanup of problems in 31-bit mcount, which are similar to
>> those found while implementing 64-bit __fentry__.
>>
>> [1] https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00784.html
>> [2] https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00912.html
>>
>>
>
> Hi,
>
> I've reviewed the s390-specific patches. They are all okay.
>
> I think the move of the Intel-specific __fentry__ defintion into the
> Versions-files of the corresponding sysdeps directories is okay, too.
> Do anybody complain about that?
>
> If not, I plan to commit this patch-series at the end of this week.
> Thank you for implementing the __fentry__ support for s390x.
>
> Bye
> Stefan
>
Committed.
Thanks
Stefan
prev parent reply other threads:[~2018-08-10 7:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 7:58 Ilya Leoshkevich
2018-08-02 7:58 ` [PATCH 01/12] S390: Use symbolic offsets for stack variables in 32-bit _dl_runtime_resolve Ilya Leoshkevich
2018-08-02 7:58 ` [PATCH 03/12] S390: Use symbolic offsets for stack variables in 64-bit _dl_runtime_resolve Ilya Leoshkevich
2018-08-02 7:58 ` [PATCH 02/12] S390: Use symbolic offsets for stack variables in 32-bit _dl_runtime_profile Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 11/12] S390: Implement 64-bit __fentry__ Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 08/12] S390: Do not clobber R0 in 64-bit _dl_runtime_profile Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 05/12] S390: Do not clobber R0 in 32-bit _dl_runtime_resolve Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 12/12] S390: Fix unwind in 32-bit _mcount Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 07/12] S390: Do not clobber R0 in 64-bit _dl_runtime_resolve Ilya Leoshkevich
2018-08-02 7:59 ` [PATCH 09/12] S390: Test that lazy binding does not clobber R0 Ilya Leoshkevich
2018-08-02 8:10 ` [PATCH 10/12] Move __fentry__ version definition to sysdeps/{i386,x86_64} Ilya Leoshkevich
2018-08-02 8:41 ` [PATCH 06/12] S390: Do not clobber R0 in 32-bit _dl_runtime_profile Ilya Leoshkevich
2018-08-02 9:00 ` [PATCH 04/12] S390: Use symbolic offsets for stack variables in 64-bit _dl_runtime_profile Ilya Leoshkevich
2018-08-02 9:17 ` [PATCH 00/12] S390: Implement __fentry__ Florian Weimer
2018-08-02 10:43 ` Ilya Leoshkevich
2018-08-02 18:32 ` Florian Weimer
2018-08-07 8:27 ` Stefan Liebler
2018-08-10 7:15 ` Stefan Liebler [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=c303be35-62a8-2cfc-4fd3-f2e2ed1c4bd4@linux.ibm.com \
--to=stli@linux.ibm.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).