From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
libc-alpha@sourceware.org, mark.hatle@kernel.crashing.org,
"Robert Berger@yocto.user" <robert.berger.yocto.user@gmail.com>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>
Subject: Re: Yocto prelink status
Date: Fri, 21 Jan 2022 16:23:20 +0000 [thread overview]
Message-ID: <20220121162320.GI3294453@arm.com> (raw)
In-Reply-To: <20220121105844.GC1021@pbcl.net>
The 01/21/2022 11:58, Phil Blundell via Libc-alpha wrote:
> On Thu, Jan 20, 2022 at 10:51:31PM +0000, Richard Purdie via Libc-alpha wrote:
> > Bottom line was that there was some very slight speed ups and the memory usage
> > was possibly worse with prelink but it was marginal. With other more specific
> > test cases and libraries with complex/large symbol tables, the results may be
> > different.
>
> The benefits of prelink tend to be more noticeable with large C++ DSOs because
> they have a lot of RELATIVE relocs which can be eliminated entirely during
> prelinking. JUMP_SLOTs are resolved lazily in any case so the benefit of
> doing that in advance is smaller, and most modern programs don't have a lot
> of GLOB_DATs at all.
glibc plans to support the DT_RELR format for more compact representation
of relative relocs. see bug 27924.
(i believe this is used on android/chromeos for the reason you cited.)
next prev parent reply other threads:[~2022-01-21 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 22:51 Richard Purdie
2022-01-21 10:58 ` Phil Blundell
2022-01-21 16:23 ` Szabolcs Nagy [this message]
2022-01-21 17:09 ` Phil Blundell
2022-02-03 15:26 ` Richard Purdie
2022-02-03 15:43 ` Mark Hatle
-- strict thread matches above, loose matches on Subject: below --
2022-01-19 19:52 Adhemerval Zanella
2022-01-19 20:28 ` Joseph Myers
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=20220121162320.GI3294453@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=mark.hatle@kernel.crashing.org \
--cc=nicolas.dechesne@linaro.org \
--cc=pb@pbcl.net \
--cc=richard.purdie@linuxfoundation.org \
--cc=robert.berger.yocto.user@gmail.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).