From: Andreas Schwab <schwab@linux-m68k.org>
To: Tulio Magno Quites Machado Filho via Libc-alpha
<libc-alpha@sourceware.org>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
amodra@gmail.com
Subject: Re: [PATCH] powerpc64: Implement TLS using PC-relative addressing
Date: Thu, 01 Oct 2020 11:01:53 +0200 [thread overview]
Message-ID: <87r1qi2ubi.fsf@igel.home> (raw)
In-Reply-To: <20200930195512.724059-1-tuliom@linux.ibm.com> (Tulio Magno Quites Machado Filho via Libc-alpha's message of "Wed, 30 Sep 2020 16:55:12 -0300")
On Sep 30 2020, Tulio Magno Quites Machado Filho via Libc-alpha wrote:
> diff --git a/sysdeps/powerpc/mod-tlsopt-powerpc.c b/sysdeps/powerpc/mod-tlsopt-powerpc.c
> index ee0db12a73..5856dab60b 100644
> --- a/sysdeps/powerpc/mod-tlsopt-powerpc.c
> +++ b/sysdeps/powerpc/mod-tlsopt-powerpc.c
> @@ -24,7 +24,14 @@ tls_get_addr_opt_test (void)
> tls_index *tls_arg;
> #ifdef __powerpc64__
> register unsigned long thread_pointer __asm__ ("r13");
> + /* PC-relative addressing is available when compiling with -mpcrel.
> + The first releases of GCC 10 do support -mpcrel, but do not export
> + __PCREL__. */
> +# if defined(__PCREL__) || __GNUC__ <= 10 && defined(_ARCH_PWR10)
Space after defined, and remove the parens.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-10-01 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 19:55 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 [this message]
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
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=87r1qi2ubi.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=amodra@gmail.com \
--cc=libc-alpha@sourceware.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).