musl/src/thread/pthread_attr_getschedparam.c, branch 8fca0ea4e9d09b0ada66b135533a74a643de77ef musl - an implementation of the standard library for Linux-based systems debloat src/thread tree but putting lots of junk in one file 2012-11-11T21:08:38+00:00 Rich Felker dalias@aerifal.cx 2012-11-11T21:08:38+00:00 c4a35f8c2a4b1a7e62a4b9e5b2748fb4fbcace79 POSIX includes mostly-useless attribute-get functions for each attribute-set function, presumably out of some object-oriented dogmatism. the get functions are not useful with the simple idiomatic usage of attributes. there are of course possible valid uses of them (like writing wrappers for pthread init functions that perform special actions on the presence of certain attributes), but considering how tiny these functions are anyway, little is lost by putting them all in one file, and some build-time cost and archive-file-size benefits are achieved. 
POSIX includes mostly-useless attribute-get functions for each
attribute-set function, presumably out of some object-oriented
dogmatism. the get functions are not useful with the simple idiomatic
usage of attributes. there are of course possible valid uses of them
(like writing wrappers for pthread init functions that perform special
actions on the presence of certain attributes), but considering how
tiny these functions are anyway, little is lost by putting them all in
one file, and some build-time cost and archive-file-size benefits are
achieved.
add support for thread scheduling (POSIX TPS option) 2012-11-11T20:38:04+00:00 Rich Felker dalias@aerifal.cx 2012-11-11T20:38:04+00:00 1e21e78bf7a5c24c217446d8760be7b7188711c2 linux's sched_* syscalls actually implement the TPS (thread scheduling) functionality, not the PS (process scheduling) functionality which the sched_* functions are supposed to have. omitting support for the PS option (and having the sched_* interfaces fail with ENOSYS rather than omitting them, since some broken software assumes they exist) seems to be the only conforming way to do this on linux. 
linux's sched_* syscalls actually implement the TPS (thread
scheduling) functionality, not the PS (process scheduling)
functionality which the sched_* functions are supposed to have.
omitting support for the PS option (and having the sched_* interfaces
fail with ENOSYS rather than omitting them, since some broken software
assumes they exist) seems to be the only conforming way to do this on
linux.
use restrict everywhere it's required by c99 and/or posix 2008 2012-09-07T02:44:55+00:00 Rich Felker dalias@aerifal.cx 2012-09-07T02:44:55+00:00 400c5e5c8307a2ebe44ef1f203f5a15669f20347 to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict. 
to deal with the fact that the public headers may be used with pre-c99
compilers, __restrict is used in place of restrict, and defined
appropriately for any supported compiler. we also avoid the form
[restrict] since older versions of gcc rejected it due to a bug in the
original c99 standard, and instead use the form *restrict.
implement dummy pthread_attr_[gs]etschedparam functions 2011-03-11T14:51:54+00:00 Rich Felker dalias@aerifal.cx 2011-03-11T14:51:54+00:00 243b542382990d8c2d0e5469ae68dfd622551a3e for some reason these functions are not shaded by the PS/TPS option in POSIX, so presumably they are mandatory, even though the functionality they offer is optional. for now, provide them in case any programs depend on their existence, but disallow any priority except the default. 
for some reason these functions are not shaded by the PS/TPS option in
POSIX, so presumably they are mandatory, even though the functionality
they offer is optional. for now, provide them in case any programs
depend on their existence, but disallow any priority except the
default.