DotDebianandClaude Opus 5.5 096bdb38c2 fix(libkernel): give CLOCK_VIRTUAL, CLOCK_PROF and CLOCK_SECOND their FreeBSD meaning ...

clock_gettime and clock_getres served three FreeBSD clock ids with the wrong
clock or not at all:

- CLOCK_VIRTUAL (1) was the monotonic clock on Windows and threw on Linux; it
  is the user CPU time of the process.
- CLOCK_PROF (2) threw on both hosts; it is the user plus system CPU time of
  the process.
- CLOCK_SECOND (13) returned the coarse realtime clock with nanoseconds and a
  sub-second resolution; it is the current second with tv_nsec 0 and a
  resolution of one second.

Behaviour follows FreeBSD 11 clock_gettime(2) and kern_clock_gettime /
kern_clock_getres in sys/kern/kern_time.c.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-05 10:24:22 +02:00

..

include

feat(runtime): timed waits, sync primitive fixes, heap and RTC fixes, unattended-run switches

2026-09-26 19:00:39 -07:00

Time.cpp

fix(libkernel): give CLOCK_VIRTUAL, CLOCK_PROF and CLOCK_SECOND their FreeBSD meaning

2026-10-05 10:24:22 +02:00

TimedWait.cpp

feat(runtime): timed waits, sync primitive fixes, heap and RTC fixes, unattended-run switches

2026-09-26 19:00:39 -07:00