[WIP] Make get-internal-real-time monotonic #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Also: #20
This work-in-progress PR moves
ccl:current-time-in-nanoseconds
from lib/time to l1-lisp-threads, and uses it to implementget-internal-real-time
andccl::get-tick-count
.The previous implementation of
get-internal-real-time
remembered the initial seconds value and subtracted it from values before returning them. I.e. the values returned byget-internal-real-time
would be close to zero after starting CCL. The new implementation does no such thing, the value returned is relative to system boot time.Additionally it changes
ccl:current-time-in-nanoseconds
toCould anyone on Windows/Darwin test these changes? I remember Microsoft to provide virtual machine images for testing, but I doubt they include a C compiler? Anyway, this should print as shown below: