This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14717] Allow choice of clock source for calls to sem_timedwait() and pthread_mutex_timedwait().
- From: "nok2 at kirkeby dot nu" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 25 Apr 2016 07:51:24 +0000
- Subject: [Bug nptl/14717] Allow choice of clock source for calls to sem_timedwait() and pthread_mutex_timedwait().
- Auto-submitted: auto-generated
- References: <bug-14717-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14717
Niels <nok2 at kirkeby dot nu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nok2 at kirkeby dot nu
--- Comment #9 from Niels <nok2 at kirkeby dot nu> ---
Hmm, I'm into this problem as well. But futex(2) has supported CLOCK_MONOTONIC
at least since linux kernel 3.0. It does not support CLOCK_MONOTONIC_RAW. Hint:
just OR your futex command with FUTEX_CLOCK_REALTIME.
So maybe it falls back to the libc implementors after all. It should be more or
less just a matter of cut'n'paste sem_timedwait() but just with OR'ing all
FUTEX-commands with FUTEX_CLOCK_REALTIME.
--
You are receiving this mail because:
You are on the CC list for the bug.