From: Szabolcs Nagy <nsz@port70.net>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: musl firsts
Date: Thu, 24 Jul 2014 08:54:46 +0200 [thread overview]
Message-ID: <20140724065446.GN9928@port70.net> (raw)
In-Reply-To: <20140724000405.GA21561@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2014-07-23 20:04:05 -0400]:
> Random fun list I thought we could compile for promotional material
> (maybe use in future talks, website, etc.): features that musl had
> before any of the competitors. A few to start it off, in roughly
> chronological order:
>
> - TCB shadow passwords
> - Bcrypt in libc crypt
> - Safe and working thread cancellation
> - Correctly-rounded sqrt on 32-bit x86
> - AS-safe and fail-safe dynamic TLS
> - VSDO on 32-bit x86
> - Link-local address scope ids in hosts file
> - Using link-local addresses for nameservers in resolv.conf
> - OpenRISC 1000 (or1k) port in upstream
>
> I can think of a lot of smaller things too that are more like bugfixes
> and probably not worth mentioning, like AS-safety of various functions
> that are required to be AS-safe but that are broken in most libcs.
> Additions to the list are welcome.
- correct types in ipc structs on linux
- strtod that does not malloc/abort
- <10k worst-case stack usage guarantee (except execl* where
stack usage is caller dependent: args are copied to the stack)
- correct utf8 in libc?
- jn(INT_MIN, 12.34) does not invoke ub!
next prev parent reply other threads:[~2014-07-24 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 0:04 Rich Felker
2014-07-24 6:54 ` Szabolcs Nagy [this message]
2014-07-24 16:03 ` u-igbb
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=20140724065446.GN9928@port70.net \
--to=nsz@port70.net \
--cc=dalias@libc.org \
--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).