Re: gettime-res failure on Solaris 11/SPARC

2024-03-26 Thread Bruno Haible
Paul Eggert wrote: > > It doesn't work because it takes only 32 samples of current_timespec (). > > In order to work reliably it would need 10 million samples. > > Thanks for the fix. My puzzlement was more why one needs 10 million > samples. Perhaps it's possible to alter the test somewhat so th

Re: gettime-res failure on Solaris 11/SPARC

2024-03-26 Thread Paul Eggert
On 3/26/24 05:16, Bruno Haible wrote: It doesn't work because it takes only 32 samples of current_timespec (). In order to work reliably it would need 10 million samples. Thanks for the fix. My puzzlement was more why one needs 10 million samples. Perhaps it's possible to alter the test somewh

Re: gettime-res failure on Solaris 11/SPARC

2024-03-26 Thread Bruno Haible
Paul Eggert wrote: > > What shall we do with this one? Override gettime_res() to return 1 ns > > instead of 5 ns? Or adapt the unit test? > > Perhaps overriding is best. I'm a bit puzzled why the current code > doesn't work, though. It doesn't work because it takes only 32 samples of current_tim

Re: gettime-res failure on Solaris 11/SPARC

2024-03-25 Thread Paul Eggert
On 3/25/24 18:10, Bruno Haible wrote: What shall we do with this one? Override gettime_res() to return 1 ns instead of 5 ns? Or adapt the unit test? Perhaps overriding is best. I'm a bit puzzled why the current code doesn't work, though.

gettime-res failure on Solaris 11/SPARC

2024-03-25 Thread Bruno Haible
Hi Paul, On the new cfarm machine cfarm216.cfarm.net (Solaris 11.4, SPARC), the gettime-res test frequently fails, both in 32-bit and in 64-bit mode: $ ./test-gettime-res gettime_res returned 5 ns $ ./test-gettime-res gettime_res returned 5 ns current_timespec returned 1711414997.052976757 which