-
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
Remove OneThread
#116185
Remove OneThread
#116185
Conversation
r? @cjgillot (rustbot has picked a reviewer for you, use r? to override) |
It would be good to have the motivation written out explicitly for changes like this. Why was |
Both |
This |
That would be nice. More mutable state has been moved out of |
One thing however is that I would also like to be able to finalize the incremental session from within a codegen backend. The (experimental) jit mode of cg_clif never returns control back to rustc_interface after codegen has ended. It directly runs the program and exits. This means incremental compilation is currently broken with the jit mode. For the regular jit mode it would technically be possible to move execution to |
☔ The latest upstream changes (presumably #115964) made this pull request unmergeable. Please resolve the merge conflicts. |
This comment has been minimized.
This comment has been minimized.
☔ The latest upstream changes (presumably #119767) made this pull request unmergeable. Please resolve the merge conflicts. |
@rustbot ready
That's not actually an invariant though. |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Remove `OneThread` This removes `OneThread` by switching `incr_comp_session` over to `RwLock`.
☀️ Try build successful - checks-actions |
1 similar comment
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (c8e6073): comparison URL. Overall result: no relevant changes - 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 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. Binary sizeResultsThis 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.
Bootstrap: 663.584s -> 663.307s (-0.04%) |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6745c60): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis 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.
Bootstrap: 665.464s -> 666.038s (0.09%) |
This removes
OneThread
by switchingincr_comp_session
over toRwLock
.