Rollup of 5 pull requests#157863
Conversation
… since the time that was added update existing match tests as well remove hashes from output remove specific DefIds for core from output remove additional specifics that can vary and which are not relevant to the test
…c/diagnostics.rs`
Add xdg_basedir API Implements an API providing easy access to the XDG Base Directories. I chose to defer `runtime_dir` (`XDG_RUNTIME_DIR`) since the lack of a specified default (but specified expectation for applications to determine an alternative option somehow) makes the correct usage (and thus ideal API) less obvious. - Accepted ACP: rust-lang/libs-team#805 - Tracking issue: rust-lang#157515
…3, r=JonathanBrouwer Rename `errors.rs` file to `diagnostics.rs` (6/N) Follow-up of rust-lang#157485. r? @JonathanBrouwer
…rce, r=Nadrieril Match expressions had not been updated to also show the match_source,… … since the time that was added
…-3, r=saethlin Emit retags in codegen to support BorrowSanitizer (part 3) Tracking issue: rust-lang#154760 [Zulip Thread](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Staging.20for.20emitting.20retags.20in.20codegen/with/593004012) This is one of several PRs that will add experimental support for emitting retags as function calls in codegen. This PR adds `RetagPlan`, which describes where the pointers that need to be retagged live within the layout of a type. We create a `RetagPlan` ahead of time because only a subset of the variants of a type might contain retagable values. We only want to branch to these variants, and ignore all of the others. If a type can generate a `RetagPlan`, then we will use it as a guide for inserting calls to our retag intrinsics. If a type does not generate a `RetagPlan`, then it does not need to be retagged, and we can skip it. This does not emit a `RetagPlan::EmitRetag` yet. That will come in a subsequent PR. Previous parts: rust-lang#156208, rust-lang#156210 cc: @RalfJung r? @saethlin
… r=JonathanBrouwer Rename `errors.rs` file to `diagnostics.rs` (7/N) Follow-up of rust-lang#157485. r? @JonathanBrouwer
|
@bors r+ rollup=never p=5 |
This comment has been minimized.
This comment has been minimized.
|
📌 Perf builds for each rolled up PR:
previous master: 8d6b38095e In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
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 8d6b380 (parent) -> e7ef22d (this PR) Test differencesShow 39 test diffsStage 1
Stage 2
Additionally, 36 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 e7ef22d23f10e9e05546592aa9c1e3e8bb288969 --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 |
|
Finished benchmarking commit (e7ef22d): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary -3.5%, secondary -0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -3.9%)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: 517.524s -> 521.088s (0.69%) |
Successful merges:
errors.rsfile todiagnostics.rs(6/N) #157752 (Renameerrors.rsfile todiagnostics.rs(6/N))errors.rsfile todiagnostics.rs(7/N) #157861 (Renameerrors.rsfile todiagnostics.rs(7/N))r? @ghost
Create a similar rollup