From: Aurelien Jarno <aurelien@aurel32.net>
To: libc-alpha@sourceware.org
Subject: Re: [2.27 COMMITTED 1/3] RISC-V: Do not initialize $gp in TLS macros.
Date: Mon, 19 Mar 2018 18:44:00 -0000 [thread overview]
Message-ID: <20180319184406.up73ea6ymwl674va@aurel32.net> (raw)
In-Reply-To: <20180319184208.23770-1-aurelien@aurel32.net>
On 2018-03-19 19:42, Aurelien Jarno wrote:
> From: DJ Delorie <dj@redhat.com>
>
> RISC-V TLS doesn't require GP to be initialized, and doing so breaks
> TLS in a shared object.
>
> (cherry picked from commit 8090720a87e42fddc31396f6126112d4b8014d8e)
> ---
> ChangeLog | 4 ++++
> sysdeps/riscv/tls-macros.h | 20 +++-----------------
> 2 files changed, 7 insertions(+), 17 deletions(-)
Oops as the subject says, those patches are for 2.27. Sorry for sending
them to the wrong list, please ignore.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2018-03-19 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 18:42 Aurelien Jarno
2018-03-19 18:42 ` [2.27 COMMITTED 3/3] Update ChangeLog for BZ 22884 - riscv fmax/fmin Aurelien Jarno
2018-03-19 18:42 ` [2.27 COMMITTED 2/3] RISC-V: fmax/fmin: Handle signalling NaNs correctly Aurelien Jarno
2018-03-19 18:44 ` Aurelien Jarno [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=20180319184406.up73ea6ymwl674va@aurel32.net \
--to=aurelien@aurel32.net \
--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).