From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] build: add support for as-needed linking
Date: Wed, 21 Sep 2016 01:17:23 +0200 [thread overview]
Message-ID: <87zin2yxdo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <578C249C.9040700@free-electrons.com> (Gustavo Zacarias's message of "Sun, 17 Jul 2016 21:36:44 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo.zacarias@free-electrons.com> writes:
Hi,
>> So, what would that bring to us?
> Yes, that's what lazy binding does... but it's still based on
> DT_NEEDED entries, hence instead of scanning 10 libraries at required
> time in my example it will only need to scan 8 to resolve required
> symbols.
> For more complex applications that use many nested libraries the
> savings can be bigger.
> Example diff between non-as-needed gst-launch-1.0 and as-needed version:
> libgstreamer-1.0.so.0
> libgobject-2.0.so.0
> -libgmodule-2.0.so.0
> libglib-2.0.so.0
> -librt.so.1
> -libdl.so.2
> libgcc_s.so.1
> libpthread.so.0
> libc.so.6
So what is E.G. the time differences when running
time gst-launch-1.0 fakesrc num-buffers=1 ! fakesink
on a "normal" machine with/without these patches?
(Notice that gstreamer searches plugins and creates cache file first
time it is run).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-09-20 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 15:05 [Buildroot] [PATCH 1/2] build: add support for as-needed linking gustavo.zacarias at free-electrons.com
2016-07-17 15:05 ` [Buildroot] [PATCH 2/2] docs/manual: document PKG_AS_NEEDED gustavo.zacarias at free-electrons.com
2016-07-17 21:01 ` [Buildroot] [PATCH 1/2] build: add support for as-needed linking Yann E. MORIN
2016-07-18 0:36 ` Gustavo Zacarias
2016-09-20 23:17 ` Peter Korsgaard [this message]
2016-09-20 18:07 ` Thomas Petazzoni
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=87zin2yxdo.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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