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>

diff --git a/ChangeLog b/ChangeLog
index 7f7555984bde162953e7e86e736bd5c21786c0ce..9eb8263250c6d6285a0899548f8e43596a7accb5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -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.

diff --git a/NEWS b/NEWS
index 11099f7248eabbfabb5c8ce9856930a65848e170..6d731b156d114ba8b1f846127f4b76f07282f0c8 100644 (file)
--- 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