http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41861
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|SUSPENDED |NEW
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-07-03
16:23:30 UTC ---
887 is NAD, reopening.
This is a QoI issue, but even if monotonic clock support was added to gthreads
(by which I assume people mean providing an API for pthread_condattr_setclock)
we couldn't meet all the QoI suggestions.
The standard says implementations should use a steady clock for xxx_for, but
should use the user-provided clock for xxx_until. It's not possible to do both
on POSIX, because a condition variable has a single clock, set on construction,
and mutexes always use the system clock.
