diff options
author | Benoit Daloze <eregontp@gmail.com> | 2020-04-13 18:23:39 +0200 |
---|---|---|
committer | Benoit Daloze <eregontp@gmail.com> | 2020-04-13 18:23:39 +0200 |
commit | a6f7458ea81e084f6ebe7dc5c8cb5b7cb70fe2be (patch) | |
tree | 77010d77261ce6daf45c2181898f635244c1280e | |
parent | c28e230ab5865df55399431239c5fdd9b54206d6 (diff) | |
download | ruby-a6f7458ea81e084f6ebe7dc5c8cb5b7cb70fe2be.tar.gz |
Add a a list of cases for which clock_getres() has been observed to be inaccurate
* See [Bug #16740]
-rw-r--r-- | process.c | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -7959,8 +7959,11 @@ rb_clock_gettime(int argc, VALUE *argv, VALUE _) * <code>clock_getres()</code> function. * * 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. + * 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. * See the document of +Process.clock_gettime+ for details. |