public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Tulio Magno Quites Machado Filho via Libc-alpha
	<libc-alpha@sourceware.org>,
	 Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Subject: Re: [PATCH] powerpc64: Implement TLS using PC-relative addressing
Date: Thu, 1 Oct 2020 20:45:16 +0930	[thread overview]
Message-ID: <20201001111516.GJ15011@bubble.grove.modra.org> (raw)
In-Reply-To: <87y2kqjpp4.fsf@oldenburg2.str.redhat.com>

On Thu, Oct 01, 2020 at 10:49:43AM +0200, Florian Weimer wrote:
> * Tulio Magno Quites Machado Filho via Libc-alpha:
> 
> > 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)
> > +  asm ("pla %0,foo@got@tlsgd@pcrel" : "=r" (tls_arg));
> > +# else
> >    asm ("addi %0,2,foo@got@tlsgd" : "=r" (tls_arg));
> > +# endif
> 
> Should this check for binutils support for @pcrel?  Or won't GCC enable
> _ARCH_PWR10 in this case?

Right, gcc doesn't support power10 without the requisite binutils
support.  In any case, this file is only used when running the
testsuite so it hardly seems worth the bother of configure checks.
The patch looks good to me.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2020-10-01 11:15 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 [this message]
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

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=20201001111516.GJ15011@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=fweimer@redhat.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).