Uh oh!
There was an error while loading. Please reload this page.
Remove OneThread - #116185
Conversation
rustbot
commented
Sep 26, 2023
r? @cjgillot (rustbot has picked a reviewer for you, use r? to override) |
petrochenkov
commented
Sep 27, 2023
It would be good to have the motivation written out explicitly for changes like this. Why was |
Zoxc
commented
Sep 30, 2023
Both |
cjgillot
commented
Sep 30, 2023
This |
bjorn3
commented
Sep 30, 2023
That would be nice. More mutable state has been moved out of |
bjorn3
commented
Sep 30, 2023
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 |
bors
commented
Oct 13, 2023
☔ 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.
bors
commented
Jan 9, 2024
☔ The latest upstream changes (presumably #119767) made this pull request unmergeable. Please resolve the merge conflicts. |
Zoxc
commented
Jan 18, 2024
@rustbot ready
That's not actually an invariant though. |
cjgillot
commented
Jan 20, 2024
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
bors
commented
Jan 20, 2024
Remove `OneThread` This removes `OneThread` by switching `incr_comp_session` over to `RwLock`.
bors
commented
Jan 20, 2024
☀️ Try build successful - checks-actions |
1 similar comment
bors
commented
Jan 20, 2024
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Jan 20, 2024
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%) |
cjgillot
commented
Jan 20, 2024
@bors r+ |
bors
commented
Jan 20, 2024
bors
commented
Jan 20, 2024
bors
commented
Jan 20, 2024
☀️ Test successful - checks-actions |
rust-timer
commented
Jan 20, 2024
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
OneThreadby switchingincr_comp_sessionover toRwLock.