> Date: Wed, 20 Apr 2022 12:23:43 -0700 > Cc: maniku...@gmail.com, emacs-orgm...@gnu.org, 54...@debbugs.gnu.org, > bug-gnulib@gnu.org > From: Paul Eggert <egg...@cs.ucla.edu> > > On 4/20/22 12:14, Eli Zaretskii wrote: > > Sorry, my bad. The result is the same, but I do get printouts. What > > do you want to know or see from there? > > I want to see what the current_timespec's resolution is, which we should > be able to tell from the debugging output. For example, on my Solaris 10 > sparc platform the command 'gltests/test-gettime-res x' outputs: > > gettime_res returned 200 ns > time = 1650482432.256445600 > time = 1650482432.256460600 > time = 1650482432.256464400 > time = 1650482432.256468200 > time = 1650482432.256471400 > time = 1650482432.256474600 > time = 1650482432.256478000 > time = 1650482432.256481200 > time = 1650482432.256484800 > ... > > and these timestamps say that with very high probability > current_timespec's clock resolution is indeed 200 ns.
I see the time samples change in jumps of 15 msec. Which is expected on MS-Windows, given the scheduler time tick, but what does that have to do with the system's time resolution? And how is the 0.625 msec number reported by the program obtained from those samples?
