-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 9 pull requests #94606
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
Closed
Closed
Rollup of 9 pull requests #94606
Conversation
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
autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
Co-authored-by: Josh Triplett <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Follow up to rust-lang#92746. Address rust-lang#94510.
The majority of the code is only used by either rustbuild or rustc_llvm's build script. Rust_build is compiled once for rustbuild and once for every stage. This means that the majority of the code in this crate is needlessly compiled multiple times. By moving only the code actually used by the respective crates to rustbuild and rustc_llvm's build script, this needless duplicate compilation is avoided.
…lett add #[must_use] to functions of slice and its iterators. See rust-lang#89692.
…lacrum Remove build_helper The majority of the code is only used by either rustbuild or rustc_llvm's build script. Rust_build is compiled once for rustbuild and once for every stage. This means that the majority of the code in this crate is needlessly compiled multiple times. By moving only the code actually used by the respective crates to rustbuild and rustc_llvm's build script, this needless duplicate compilation is avoided.
Bump autocfg to 1.1.0 autocfg 1.1.0 makes it so that rustflags from the build are correctly passed to the compiler probes, which in turn means those probes more accurately reflect the outer build conditions. This is particularly important if rustflags includes _required_ `-Clink-arg=` flags without which builds will fail, as older versions of `autocfg` will then fail the probe and erroneously report the probed feature as unavailable. See also rust-lang#94007 (comment)
…lacrum Remove num_cpus dependency from bootstrap, build-manifest and rustc_s… …ession `std::threads::available_parallelism` was stabilized in rust 1.59. r? `````````````````````````@Mark-Simulacrum`````````````````````````
…ou-se Clean up the std library's #![feature]s Signed-off-by: JmPotato <[email protected]> This is part of rust-lang#87766. r? ``````````````````@m-ou-se``````````````````
Rename JoinHandle::is_running to is_finished. This is renaming `is_running` to `is_finished` as discussed on the tracking issue here: rust-lang#90470 (comment) Taking some of the docs suggestions from rust-lang#94033
Do not recover from `Ty?` in macro parsing Follow up to rust-lang#92746. Address rust-lang#94510.
@bors r+ rollup=never p=5 |
📌 Commit 3fe5163 has been approved by |
⌛ Testing commit 3fe5163 with merge 09d87dd176d3fc1171490af5aee7a97e39241d3e... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
rollup
A PR which is a rollup
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
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.
creating a rollup manually since bors is acting weird
r? @ghost