From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Henderson <rth@twiddle.net>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org,
"Ryan S. Arnold" <rsa@linux.vnet.ibm.com>,
David Miller <davem@davemloft.net>
Subject: Re: [ppc] Include hwcap as ifunc argument
Date: Thu, 24 May 2012 14:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1205241445100.13635@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4FBE4843.5030107@twiddle.net>
On Thu, 24 May 2012, Richard Henderson wrote:
> On 05/21/2012 09:58 AM, Richard Henderson wrote:
> > Aside from the x86 port, there are only two targets that have ifunc
> > support in glibc mainline: ppc and arm. It would be awesomely handy
> > if we switch these targets to mirror the sparc lead in passing along
> > the dl_hwcap contents as an argument to the resolver, *and* to do it
> > in the same release as adding getauxval. There are some clever things
> > we can do at static link time if we know that getauxval corresponds to
> > the availability of the ifunc argument.
> >
> > Dave, dunno if you wanna change the signature of the arg from int to
> > unsigned long for 64-bit? It just seemed prudent to do that here...
> >
> > I'll present a similar patch for arm shortly...
>
> Like so. Tested on armv7. And a ping for the ppc patch?
This ARM patch is OK with the usual copyright dates update.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-05-24 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FBA744A.6000702@twiddle.net>
2012-05-24 14:40 ` Richard Henderson
2012-05-24 14:45 ` Joseph S. Myers [this message]
2012-05-24 19:47 ` David Miller
2012-05-25 17:44 ` Richard Henderson
2012-06-04 21:22 ` Ryan S. Arnold
2012-06-04 22:14 ` Richard Henderson
2012-06-08 14:01 ` Andreas Krebbel
2012-06-08 14:49 ` Richard Henderson
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=Pine.LNX.4.64.1205241445100.13635@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=davem@davemloft.net \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=rsa@linux.vnet.ibm.com \
--cc=rth@twiddle.net \
/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).