rustc_codegen_ssa: Correctly apply the static --jobs-backend limit to backend parallelism - #160387
Open
petrochenkov wants to merge 1 commit into
Open
rustc_codegen_ssa: Correctly apply the static --jobs-backend limit to backend parallelism#160387petrochenkov wants to merge 1 commit into
--jobs-backend limit to backend parallelism#160387petrochenkov wants to merge 1 commit into
Conversation
…to backend parallelism
rustbot
added
S-waiting-on-review
Contributor
|
☔ The latest upstream changes (presumably #160411) made this pull request unmergeable. Please resolve the merge conflicts by rebasing. |
Contributor
Author
|
This PR will become simpler if #160424 is merged first. |
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Aug 3, 2026
Use `thread::available_parallelism` as the default limit for backend parallelism Instead of the old scheme with 32-or-unlimited, depending on inherited-ness of the jobserver. Not sure if this needs some wider discussion or not. In the most common case (rustc is called from cargo) nothing changes, because cargo already limits the parallelism to `thread::available_parallelism` by default, and passes this limit to rustc through jobserver. rust-lang#160387 will become simpler if this PR is merged first. r? @bjorn3 @Zoxc
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Aug 3, 2026
Use `thread::available_parallelism` as the default limit for backend parallelism Instead of the old scheme with 32-or-unlimited, depending on inherited-ness of the jobserver. Not sure if this needs some wider discussion or not. In the most common case (rustc is called from cargo) nothing changes, because cargo already limits the parallelism to `thread::available_parallelism` by default, and passes this limit to rustc through jobserver. rust-lang#160387 will become simpler if this PR is merged first. r? @bjorn3 @Zoxc
JonathanBrouwer
added a commit
to JonathanBrouwer/rust
that referenced
this pull request
Aug 3, 2026
Use `thread::available_parallelism` as the default limit for backend parallelism Instead of the old scheme with 32-or-unlimited, depending on inherited-ness of the jobserver. Not sure if this needs some wider discussion or not. In the most common case (rustc is called from cargo) nothing changes, because cargo already limits the parallelism to `thread::available_parallelism` by default, and passes this limit to rustc through jobserver. rust-lang#160387 will become simpler if this PR is merged first. r? @bjorn3 @Zoxc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up to #159675.
r? @bjorn3