From: Alan Modra <amodra@gmail.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCHv2] powerpc64: Implement TLS using PC-relative addressing
Date: Wed, 27 Jan 2021 21:46:50 +1030 [thread overview]
Message-ID: <20210127111650.GW26219@bubble.grove.modra.org> (raw)
In-Reply-To: <87k0s06a39.fsf@linux.ibm.com>
On Mon, Jan 25, 2021 at 05:22:02PM -0300, Tulio Magno Quites Machado Filho wrote:
> Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org> writes:
>
> > On 21/01/2021 22:29, Tulio Magno Quites Machado Filho via Libc-alpha wrote:
>
> > So, what I recommend you to do is:
> >
> > 1. Change the documentation patch [1] and update the powerpc
> > sysdeps/powerpc/powerpc64/le/configure.ac to check 'as' version
> > instead of 'objcopy'.
>
> This has already been changed in the following patch:
> https://sourceware.org/pipermail/libc-alpha/2021-January/121919.html
>
> It's still missing the configure check, though. I'm working on that.
>
> > 2. Add a configure check for the new TLS using PC-relative and
> > set a new config.h flag (SUPPORT_PPC_TLS_PCREL).
>
> Ack. I'm working on it.
mod-tlsopt-powerpc.c and tls-macros.h are used only by the
testsuite, so don't fuss too much. Hopefully one day those files will
disappear.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2021-01-27 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 19:55 [PATCH] " Tulio Magno Quites Machado Filho
2020-10-01 8:49 ` Florian Weimer
2020-10-01 11:15 ` Alan Modra
2020-10-01 9:01 ` Andreas Schwab
2021-01-22 1:29 ` [PATCHv2] " Tulio Magno Quites Machado Filho
2021-01-25 15:20 ` Tulio Magno Quites Machado Filho
2021-01-25 17:13 ` Adhemerval Zanella
2021-01-25 20:22 ` Tulio Magno Quites Machado Filho
2021-01-27 11:16 ` Alan Modra [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=20210127111650.GW26219@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=tuliom@linux.ibm.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).