diff options
author | Auke Kok <sofar@foo-projects.org> | 2016-01-23 23:06:26 -0800 |
---|---|---|
committer | ShadowNinja <shadowninja@minetest.net> | 2016-01-29 00:58:08 -0500 |
commit | 4ac1e9bccbd0222ab779b3fc4d2144d60e1f2b49 (patch) | |
tree | 4c509943cda1bb0473961bcf58adf366e32bd2f6 /src/irr_aabb3d.h | |
parent | 860d70bd0e228ee542e3e559961bfc7e56888d77 (diff) | |
download | minetest-4ac1e9bccbd0222ab779b3fc4d2144d60e1f2b49.tar.gz minetest-4ac1e9bccbd0222ab779b3fc4d2144d60e1f2b49.tar.bz2 minetest-4ac1e9bccbd0222ab779b3fc4d2144d60e1f2b49.zip |
Clocksource: use a better clock if available.
clock_gettime() is a far better clock than gettimeofday().
Even better than clock_gettime() is that you can select either
CLOCK_MONOTONIC, or even CLOCK_MONOTONIC_RAW. These clocks offer
high precision time. And the _RAW variant will never roll back
due to NTP drift or daylight savings, or otherwise.
I've adjusted this code to select the right clock method auto-
matically based on what's available in the OS. This means that
if you're running a very old linux version, MacOS or other,
you will automatically get the best clocksource available.
I've tested all Linux clocksources by selectively compiling and
running a 10k+ timer test suite. In all cases I confirmed that
the 3 POSIX Linux clocksources worked properly, and were
selected properly.
I've modified the OS X compile path to use the high-res clock
source for all time functions, but I can't confirm it works or
that it compiles.
As for WIN32, I confirmed that the used clocksource is indeed
a Monotonic clocksource, so good news: that code section appears
to be exactly what it should be.
Diffstat (limited to 'src/irr_aabb3d.h')
0 files changed, 0 insertions, 0 deletions