mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: musl for ARM
Date: Tue, 2 Oct 2012 09:48:43 -0400	[thread overview]
Message-ID: <20121002134843.GV254@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPW=hRTK-vP9Nmk938PQvZzOUcFF0GFvOLqevMBwYxR4a=-+eA@mail.gmail.com>

On Tue, Oct 02, 2012 at 03:27:28PM +0800, Brian Wang wrote:
> Hello all,
> 
> I am currently thinking of switching to musl from glibc for my target
> after some readings on musl.
> I would like some advice from musl experts:
>   * Does it support gettext stuff?
>   * Does it _boost_ the performance on a 400MHz arm926 device?  Or it
> is just smaller?
>     By _boost_, I mean if the user can actually feel the improvement
> in performance.

In general, if an application's perceived performance varies heavily
depending on libc, the application is probably doing something wrong
or at least naive. I can think of some exceptions of course, but this
advice is just to say that libc is probably not a place to look for
significantly improving overall performance. If there are libc
bottlenecks, you could probably get a lot more performance out of
changing the application.

The main exceptions I can think of are places where libc has the wrong
big-O: for example, O(n²) qsort or O(nm) strstr, or backtracking
regex implementations, can make completely-sane programs run extremely
slow on a bad libc. Note that musl and glibc are almost always
equivalent in this area; uclibc and dietlibc and perhaps others have
some problems here.

One area you can get vastly better performance with musl is
application startup overhead. Especially with static linking, but even
with dynamic linking if your only .so is libc, the startup time is
2-5x faster than glibc, which really makes a difference to the runtime
of shell scripts (like configure) that invoke tons of external
programs.

> I did try the musl cross project and successfully built a musl-based
> arm linux toolchain.
> My kernel (2.6.24) was built successfully (not tried it on my device yet).
> However, when building busybox, there are some header files clashes,
> resulting in conflicting types.
> An example of it:
> ---------------------
> In file included from
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/linux/kd.h:3:0,
>                  from console-tools/kbd_mode.c:23:
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/linux/types.h:12:26:
> error: conflicting types for ‘fd_set’
> In file included from
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/sys/time.h:9:0,
>                  from include/libbb.h:45,
>                  from console-tools/kbd_mode.c:22:
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/sys/select.h:25:3:
> note: previous declaration of ‘fd_set’ was here
> ---------------------

It looks like these kernel headers are not sanitized for compatibility
with userspace..?

Rich


  parent reply	other threads:[~2012-10-02 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02  7:27 Brian Wang
2012-10-02 10:55 ` John Spencer
2012-10-02 16:05   ` Brian Wang
2012-10-02 13:48 ` Rich Felker [this message]
2012-10-02 16:18   ` Brian Wang
2012-10-02 17:45     ` Rich Felker
2012-10-02 16:39   ` Szabolcs Nagy
2012-10-02 17:46     ` Rich Felker

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=20121002134843.GV254@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).