80081475f1
Even though pthreads doesn't support this, there are various alternative APIs that use this. For example, uv_cond_timedwait() accepts a relative timeout. So does Rust's std::sync::Condvar::wait_timeout(). Though I personally think that relative timeouts are bad (due to imprecision for repeated operations), it does seem that people want this. Extend the existing futex functions to keep track of whether an absolute timeout is used in a boolean flag. MFC after: 1 month |
||
|---|---|---|
| .. | ||
| cloudabi_clock.c | ||
| cloudabi_errno.c | ||
| cloudabi_fd.c | ||
| cloudabi_file.c | ||
| cloudabi_futex.c | ||
| cloudabi_mem.c | ||
| cloudabi_proc.c | ||
| cloudabi_proto.h | ||
| cloudabi_random.c | ||
| cloudabi_sock.c | ||
| cloudabi_thread.c | ||
| cloudabi_util.h | ||
| cloudabi_vdso.c | ||
| cloudabi_vdso.lds | ||