From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Alistair Francis <alistair23@gmail.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Chung-Lin Tang <cltang@codesourcery.com>,
DJ Delorie <dj@redhat.com>
Subject: Re: glibc 2.32 release strategy for ABI changes.
Date: Wed, 8 Jul 2020 10:33:21 +0100 [thread overview]
Message-ID: <20200708093320.GD24937@arm.com> (raw)
In-Reply-To: <ab44870f-4d3d-ea1c-d30c-2ba344a006e6@redhat.com>
The 07/07/2020 17:44, Carlos O'Donell wrote:
> > (a) AArch64 BTI and PAC-RET.
>
> Status?
>
> > (b) Szabolcs's TLS reservation fixes.
> > - Internal ABI changes are OK e.g. GLIBC_PRIVATE.
>
> Reviewed. Needs some fixing up after rseq changes. No semantic problems,
> just needing extra TLS surplus to satisfy 8 module tests e.g. tst-auditmany.
i'm about to post updated version of (a) and (b).
bti and pac-ret were reviewed by Adhemerval and i
think the updated version will be ready for commit.
next prev parent reply other threads:[~2020-07-08 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 21:49 Carlos O'Donell
2020-07-03 22:37 ` Adhemerval Zanella
2020-07-04 3:24 ` Vineet Gupta
2020-07-04 3:37 ` Vineet Gupta
2020-07-04 12:07 ` H.J. Lu
2020-07-06 15:36 ` Joseph Myers
2020-07-06 16:03 ` Carlos O'Donell
2020-07-07 21:44 ` Carlos O'Donell
2020-07-07 22:06 ` Alistair Francis
2020-07-07 22:08 ` Vineet Gupta
2020-07-08 9:33 ` Szabolcs Nagy [this message]
2020-07-08 12:21 ` Szabolcs Nagy
2020-07-08 14:08 ` Szabolcs Nagy
2020-07-08 16:36 ` Szabolcs Nagy
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=20200708093320.GD24937@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair23@gmail.com \
--cc=carlos@redhat.com \
--cc=cltang@codesourcery.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=mathieu.desnoyers@efficios.com \
/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).