dalias

15 ms·

31.
by dalias 13y ago
A special treat to go with the release, that's not linked on the website yet: in-browser demo setup using jslinux: http://www.musl-libc.org/jslinux/
32.
by dalias 13y ago
Yes. If anyone has suggestions for other comparison points I should add that would be more balanced, I can try to add them (but some things require non-trivial work to measure so it might take me a while to get around to it). Note that the
33.
by dalias 13y ago
The size isn't really an issue for most desktop or server oriented distributions. Perhaps bigger issues for distros are: - Symbol versioning: If you have a newer glibc installed when you build your packages, they'll refuse to run
34.
by dalias 13y ago
The musl figures may be somewhat outdated since musl is developing rather quickly. With regards to the others, the main thing that's outdated is the size of glibc. It's considerably larger now. :-)
35.
by dalias 13y ago
I don't think there's much value in adding an Annex K comparison anywhere since none of the compared libcs have Annex K functions; comparison items are only meaningful where they differ. Even if some libcs did have it, though, I&#
36.
by dalias 13y ago
Could you clarify what you mean by "doesn't support aarch32"? I can't find any clear definition of what aarch32 means, but my impression is that it's just a new name for what we call "arm", but possibly im
37.
by dalias 13y ago
I don't think Bionic is really suitable for this. It's unlikely to even work for building apps that weren't specifically designed for Bionic, since it's rather deficient in its support for many of the standard functions,
38.
by dalias 13y ago
Folks on #musl found 2 integer overflow bugs in the UTF-8 handling code within seconds of checking out the source to read it. It's not clear to me where the code is called from and what inputs reach it, but that kind of bug does not in
39.
by dalias 13y ago
Functionality is not being moved out of the kernel and into userspace. It's being moved out of legacy freedesktop.org components (hald, ConsoleKit, PolicyKit, etc.) and into PID 1. Where should it be moved to? /dev/null.
40.
by dalias 13y ago
Almost all daemons have a command line or config file option to skip "daemonizing" so that the parent can watch the PID correctly. For the few that don't, you can fix them, hack them (e.g. LD_PRELOAD wrappers to shutdown thei
41.
by dalias 14y ago
The lore is that the the name POSIX, not the idea for POSIX, came from RMS and was a form of disguised spite for the process (i.e. that he intended it to be read as Piece Of Shit *IX, or similar). I'm not sure whether there's any evidence
42.
by dalias 14y ago
Machines with a word size that's not a multiple of 8 cannot support POSIX at all. POSIX requires CHAR_BIT==8, and to support the POSIX and C11 memory model for threads, bytes must be individually addressible without a read-modify-write cycl
43.
by dalias 14y ago
The glibc default thread stack size is unacceptable/broken for a couple reasons. It eats memory like crazy (usually 8-10 megs per thread), and by memory I mean commit charge, which is a highly finite resource on a well-configured system wit
44.
by dalias 14y ago
Addressing afhof's comments... 1 & 2. I don't see any reason to believe there will ever be a new machine with non-power-of-two word size, and I'm doubtful that there are even any historical post-standardization C implementations like th