From c23acb9b5636e7b908fba03d6b3584d8f80dba6d Mon Sep 17 00:00:00 2001 From: Derek Mauro Date: Wed, 12 Apr 2023 13:26:48 -0700 Subject: Synchronization: Consolidate the logic for whether steady clocks are supported for relative timeouts PiperOrigin-RevId: 523789416 Change-Id: Ide4cfdcae9ea7bffca3355c80ea9c8833a9536e6 --- absl/synchronization/internal/stdcpp_waiter.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'absl/synchronization/internal/stdcpp_waiter.cc') diff --git a/absl/synchronization/internal/stdcpp_waiter.cc b/absl/synchronization/internal/stdcpp_waiter.cc index 8b5d1df4..355718a7 100644 --- a/absl/synchronization/internal/stdcpp_waiter.cc +++ b/absl/synchronization/internal/stdcpp_waiter.cc @@ -50,7 +50,7 @@ bool StdcppWaiter::Wait(KernelTimeout t) { if (!t.has_timeout()) { cv_.wait(lock); } else { - auto wait_result = t.is_relative_timeout() + auto wait_result = t.SupportsSteadyClock() && t.is_relative_timeout() ? cv_.wait_for(lock, t.ToChronoDuration()) : cv_.wait_until(lock, t.ToChronoTimePoint()); if (wait_result == std::cv_status::timeout) { -- cgit v1.2.3