Skip to content

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
wants to merge 18 commits into from
Closed

Conversation

Dylan-DPC
Copy link
Member

creating a rollup manually since bors is acting weird

r? @ghost

jendrikw and others added 18 commits January 13, 2022 14:33
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)
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.
@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Mar 4, 2022
@Dylan-DPC Dylan-DPC added the rollup A PR which is a rollup label Mar 4, 2022
@Dylan-DPC
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Mar 4, 2022

📌 Commit 3fe5163 has been approved by Dylan-DPC

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Mar 4, 2022
@bors
Copy link
Collaborator

bors commented Mar 4, 2022

⌛ Testing commit 3fe5163 with merge 09d87dd176d3fc1171490af5aee7a97e39241d3e...

@rust-log-analyzer
Copy link
Collaborator

The job dist-x86_64-illumos failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
[TIMING] Rustc { compiler: Compiler { stage: 2, host: TargetSelection { triple: "x86_64-unknown-illumos", file: None } } } -- 22.032
Dist rust-std-nightly-x86_64-unknown-illumos
 finished in 10.211 seconds
[TIMING] Std { compiler: Compiler { stage: 1, host: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None } }, target: TargetSelection { triple: "x86_64-unknown-illumos", file: None } } -- 10.213
thread 'main' panicked at 'could not read dir "/checkout/src/build_helper": Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/bootstrap/lib.rs:1462:25
Build completed unsuccessfully in 0:14:04

@bors
Copy link
Collaborator

bors commented Mar 4, 2022

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 4, 2022
@Dylan-DPC Dylan-DPC closed this Mar 4, 2022
@Dylan-DPC Dylan-DPC deleted the rollup-sar3rcr branch March 4, 2022 16:29
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants