-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
openbsd: convert futex timeout managment to Timespec usage #96860
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
r? @m-ou-se (rust-highfive has picked a reviewer for you, use r? to override) |
ah, bad syntax for my r? command ... so just cc @cuviper , and I will let you rearrange assignation the way you prefer. thanks |
the build previously failed with :
|
Yeah, that's going to happen on more platforms. Maybe we should just add #[allow(dead_code)] // not used on all platforms to |
0c42393
to
d8ccbb5
Compare
@cuviper what do you think about it ? |
I think |
☔ The latest upstream changes (presumably #96904) made this pull request unmergeable. Please resolve the merge conflicts. |
05b0ec7
to
42f8e1f
Compare
rebased after #96861 |
@bors r+ rollup |
📌 Commit 42f8e1f has been approved by |
…askrgr Rollup of 5 pull requests Successful merges: - rust-lang#95896 (Note the contacts for the nvptx64 target(s)) - rust-lang#96860 (openbsd: convert futex timeout managment to Timespec usage) - rust-lang#96939 (Fix settings page CSS) - rust-lang#96941 (update graphviz links) - rust-lang#96968 (Add tests for rust-lang#96806) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
unbreak openbsd build after #96657
r? cuviper
please note I made
Timespec::zero()
public to be able to use it. OpenBSD is using relative timeout forfutex(2)
and I don't find simple way to useTimespec
this way.