8 Commits

Author	SHA1	Message	Date
Nick Mathewson	7505f452c8	Run the copyright update script.	2017-03-15 16:13:17 -04:00
Nick Mathewson	22314f9050	loony mingwcross bug: insist we dont have clock_gettime.	2016-07-21 14:09:00 +02:00
Nick Mathewson	2d26b1a549	Actually make monotonic time functions mockable. ... This is different from making the functions mockable, since monotime_t is opaque and so providing mocks for the functions is really hard.	2016-07-21 07:02:33 -04:00
Nick Mathewson	72a1f0180d	Revert "Make the monotonic{_coarse,}_get() functions mockable." ... This reverts commit 2999f0b33f.	2016-07-21 10:30:21 +02:00
Nick Mathewson	2999f0b33f	Make the monotonic{_coarse,}_get() functions mockable.	2016-07-21 10:25:23 +02:00
Nick Mathewson	2a217ef723	Expose monotonic time ratchet functions for testing.	2016-07-19 11:40:47 +02:00
Nick Mathewson	dc6f5d1dc1	Basic portable monotonic timer implementation ... This code uses QueryPerformanceCounter() [**] on Windows, mach_absolute_time() on OSX, clock_gettime() where available, and gettimeofday() [*] elsewhere. Timer types are stored in an opaque OS-specific format; the only supported operation is to compute the difference between two timers. [*] As you know, gettimeofday() isn't monotonic, so we include a simple ratchet function to ensure that it only moves forward. [**] As you may not know, QueryPerformanceCounter() isn't actually always as monotonic as you might like it to be, so we ratchet that one too. We also include a "coarse monotonic timer" for cases where we don't actually need high-resolution time. This is GetTickCount{,64}() on Windows, clock_gettime(CLOCK_MONOTONIC_COARSE) on Linux, and falls back to regular monotonic time elsewhere.	2016-07-19 11:40:46 +02:00
Nick Mathewson	aa971c5924	Move our "what time is it now" compat functions into a new module ... I'm not moving our "format and parse the time" functions, since those have been pretty volatile over the last couple of years.	2016-07-08 10:38:59 -04:00