-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add clock_gettime shim #975
Conversation
2ffc663
to
5259ebe
Compare
You could calculate the opposite difference (UNIX_EPOCH-now) and then write a negative number, as |
That sounds like a good idea. I'll try to do that |
Also CI is failing because the size of Edit: Solved by recovering the types from the target's |
☔ The latest upstream changes (presumably #977) made this pull request unmergeable. Please resolve the merge conflicts. |
bbef7a0
to
e00db1b
Compare
☔ The latest upstream changes (presumably #983) made this pull request unmergeable. Please resolve the merge conflicts. |
Yeah this looks good, thanks a lot. :) @bors r+ |
📌 Commit f9c7688 has been approved by |
Add clock_gettime shim r? @oli-obk I think there is no way to do proper testing of this other than checking that miri does not crash when calling `clock_gettime`.
That push aborted landing the PR I think. @bors r+ retry |
📌 Commit f9c7688 has been approved by |
Add clock_gettime shim r? @oli-obk I think there is no way to do proper testing of this other than checking that miri does not crash when calling `clock_gettime`.
☀️ Test successful - checks-travis, status-appveyor |
Thank you, I did a commit to the wrong branch by accident D: |
r? @oli-obk
I think there is no way to do proper testing of this other than checking that miri does not crash when calling
clock_gettime
.