consistently use the LOCK an UNLOCK macros
authorJens Gustedt <Jens.Gustedt@inria.fr>
Wed, 3 Jan 2018 13:17:12 +0000 (14:17 +0100)
committerRich Felker <dalias@aerifal.cx>
Tue, 9 Jan 2018 18:14:49 +0000 (13:14 -0500)
commitc4bc0b1a64e1ef1e105df84401805a16e8dbe82a
treed4aa94638bb44b688b1c0acd8cfa02259c15bd4f
parent47d0bcd4762f223364e5b58d5a381aaa0cbd7c38
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.
src/thread/pthread_create.c
src/thread/pthread_detach.c
src/thread/pthread_getschedparam.c
src/thread/pthread_kill.c
src/thread/pthread_setschedparam.c
src/thread/pthread_setschedprio.c