From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: nd <nd@arm.com>, "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [Question] ifunc odering in ELF
Date: Fri, 20 Sep 2019 16:00:39 +0000 [thread overview]
Message-ID: <0a862d00-8b76-4015-3750-f05636544611@arm.com> (raw)
In-Reply-To: <87v9tnezju.fsf@oldenburg2.str.redhat.com>
On 20/09/2019 16:51, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>> That's was not my impression, I this we should to go this way iff we can't
>> really make IFUNC reordering work on loader. From your initial work on
>> the two-phase IFUNC relocation, which prevents us to move forward?
>
> No one said, “yes, we do need this feature in the loader”.
>
> (Keep in mind that it does not solve all ordering problems, the example
> in this thread would still break.)
if most "reasonable" ordering issues can be fixed, then
i think the ordering should be fixed.
but i seem to remember that for it to work it's not enough
to consider the relocations of a single module, but other
modules have to be considered (in case of copy relocated
function pointers? or extern ifunc code in not yet relocated
modules?).
if relocations have to be processed twice across multiple
modules then i think the complexity is too much (we need to
allocate space for the list of relocs that need reprocessing
etc).
next prev parent reply other threads:[~2019-09-20 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 19:03 [Question] ifunc odering in ELF Juchan Kim
2019-09-12 19:17 ` Andrew Pinski
2019-09-17 2:43 ` Florian Weimer
2019-09-17 13:19 ` Juchan Kim
2019-09-17 13:24 ` Adhemerval Zanella
2019-09-20 15:51 ` Florian Weimer
2019-09-20 16:00 ` Szabolcs Nagy [this message]
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a862d00-8b76-4015-3750-f05636544611@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).