зеркало из https://github.com/mozilla/gecko-dev.git
b75080bb8b
On Linux and Android, both jitdump and the marker file will keep using `CLOCK_MONOTONIC` nanoseconds, as before. On macOS, both jitdump and the marker file will now be using `TimeStamp::RawMachAbsoluteTimeNanoseconds()` , i.e. "nanoseconds since mach_absolute_time origin". This value has the advantage that it is also relatively easy to obtain in other browser engines, because their internal timestamp value is stored in milliseconds or nanoseconds rather than in `mach_absolute_time` ticks. In the past, on macOS, Firefox was using `CLOCK_MONOTONIC` nanoseconds for jitdump and `TimeStamp::RawMachAbsoluteTimeValue()` for the marker file. This inconsistency is now fixed. I will update samply to change how it treats jitdump timestamps on macOS. There are no other consumers of jitdump files on macOS that I know of. On Windows, we will keep using raw QPC values for the marker file - this matches what's in the ETW events. Jitdump on Windows is mostly unused but I'm updating it to match. Furthermore, this fixes the order in mozglue/misc/moz.build to make sure we always use the TimeStamp_darwin implementation on Darwin (and not just due to a broken configure check, see bug 1681445), and it fixes the #ifdef in TimeStamp.h to match the Darwin check. Differential Revision: https://phabricator.services.mozilla.com/D199592 |
||
|---|---|---|
| .. | ||
| android | ||
| baseprofiler | ||
| build | ||
| interposers | ||
| linker | ||
| misc | ||
| static | ||
| tests | ||
| moz.build | ||