Update NEWS for new _clockwait and _clocklock functions

* NEWS: Mention recently-added pthread_cond_clockwait,
	pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock and
	sem_clockwait functions.

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
This commit is contained in:
Mike Crowe 2019-06-24 19:51:03 +00:00 committed by Adhemerval Zanella
parent 9d20e22e46
commit 65dd7e9ce3
2 changed files with 13 additions and 0 deletions

View File

@ -1,5 +1,9 @@
2019-07-12 Mike Crowe <mac@mcrowe.com>
* NEWS: Mention recently-added pthread_cond_clockwait,
pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock and
sem_clockwait functions.
nptl: Add POSIX-proposed pthread_mutex_clocklock function that
works like pthread_mutex_timedlock but takes a clockid parameter to
measure the abstime parameter against.

9
NEWS
View File

@ -40,6 +40,15 @@ Major new features:
FUNCTION-NAME, version SYMBOL-VERSION not defined in file DSO-NAME with
link time reference, is gone.
* Add new POSIX-proposed pthread_cond_clockwait, pthread_mutex_clocklock,
pthread_rwlock_clockrdlock, pthread_rwlock_clockwrlock and sem_clockwait
functions. These behave similarly to their "timed" equivalents, but also
accept a clockid_t parameter to determine which clock their timeout should
be measured against. All functions allow waiting against CLOCK_MONOTONIC
and CLOCK_REALTIME. The decision of which clock to be used is made at the
time of the wait (unlike with pthread_condattr_setclock, which requires
the clock choice at initialization time).
Deprecated and removed features, and other changes affecting compatibility:
* The copy_file_range function fails with ENOSYS if the kernel does not