mirror of
https://sourceware.org/git/glibc.git
synced 2024-11-27 19:53:32 +08:00
nptl: Remove futex_wait_cancelable
It is used solely on __pthread_cond_wait_common and the call can be replaced by a __futex_abstimed_wait_cancelable64 one. Checked on x86_64-linux-gnu and i686-linux-gnu. Reviewed-by: Lukasz Majewski <lukma@denx.de>
This commit is contained in:
parent
7e9afa8a84
commit
2e39f65b5e
@ -501,26 +501,8 @@ __pthread_cond_wait_common (pthread_cond_t *cond, pthread_mutex_t *mutex,
|
||||
cbuffer.private = private;
|
||||
__pthread_cleanup_push (&buffer, __condvar_cleanup_waiting, &cbuffer);
|
||||
|
||||
if (abstime == NULL)
|
||||
{
|
||||
/* Block without a timeout. */
|
||||
err = futex_wait_cancelable (
|
||||
cond->__data.__g_signals + g, 0, private);
|
||||
}
|
||||
else
|
||||
{
|
||||
/* Block, but with a timeout.
|
||||
Work around the fact that the kernel rejects negative timeout
|
||||
values despite them being valid. */
|
||||
if (__glibc_unlikely (abstime->tv_sec < 0))
|
||||
err = ETIMEDOUT;
|
||||
else
|
||||
{
|
||||
err = __futex_abstimed_wait_cancelable64
|
||||
(cond->__data.__g_signals + g, 0, clockid, abstime,
|
||||
private);
|
||||
}
|
||||
}
|
||||
err = __futex_abstimed_wait_cancelable64 (
|
||||
cond->__data.__g_signals + g, 0, clockid, abstime, private);
|
||||
|
||||
__pthread_cleanup_pop (&buffer, 0);
|
||||
|
||||
|
@ -177,35 +177,6 @@ futex_wait_simple (unsigned int *futex_word, unsigned int expected,
|
||||
ignore_value (futex_wait (futex_word, expected, private));
|
||||
}
|
||||
|
||||
|
||||
/* Like futex_wait but is a POSIX cancellation point. */
|
||||
static __always_inline int
|
||||
futex_wait_cancelable (unsigned int *futex_word, unsigned int expected,
|
||||
int private)
|
||||
{
|
||||
int oldtype;
|
||||
oldtype = __pthread_enable_asynccancel ();
|
||||
int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
|
||||
__pthread_disable_asynccancel (oldtype);
|
||||
switch (err)
|
||||
{
|
||||
case 0:
|
||||
case -EAGAIN:
|
||||
case -EINTR:
|
||||
return -err;
|
||||
|
||||
case -ETIMEDOUT: /* Cannot have happened as we provided no timeout. */
|
||||
case -EFAULT: /* Must have been caused by a glibc or application bug. */
|
||||
case -EINVAL: /* Either due to wrong alignment or due to the timeout not
|
||||
being normalized. Must have been caused by a glibc or
|
||||
application bug. */
|
||||
case -ENOSYS: /* Must have been caused by a glibc bug. */
|
||||
/* No other errors are documented at this time. */
|
||||
default:
|
||||
futex_fatal_error ();
|
||||
}
|
||||
}
|
||||
|
||||
/* Like futex_wait, but will eventually time out (i.e., stop being
|
||||
blocked) after the duration of time provided (i.e., RELTIME) has
|
||||
passed. The caller must provide a normalized RELTIME. RELTIME can also
|
||||
|
Loading…
Reference in New Issue
Block a user