mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 13:13:44 +01:00
e531d4d1b9
Bug 1: We were purporting to calculate milliseconds per tick, when we *should* have been computing ticks per millisecond. Bug 2: Instead of computing either one of those, we were _actually_ computing femtoseconds per tick. These two bugs covered for one another on x86 hardware, where 1 tick == 1 nanosecond. But on M1 OSX, 1 tick is about 41 nanoseconds, causing surprising results. Fixes bug 40684; bugfix on 0.3.3.1-alpha.
7 lines
332 B
Plaintext
7 lines
332 B
Plaintext
o Major bugfixes (OSX):
|
|
- Fix coarse-time computation on Apple platforms (like Mac M1) where
|
|
the Mach absolute time ticks do not correspond directly to
|
|
nanoseconds. Previously, we computed our shift value wrong, which
|
|
led us to give incorrect timing results.
|
|
Fixes bug 40684; bugfix on 0.3.3.1-alpha.
|