Bug 43843 - [profiler] Support clock_gettime (CLOCK_PROCESS_CPUTIME_ID) for sampling on Sierra
Summary: [profiler] Support clock_gettime (CLOCK_PROCESS_CPUTIME_ID) for sampling on S...
Alias: None
Product: Runtime
Classification: Mono
Component: Profiler ()
Version: master
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Alex Rønne Petersen
Depends on:
Reported: 2016-08-29 19:12 UTC by Alex Rønne Petersen
Modified: 2016-09-10 07:15 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Alex Rønne Petersen 2016-08-29 19:12:21 UTC
Currently, sampling on OS X is always based on real time, unlike other OSs, where we use clock_gettime (CLOCK_PROCESS_CPUTIME_ID) in the process time case. Sierra introduces clock_gettime () and friends, including CLOCK_PROCESS_CPUTIME_ID. We should dynamically detect the presence of that function and use it, so that we have the same sampling semantics across platforms.
Comment 1 Alex Rønne Petersen 2016-09-10 07:15:22 UTC
Looks like this won't be happening. Apparently Apple decided to implement clock_gettime, clock_getres, and some others, and a bunch of different clocks, but they didn't think to implement clock_nanosleep.