Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140724065446.GN9928@port70.net>
Date: Thu, 24 Jul 2014 08:54:46 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: musl firsts

* Rich Felker <dalias@...c.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!

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.