[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ab50ffb-4d48-421d-9b0a-f4ed47bdfa45@maxsi.org>
Date: Mon, 29 Sep 2025 16:34:22 +0200
From: Jonas 'Sortie' Termansen <sortie@...si.org>
To: musl@...ts.openwall.com
Subject: Running os-test on musl's POSIX headers
Hi musl,
You might be interested in the os-test project I've been building
lately. The new include test suite checks whether the standard library
headers declare everything that POSIX.1-2024 requires, sliced by each
option group:
https://sortix.org/os-test/include/ for the raw data
https://sortix.org/blog/os-testing-posix-headers/ for a write-up about
the results
I'm pleased to say that musl is actually the top scoring libc in terms
of POSIX completeness at 96%, slightly ahead of glibc and Illumos!
musl is also the only libc that doesn't have any incompatible function
type signatures.
There are a few feature macros that should adjusted in the headers for
POSIX,1.-2024. The pthread_mutexattr_[gs]etprioceiling functions are
declared but cannot be linked with. Otherwise the interesting results
are basically just missing declarations, generally for new POSIX.1-2024
stuff. You can also compare with the glibc results or those of other
systems if you're curious. If you're interested using this project to
improve musl interoperability, then please dive into the data and have
a look :)
This work has been inspired by the methodology of libc-test. os-test
has been funded and next up I'll be working on namespace pollution
and seeing if functions actually work if invoked.
Jonas
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.
