| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | improve pthread_exit synchronization with functions targeting tid•••if the last thread exited via pthread_exit, the logic that marked it
dead did not account for the possibility of it targeting itself via
atexit handlers. for example, an atexit handler calling
pthread_kill(pthread_self(), SIGKILL) would return success
(previously, ESRCH) rather than causing termination via the signal.
move the release of killlock after the determination is made whether
the exiting thread is the last thread. in the case where it's not,
move the release all the way to the end of the function. this way we
can clear the tid rather than spending storage on a dedicated
dead-flag. clearing the tid is also preferable in that it hardens
against inadvertent use of the value after the thread has terminated
but before it is joined.
| Rich Felker | 2018-05-05 | 1 | -1/+1 |
| * | consistently use the LOCK an UNLOCK macros•••In some places there has been a direct usage of the functions. Use the
macros consistently everywhere, such that it might be easier later on to
capture the fast path directly inside the macro and only have the call
overhead on the slow path.
| Jens Gustedt | 2018-01-09 | 1 | -2/+2 |
| * | fix failure of pthread_setschedparam to pass correct param to kernel•••the address of the pointer, rather than the pointer, was being passed.
this was probably a copy-and-paste error from corresponding get code.
| Rich Felker | 2013-06-26 | 1 | -1/+1 |
| * | add support for thread scheduling (POSIX TPS option)•••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.
| Rich Felker | 2012-11-11 | 1 | -0/+10 |
