Rollup of 5 pull requests - #162640
Conversation
…ialization to make DefId creation in it deterministic
Instead of Tier 2 without host tools table.
…cnr,BoxyUwU Rename various resolving functions for consistency, and document them r? @lcnr or anyone in @rust-lang/initiative-trait-system-refactor This is all changes from https://github.com/rust-lang/rust/pull/160913/changes that are *just* renames. Updating that PR to be *just* the logic changes All interesting changes happened in `rustc_infer/src/infer/mod.rs` across all commits. Everything else is renames propagating through other files. The functions are now called: | before | after | note | |---|---|---| | `shallow_resolve_*` | (unchanged) `shallow_resolve_*` | Now with newly added docs. | | `resolve_vars_if_possible_*` | `deeply_resolve_ignoring_regions_*` | | | `eager_resolve_vars` | `deeply_resolve_via_unification_table` | moved onto the `InferCtxtLike` as an inherent method with default body. | | `fully_resolve` |`deeply_resolve_via_region_graph` | Resolves *with* regions and asserts that all variables are resolved at the end. Note, we only use this function 3x so the long name is ok, it shouldn't be your go-to anyway. | | `opportunistic_resolve_var` | | gone, same as `shalllow_resolve` now that we resolve to roots | > [!NOTE] > I've not used an LLM for any part of this PR, or any other PR I make. This includes any related work like research.
…, r=jieyouxu Respect `--all-targets` flag when checking the compiler Chris was trying to get `x check library --all-targets` working in https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Checking.20std.20tests.20without.20building/with/613735399. I took a look into this and realized that the `x check --all-targets` flag is literally unused - nothing in bootstrap was reading it. So the compiler and library were never checked with `--all-targets`, but on the other hands all tools are checked with `--all-targets` (or equivalent) by default, even without the flag. The library seems to be broken with `x check --all-targets`, but compiler works. This PR thus enables `--all-targets` for the compiler. Tools are still checked with all targets unconditionally.
…body, r=petrochenkov Parallel frontend: reproducible coroutine_by_move_body_def_id Adds test for and fixes `DefId` creation reproducibility issue in `coroutine_by_move_body_def_id` that came up in rust-lang#162202 r? @petrochenkov
…regression, r=petrochenkov add regression test for RPITIT fulfillment error Closes rust-lang#159680
…f-target-tier-docs, r=JohnTitor Move `riscv64im-unknown-none-elf` to Tier 3 table Instead of Tier 2 without host tools table. Noticed when looking at `i686-pc-windows-msvc` target docs and rust-lang#113739.
|
@bors r+ p=5 |
This comment has been minimized.
This comment has been minimized.
…uwer Rollup of 5 pull requests Successful merges: - #162126 (Rename various resolving functions for consistency, and document them) - #160681 (Respect `--all-targets` flag when checking the compiler) - #162580 (Parallel frontend: reproducible coroutine_by_move_body_def_id ) - #162614 (add regression test for RPITIT fulfillment error) - #162626 (Move `riscv64im-unknown-none-elf` to Tier 3 table)
|
💔 Test for 3c4d262 failed: CI. Failed job:
|
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing ada41e1 (parent) -> 3fbb92e (this PR) Test differencesShow 51 test diffsStage 1
Stage 2
Additionally, 44 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3fbb92e14159dd8b9bdb81e065883d1132e5abb7 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
📌 Perf builds for each rolled up PR:
parent commit: ada41e1ce8 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (3fbb92e): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -1.1%, secondary -2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.3%, secondary -2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 497.659s -> 492.981s (-0.94%) |
Successful merges:
--all-targetsflag when checking the compiler #160681 (Respect--all-targetsflag when checking the compiler)riscv64im-unknown-none-elfto Tier 3 table #162626 (Moveriscv64im-unknown-none-elfto Tier 3 table)r? @ghost
Create a similar rollup