From c5b4bbd1816e0acb25d8b1ac302e097a1669dc44 Mon Sep 17 00:00:00 2001 From: Patrick O'Leary Date: Tue, 10 Nov 2015 17:28:45 -0600 Subject: [PATCH] on OS X, use SYSTEM_CLOCK, not CALENDAR_CLOCK Analogously to using `CLOCK_MONOTONIC` on Linux to time events in favor of `CLOCK_REALTIME`, `SYSTEM_CLOCK` should be used in favor of `CALENDAR_CLOCK` on OS X. Ref: http://stackoverflow.com/questions/11680461/monotonic-clock-on-osx --- src/impl/unix.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/impl/unix.cc b/src/impl/unix.cc index e0a8953..0ff251e 100755 --- a/src/impl/unix.cc +++ b/src/impl/unix.cc @@ -85,7 +85,7 @@ MillisecondTimer::timespec_now () # ifdef __MACH__ // OS X does not have clock_gettime, use clock_get_time clock_serv_t cclock; mach_timespec_t mts; - host_get_clock_service(mach_host_self(), CALENDAR_CLOCK, &cclock); + host_get_clock_service(mach_host_self(), SYSTEM_CLOCK, &cclock); clock_get_time(cclock, &mts); mach_port_deallocate(mach_task_self(), cclock); time.tv_sec = mts.tv_sec;