-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Use futex-based locks and thread parker on {Free, Open, DragonFly}BSD. #96510
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
cc @semarie |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The implementation mostly looks good to me. Have you actually tested these on a BSD system? We don't test those in CI.
We don't guarantee this panics. On most platforms it doesn't anymore.
I've tested this change on FreeBSD, and all of |
@bors r+ rollup=never |
📌 Commit 21c5f78 has been approved by |
⌛ Testing commit 21c5f78 with merge 3beddd083e1fd318b89445a6282e80c46da01c5f... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (7f9e013): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
This switches *BSD to our futex-based locks and thread parker.
Tracking issue: #93740
r? @Amanieu