clock_gettime function only returns seconds.

[MarkCallow]

clock_gettime has two problems.

• It does not use a monotonic timer when CLOCK_MONOTONIC is set.
• It does not set the nanosecond part of the returned timespec.

Something like the following change should be made

-    var now = Date.now();
-    {{{ makeSetValue('tp', '___timespec_struct_layout.tv_sec', 'Math.floor(now/1000)', 'i32') }}}; // seconds

-    {{{ makeSetValue('tp', '___timespec_struct_layout.tv_nsec', '0', 'i32') }}}; // nanoseconds - not supported
----
+   var now, msec, fmsec;
+   if (clk_id == CLOCK_REALTIME) {
+     now = Date.now();
+   } else {
+     now = performance.now();
+   }
+   msec = Math.floor(now);
+   fmsec = now - msec;
+   {{{ makeSetValue('tp', '___timespec_struct_layout.tv_sec', 'msec/1000', 'i32') }}}; // seconds

+   {{{ makeSetValue('tp', '___timespec_struct_layout.tv_nsec', 'fmsec*1000', 'i32') }}}; // nanoseconds

I'm not sure how widespread support is for the high resolution timer (performance.now()).

[Daft-Freak]

clock_gettime does now set the nanoseconds:
https://github.com/kripken/emscripten/blob/master/src/library.js#L6123

using performance.now() for CLOCK_MONOTONIC does seem like a good idea though. (and process.hrtime() for node?)

[kripken]

Yeah, performance.now is a good idea, I did that on incoming. Please test it though as I am not sure I did it correctly.

[Daft-Freak]

Seems to work fine, thanks!

[Daft-Freak]

clock_getres still returns that the resolution is in milliseconds.

[kripken]

Good point, thanks. Fixed that too.