|
From: | Paul Eggert |
Subject: | Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones |
Date: | Wed, 20 Apr 2022 12:23:43 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 |
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.
[Prev in Thread] | Current Thread | [Next in Thread] |