| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
it obvious that truncation is occuring. Something to deal with in 2038
I guess, though get_nanoseconds_clock is already an unknown/unspecified
epoch (since the Windows timer uses 1/1/1601 as the epoch)
|
|
|
|
| |
the calendar time without tying to a particular format. From the C++0x branch.
|
| |
|
|
|
|
|
|
|
| |
Add macros for OS support of gmtime_r (Unix) and gmtime_s (Win32) to deal
with thread-unsafety of std::gmtime. Only enable gmtime_r on Linux currently,
but it's probably available pretty much everywhere (specified in pthreads,
origininally, AFAICT).
|
| |
|
|
QueryPerformanceCounter, into an entropy source hres_timer. Its
results, if any, do not count as contributing entropy to the poll.
Convert the other (monotonic/fixed epoch) timers to a single function
get_nanoseconds_clock(), living in time.h, which statically chooses
the 'best' timer type (clock_gettime, gettimeofday, std::clock, in
that order depending on what is available). Add feature test macros
for clock_gettime and gettimeofday.
Remove the Timer class and timer.h. Remove the Timer& argument to the
algorithm benchmark function.
|