-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Avoid a few locks #109117
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
Avoid a few locks #109117
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @michaelwoerister (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
@bors try @rust-timer queue |
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 5ac97021ecaa10a9a71bbb1b02a5ac9034ecd998 with merge 373a5c1ab3f3ab2f54dcb45edd9e3a40a10783c9... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (373a5c1ab3f3ab2f54dcb45edd9e3a40a10783c9): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
Sounds good! I'll try to review within the next couple of days. |
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.
Looks good to me! I've left a few comments below.
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri |
@bors r=michaelwoerister |
📌 Commit da3d4abb103a3469a997a7b7b0a12ef8eda4214e has been approved by It is now in the queue for this repository. |
⌛ Testing commit da3d4abb103a3469a997a7b7b0a12ef8eda4214e with merge c0a435cb4b538fcba4901b9da6615c3a8c8120a3... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors retry SIGSEGV due to LLVM upgrade |
This comment has been minimized.
This comment has been minimized.
I can reproduce the segfault locally in parallel-rustc. Investigating... |
These commits modify the If this was intentional then you can ignore this comment. |
This comment was marked as outdated.
This comment was marked as outdated.
I fixed the issue upstream in @bors r=michaelwoerister |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
Finished benchmarking commit (383c1d7): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
We can use atomics or datastructures tuned for specific access patterns instead of locks. This may be an improvement for parallel rustc, but it's mostly a cleanup making various datastructures only usable in the way they are used right now (append data, never mutate), instead of having a general purpose lock.