kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

Add a a list of cases for which clock_getres() has been observed to be inaccurate

Browse source 
* See [Bug #16740]
This commit is contained in:
Benoit Daloze 2020-04-13 18:23:39 +02:00
parent c28e230ab5
commit a6f7458ea8
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
process.c
View file

@ -7959,8 +7959,11 @@ rb_clock_gettime(int argc, VALUE *argv, VALUE _)
* <code>clock_getres()</code> function. * <code>clock_getres()</code> function.
* *
* Note the reported resolution is often inaccurate on most platforms due to * Note the reported resolution is often inaccurate on most platforms due to
* operating system bugs for this function and therefore the reported resolution * underlying bugs for this function and therefore the reported resolution
* often differs from the actual resolution of the clock in practice. * often differs from the actual resolution of the clock in practice.
* Inaccurate reported resolutions have been observed for various clocks including
* CLOCK_MONOTONIC and CLOCK_MONOTONIC_RAW when using Linux, macOS, BSD or AIX
* platforms, when using ARM processors, or when using virtualization.
* *
* +clock_id+ specifies a kind of clock. * +clock_id+ specifies a kind of clock.
* See the document of +Process.clock_gettime+ for details. * See the document of +Process.clock_gettime+ for details.