Find a file
Rich Felker 729d6368bd redo cond vars again, use sequence numbers
testing revealed that the old implementation, while correct, was
giving way too many spurious wakeups due to races changing the value
of the condition futex. in a test program with 5 threads receiving
broadcast signals, the number of returns from pthread_cond_wait was
roughly 3 times what it should have been (2 spurious wakeups for every
legitimate wakeup). moreover, the magnitude of this effect seems to
grow with the number of threads.

the old implementation may also have had some nasty race conditions
with reuse of the cond var with a new mutex.

the new implementation is based on incrementing a sequence number with
each signal event. this sequence number has nothing to do with the
number of threads intended to be woken; it's only used to provide a
value for the futex wait to avoid deadlock. in theory there is a
danger of race conditions due to the value wrapping around after 2^32
signals. it would be nice to eliminate that, if there's a way.

testing showed no spurious wakeups (though they are of course
possible) with the new implementation, as well as slightly improved
performance.
2011-09-26 00:25:13 -04:00
arch "optimize" arm __pthread_self 2011-09-22 22:56:06 -04:00
crt initial commit of the arm port 2011-09-18 16:44:54 -04:00
dist cleanup shared library build system to be more $HOME-local-install friendly 2011-06-27 21:38:11 -04:00
include FD_ISSET must return an int. this is the easiest way. 2011-09-23 22:24:33 -04:00
lib new solution for empty lib dir (old one had some problems) 2011-02-17 17:12:52 -05:00
src redo cond vars again, use sequence numbers 2011-09-26 00:25:13 -04:00
tools new gcc wrapper now supports pre-4.4 gcc versions and is more robust 2011-09-21 19:40:55 -04:00
COPYING initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00
COPYRIGHT XSI search.h API implementation by Szabolcs Nagy 2011-06-25 18:18:57 -04:00
INSTALL new installation guide with alternate and primary libc setups 2011-09-21 19:39:40 -04:00
Makefile fix a few bugs from last dynamic linking build system commit 2011-06-28 08:27:38 -04:00
README 0.8.0 release 2011-09-13 13:41:40 -04:00
WHATSNEW release notes for 0.8.3 2011-09-21 20:24:12 -04:00

musl libc - a new standard library to power a new generation of
Linux-based devices. musl is lightweight, fast, simple, free, and
strives to be correct in the sense of standards-conformance and
safety.

musl is an alternative to glibc, eglibc, uClibc, dietlibc, and klibc.
For reasons why one might prefer musl, please see the FAQ and libc
comparison chart on the project website,

    http://www.etalabs.net/musl/

For installation instructions, see the INSTALL file.

Please refer to the COPYRIGHT file for details on the copyright status
of code included in musl, and the COPYING file for the license (LGPL)
under which the library as a whole is distributed.



Greetings!

As of the 0.8.0 release, musl is in _beta_ status. While some
interfaces remain incomplete or yet to be implemented, the ABI is
intended to be stable at this point, and serious efforts have been
made, using three separate test frameworks, to verify the correctness
of the implementation. Many major system-level and user-level programs
are known to work with musl, either out-of-the-box or with minor
patches to address portability errors; the main remaining applications
which definitely will not work are those which require C++ support,
which will be addressed during the 0.8 or 0.9 development series.

Included with this package is a gcc wrapper script (musl-gcc) which
allows you to build musl-linked programs using an existing gcc 4.x
toolchain on the host. There are also now at least two mini
distributions (in the form of build scripts) which provide a
self-hosting musl-based toolchain and system root: Sabotage Linux and
Bootstrap Linux. These are much better options than the wrapper script
if you wish to use dynamic linking or build packages with many library
dependencies.

The musl project is actively seeking contributors, mostly in the areas
of porting, testing, and application compatibility improvement. For
bug reports, support requests, or to get involved in development,
please visit #musl on Freenode IRC or subscribe to the musl mailing
list by sending a blank email to musl-subscribe AT lists DOT openwall
DOT com.

Thank you for using musl.

Cheers,

Rich Felker / dalias