From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Draft: musl promo materials
Date: Fri, 13 Jul 2012 21:16:09 +0200 [thread overview]
Message-ID: <20120713191609.GC14463@port70.net> (raw)
In-Reply-To: <20120713181254.GA31206@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-07-13 14:12:54 -0400]:
> Consistent quality and implementation behavior from tiny embedded
> systems to full servers.
>
> Minimal machine-specific code, meaning less chance of breakage on
> minority architectures and better success with "write once run
> everywhere" development.
>
> Realtime-quality robustness. No unnecessary dynamic allocation. No
> unrecoverable late failures. No lazy binding or lazy allocation.
>
> MIT license.
>
> Full math library with a focus on correctness. Exact and
> correctly-rounded conversion between binary floating point and decimal
> strings.
>
> Reentrancy, thread-safety, and async-signal safety well beyond the
> requirements of POSIX. Even snprintf and dprintf are fully reentrant
> and async-signal-safe.
>
> Highly resource-efficient POSIX threads implementation, making
> multi-threaded application design viable even for memory-constrained
> systems.
i'd somehow add that both static and dynamic linking is supported
properly and without bloat as musl is better at it than glibc
i like musl's clean code, clean header files (no gcc specific mess)
and simple build system (even for cross compilation)
again something that glibc is lacking
and there could be a hint that things like security, worst cases
(stack usage, algorithm complexity) and conformance are taken seriously
next prev parent reply other threads:[~2012-07-13 19:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:12 Rich Felker
2012-07-13 19:16 ` Szabolcs Nagy [this message]
2012-07-14 6:40 ` orc
2012-07-13 23:30 ` Rich Felker
2012-07-14 19:05 ` Isaac Dunham
2012-07-15 0:01 ` Rich Felker
2012-07-14 21:45 ` Charlie Kester
2012-07-14 23:06 ` Isaac Dunham
2012-07-14 23:30 ` Gregor Richards
2012-07-15 0:49 ` Isaac Dunham
2012-07-15 0:58 ` Gregor Richards
2012-07-15 0:03 ` 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=20120713191609.GC14463@port70.net \
--to=nsz@port70.net \
--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).