mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alex Dowad <alexinbeijing@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Question re: dynamic linking in musl
Date: Wed, 27 May 2015 15:15:03 +0200	[thread overview]
Message-ID: <5565C357.1070508@gmail.com> (raw)
In-Reply-To: <20150527160955.1bda26cf@vostro>



On 27/05/15 15:09, Timo Teras wrote:
> On Wed, 27 May 2015 16:01:50 +0300 (MSK)
> Alexander Monakov <amonakov@ispras.ru> wrote:
>
>> On Wed, 27 May 2015, Alex Dowad wrote:
>>>> Can you also provide exact figures?  For example your callgrind
>>>> logs?  Or just
>>>> 'time' statistics for executables that spend much time in the
>>>> dynamic linker.
>>> Callgrind data attached.
>> Oh.  The profile makes it evident that most of the libraries
>> lack .gnu.hash, and the lookup is almost always using SysV lookup.
>> With many dependencies SysV lookup is slower: in my testing with
>> Clang/LLVM I got something like 420 ms (compared to 240 ms unpatched
>> or 110 ms patched musl with .gnu.hash lookup).
>>
>> I'm not familiar with Alpine.  Hopefully someone else can chime in
>> whether .gnu.hash is deliberately disabled.
> We have not touched, so we are using the gcc default. Which apparently
> then is sysv only (bummer).
>
Yes, that callgrind profile was from a program installed from Alpine repos.

Use --hash-style=both in LD_FLAGS when building the APKs, and dynamic 
linking will become much faster!

Alex


  reply	other threads:[~2015-05-27 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 10:08 Alex Dowad
2015-05-27 10:40 ` Alexander Monakov
2015-05-27 11:18   ` Alex Dowad
2015-05-27 13:01     ` Alexander Monakov
2015-05-27 13:09       ` Timo Teras
2015-05-27 13:15         ` Alex Dowad [this message]
2015-05-27 13:23           ` Timo Teras
2015-05-27 14:06             ` Szabolcs Nagy
2015-05-27 14:06             ` Rich Felker
2015-05-28 14:03               ` Natanael Copa
2015-05-27 13:06     ` Szabolcs Nagy

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=5565C357.1070508@gmail.com \
    --to=alexinbeijing@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).