From 65dd7e9ce36ca8485a68ed41ac731188b6473dd2 Mon Sep 17 00:00:00 2001 From: Mike Crowe Date: Mon, 24 Jun 2019 19:51:03 +0000 Subject: [PATCH] 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 --- ChangeLog | 4 ++++ NEWS | 9 +++++++++ 2 files changed, 13 insertions(+) diff --git a/ChangeLog b/ChangeLog index 7f75559..9eb8263 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2019-07-12 Mike Crowe + * 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. diff --git a/NEWS b/NEWS index 11099f7..6d731b1 100644 --- a/NEWS +++ b/NEWS @@ -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 -- 2.7.4