From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Current status vs 1.0 wishlist, 0.9
Date: Wed, 2 May 2012 17:01:34 -0400 [thread overview]
Message-ID: <20120502210134.GT14673@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120502131740.3bc8dba5.idunham@lavabit.com>
On Wed, May 02, 2012 at 01:17:40PM -0700, Isaac Dunham wrote:
> Here's what he said:
> [...]
Everybody's favorite topic again! :-)
Hope to get back to everyone on license topic soon.
> I know at least one developer (working on one of the Puppy Linux
> variants) who's waiting for this, though I can't say about
> "widespread" use. Another of the Puppy developers was fairly
> impressed with the size, though he hasn't switched from uclibc yet
> (for reasons not known to me).
> (I'm getting static binaries a couple kb larger than he gets with uclibc)
I would believe that it's possible to get smaller binaries with a
uClibc that's had lots of features turned off when the library was
built, meaning that those features are completely unavailable to
applications. On the other hand, I suspect musl will easily beat
uClibc in static linking size when uClibc is full-featured (UTF-8,
pthread, full malloc, stdio, hex floats in printf, ...) because musl
takes a lot more care not to have unnecessary cross-dependency between
.o files in the static lib. Still, some things are impossible to
optimize out with the linker - for example, printf always pulls in a
minimum amount of UTF-8 conversion code for %ls and %c.
Rich
prev parent reply other threads:[~2012-05-02 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 0:31 Rich Felker
2012-04-24 6:47 ` Georgi Chorbadzhiyski
2012-05-02 9:49 ` Georgi Chorbadzhiyski
2012-05-02 9:54 ` Georgi Chorbadzhiyski
2012-05-02 11:08 ` Solar Designer
2012-05-02 11:51 ` Georgi Chorbadzhiyski
2012-05-02 12:04 ` Solar Designer
2012-05-02 20:17 ` Isaac Dunham
2012-05-02 21:01 ` Rich Felker [this message]
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=20120502210134.GT14673@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).