about summary refs log tree commit diff
path: root/signal/sigaltstack.c
diff options
context:
space:
mode:
authorMike Crowe <mac@mcrowe.com>2019-06-24 20:18:00 +0000
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2019-07-12 13:36:25 +0000
commit1ff1373b3302e9e095dc4fd4d371451c00190780 (patch)
treea2674e19f74165d5825c272dc7f4838c86d65ef8 /signal/sigaltstack.c
parent65dd7e9ce36ca8485a68ed41ac731188b6473dd2 (diff)
downloadglibc-1ff1373b3302e9e095dc4fd4d371451c00190780.tar.gz
glibc-1ff1373b3302e9e095dc4fd4d371451c00190780.tar.xz
glibc-1ff1373b3302e9e095dc4fd4d371451c00190780.zip
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 <adhemerval.zanella@linaro.org>
Diffstat (limited to 'signal/sigaltstack.c')
0 files changed, 0 insertions, 0 deletions