Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: arnez@linux.vnet.ibm.com (Andreas Arnez)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Pass HWCAP to ifunc resolver
Date: Tue, 06 Sep 2016 15:42:00 -0000	[thread overview]
Message-ID: <20160906154240.CCF5B100057@oc8523832656.ibm.com> (raw)
In-Reply-To: <m3inuhma3e.fsf@oc1027705133.ibm.com> from "Andreas Arnez" at Aug 31, 2016 01:49:57 PM

Andreas Arnez wrote:

> On various GNU Elf architectures, including AArch64, ARM, s390/s390x,
> ppc32/64, and sparc32/64, the dynamic loader passes HWCAP as a parameter
> to each ifunc resolver.  Currently there is an open glibc Bugzilla that
> requests this to be generalized to all architectures:
> 
>   https://sourceware.org/bugzilla/show_bug.cgi?id=19766
> 
> And various ifunc resolvers already rely on receiving HWCAP.  Currently
> GDB always calls an ifunc resolver without any arguments; thus the
> resolver may receive garbage, and based on that, the resolver may decide
> to return a function that is not suited for the given platform.
> 
> This patch always passes HWCAP to ifunc resolvers, even on systems where
> the dynamic loader currently behaves otherwise.  The rationale is
> that (1) the dynamic loader may get adjusted on those systems as well in
> the future; (2) passing an unused argument should not cause a problem
> with existing resolvers; and (3) the logic is much simpler without such
> a distinction.

This makes sense to me.  If necessary, we can always still add platform-
specific call sequences later.

> gdb/ChangeLog:
> 
> 	* elfread.c (auxv.h): New include.
> 	(elf_gnu_ifunc_resolve_addr): Pass HWCAP to ifunc resolver.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/gnu-ifunc-lib.c (resolver_hwcap): New external
> 	variable declaration.
> 	(gnu_ifunc): Add parameter hwcap.  Store it in resolver_hwcap.
> 	* gdb.base/gnu-ifunc.c (resolver_hwcap): New global variable.
> 	* gdb.base/gnu-ifunc.exp: Add test to verify that the resolver
> 	received HWCAP as its argument.

This is OK.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  parent reply	other threads:[~2016-09-06 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 11:50 Andreas Arnez
2016-09-01  5:03 ` Andrew Pinski
2016-09-01  9:19   ` Andreas Arnez
2016-09-06 15:42 ` Ulrich Weigand [this message]
2016-09-09 18:02   ` Andreas Arnez

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=20160906154240.CCF5B100057@oc8523832656.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@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