public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Juchan Kim <juckim@blackberry.com>
To: "fweimer@redhat.com" <fweimer@redhat.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [Question] ifunc odering in ELF
Date: Tue, 17 Sep 2019 13:19:00 -0000	[thread overview]
Message-ID: <1568726364.28076.91.camel@blackberry.com> (raw)
In-Reply-To: <87pnjzy75u.fsf@oldenburg2.str.redhat.com>

Hi Florian,

OK. That's what I also expected. 
Thanks for the reply.

Cheers,
Juchan

On Mon, 2019-09-16 at 22:43 -0400, Florian Weimer wrote:
> * Juchan Kim:
> 
> > 
> > We have two ifuncs foo1 and foo2 in our library
> > 
> > foo1 has foo1_resolver() 
> > foo2 has foo2_resolver()
> > 
> > 
> > foo1_resolver() {
> > 	...
> > }
> > 
> > foo2_resolver() {
> > 	foo1()
> > 	...
> > }
> IFUNC resolvers must not depend on run-time relocations.  If you
> follow
> that rule, this cannot happen.
> 
> binutils ld sorts IFUNC relocations last, which helps, but to cover
> more
> cases (but not all of them), run-time reordering of relocations is
> needed.  We have some patches for that, but my impression is that the
> glibc project does not want them.  Instead, we're probably going to
> remove all IFUNC resolvers with relocation dependencies from glibc,
> and
> tell others to do so as well.
> 
> Thanks,
> Florian

  reply	other threads:[~2019-09-17 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 19:03 Juchan Kim
2019-09-12 19:18 ` Andrew Pinski
2019-09-17  2:43 ` Florian Weimer
2019-09-17 13:19   ` Juchan Kim [this message]
2019-09-17 13:25   ` Adhemerval Zanella
2019-09-20 15:51     ` Florian Weimer
2019-09-20 16:00       ` Szabolcs Nagy
2019-10-16 12:55         ` Florian Weimer

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=1568726364.28076.91.camel@blackberry.com \
    --to=juckim@blackberry.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).