Rollup of 19 pull requests - #156023
Rollup of 19 pull requests#156023
Conversation
When an import like `use crate::a::b::Item` fails because module `b` is private, the resolver now looks up public re-export paths for `Item` and suggests them to the user.
Update link to queries.rs in tracing.md
…nts-description Update THIR element description
sembr some files
This updates the rust-version file to d493b7c.
Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: rust-lang/rust@d493b7c Filtered ref: rust-lang/rustc-dev-guide@8e19834 Upstream diff: rust-lang/rust@cf1817b...d493b7c This merge was created using https://github.com/rust-lang/josh-sync.
Rustc pull update
This comment has been minimized.
This comment has been minimized.
Rollup of 19 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple try-job: x86_64-mingw-1 try-job: i686-msvc-2
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 f53b654 (parent) -> 0469a92 (this PR) Test differencesShow 132 test diffsStage 1
Stage 2
Additionally, 82 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 0469a92a76c327df972cb6c1356934b7a0c6b86d --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:
previous master: f53b654a88 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (0469a92): comparison URL. Overall result: ❌ regressions - please read:Our benchmarks found a performance regression caused by this PR. Next Steps:
@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 (secondary 1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.0%, secondary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 487.787s -> 481.713s (-1.25%) |
|
perf triage: Tiny regressions in frontend (mainly expand_crate, so likely macro expansion). Primary regressions are limited to very small benchmarks ( I suspect it's one of the PRs that touches this code - #155237, #155919 or #155980, but all those changes look pretty innocent, so I think it's probably something like an inlining change caused by moving code around. I don't think this is worth digging into more, but the queue is empty so I kicked off a perf run on #155237. @rustbot label: +perf-regression-triaged |
Rollup of 19 pull requests Successful merges: - rust-lang#155237 (Disentangle AST crates and error crates) - rust-lang#155249 (Fix: On wasm targets, call `panic_in_cleanup` if panic occurs in cleanup) - rust-lang#155853 (Use `_mcount` as the mcount symbol name on RISC-V Linux GNU targets) - rust-lang#155919 (simplify `ast_fragments!`) - rust-lang#155939 (Add feature gate for view_types experiment) - rust-lang#155954 (rustdoc: preserve parent doc cfg for `macro_export` macros) - rust-lang#155974 (add `c_variadic_experimental_arch` feature) - rust-lang#155991 (Catch unwinds from the global ctxt callback to complete queries profiling data in more cases) - rust-lang#156003 (Pass Session to optimize_and_codegen_fat_lto) - rust-lang#153566 (Add suggestion for E0401 on inner const items) - rust-lang#154610 (Suggest public re-exports when a private module makes an import path inaccessible) - rust-lang#155523 (Reorganize `tests/ui/issues/` - 02) - rust-lang#155821 (c-variadic: document `Clone` and `Drop` instances and require `VaArgSafe: Copy`) - rust-lang#155980 (Move `feature*` methods from `parse` mod to `errors` mod.) - rust-lang#155987 (Make lifting infallible) - rust-lang#155988 (tests/run-make/print-cfg: add Android target_env case) - rust-lang#156000 (Fix ICE when using -Zinstrument-mcount and -Clinker-flavor=lld) - rust-lang#156002 (Allow to use `Diagnostic` directly in `SharedContext::emit_lint`) - rust-lang#156015 (rustc-dev-guide subtree update)
Successful merges:
panic_in_cleanupif panic occurs in cleanup #155249 (Fix: On wasm targets, callpanic_in_cleanupif panic occurs in cleanup)_mcountas the mcount symbol name on RISC-V Linux GNU targets #155853 (Use_mcountas the mcount symbol name on RISC-V Linux GNU targets)ast_fragments!#155919 (simplifyast_fragments!)macro_exportmacros #155954 (rustdoc: preserve parent doc cfg formacro_exportmacros)c_variadic_experimental_archfeature #155974 (addc_variadic_experimental_archfeature)tests/ui/issues/- 02 #155523 (Reorganizetests/ui/issues/- 02)CloneandDropinstances and requireVaArgSafe: Copy#155821 (c-variadic: documentCloneandDropinstances and requireVaArgSafe: Copy)feature*methods fromparsemod toerrorsmod. #155980 (Movefeature*methods fromparsemod toerrorsmod.)Diagnosticdirectly inSharedContext::emit_lint#156002 (Allow to useDiagnosticdirectly inSharedContext::emit_lint)r? @ghost
Create a similar rollup