From 1ff1373b3302e9e095dc4fd4d371451c00190780 Mon Sep 17 00:00:00 2001 From: Mike Crowe Date: Mon, 24 Jun 2019 20:18:00 +0000 Subject: nptl: Remove futex_supports_exact_relative_timeouts The only implementation of futex_supports_exact_relative_timeouts always returns true. Let's remove it and all its callers. * nptl/pthread_cond_wait.c: (__pthread_cond_clockwait): Remove code that is only useful if futex_supports_exact_relative_timeouts () returns false. * nptl/pthread_condattr_setclock.c: (pthread_condattr_setclock): Likewise. * sysdeps/nptl/futex-internal.h: Remove comment about relative timeouts potentially being imprecise since it's no longer true. Remove declaration of futex_supports_exact_relative_timeouts. * sysdeps/unix/sysv/linux/futex-internal.h: Remove implementation of futex_supports_exact_relative_timeouts. Reviewed-by: Adhemerval Zanella --- nptl/pthread_condattr_setclock.c | 5 ----- 1 file changed, 5 deletions(-) (limited to 'nptl/pthread_condattr_setclock.c') diff --git a/nptl/pthread_condattr_setclock.c b/nptl/pthread_condattr_setclock.c index 641a041..ac91923 100644 --- a/nptl/pthread_condattr_setclock.c +++ b/nptl/pthread_condattr_setclock.c @@ -33,11 +33,6 @@ pthread_condattr_setclock (pthread_condattr_t *attr, clockid_t clock_id) in the pthread_cond_t structure needs to be adjusted. */ return EINVAL; - /* If we do not support waiting using CLOCK_MONOTONIC, return an error. */ - if (clock_id == CLOCK_MONOTONIC - && !futex_supports_exact_relative_timeouts()) - return ENOTSUP; - /* Make sure the value fits in the bits we reserved. */ assert (clock_id < (1 << COND_CLOCK_BITS)); -- cgit v1.1