[libcxx-commits] [PATCH] D65339: Implement std::condition_variable via pthread_cond_clockwait() where available
Marshall Clow via Phabricator via libcxx-commits
libcxx-commits at lists.llvm.org
Tue Aug 13 10:17:55 PDT 2019
mclow.lists added inline comments.
Comment at: include/__mutex_base:476
+ typedef time_point<steady_clock, duration<long double, nano> > __c_tpf;
+ typedef time_point<steady_clock, nanoseconds> __c_tpi;
+ __c_tpf _Max = __c_tpi::max();
> EricWF wrote:
> > This assumes the resolution of the `steady_clock`, no?
> Sort of. It mostly assumes that steady_clock::now() can be converted into nanoseconds safely, which I think is a reasonable assumption to make. The old code assumed the resolution of system_clock too, so it's not a regression from there.
> I'm happy to hear a better solution, because both this code and the original have never sit well with me. What we really want is a safe_duration_cast, where we get a ceiling effect if there would be overflow. Since that is not how std::chrono was created, we're left with two options:
> 1) This function ends up with signed integer overflow if someone passes milliseconds::max() to it and steady/system_clock.
> 2) Work-arounds like this
> What we really want is a safe_duration_cast, where we get a ceiling effect if there would be overflow. Since that is not how std::chrono was created, we're left with two options:
I suggest a third option: Write `__safe_duration_cast`
CHANGES SINCE LAST ACTION
More information about the libcxx-commits