Rollup of 14 pull requests#159814
Conversation
* Enable autodiff tests on x86_64 linux * move autodiff job def * remove redundant ./x build
Replace most of the `.span_suggestion(` in `rustc_parse` with `.span_suggestion_verbose(`, as they are more readabale, if more verbose. Verbose suggestions also tend to highlight off-by-one `Span` errors better.
This commit is in preparation for eventual [tier 2 status] for the `wasm32-wasip3` target. Initially this target will not have support for threads but it's expected to come ~later this year. The first step in supporting this is switching internal `#[cfg]` in the standard library to "ok this target has threads", and this commit is the update for synchronization primitives. All synchronization primitives on the `wasm32-wasip3` now use a `futex`-based implementation, and the implementation of the futex itself is located in wasi-libc (see WebAssembly/wasi-libc/834). Other WASI targets can eventually all use this implementation as well, but `wasi-libc`'s implementation of these symbols will need to percolate, so those targets aren't changed yet. For `wasm32-wasip3`, however, any supporting `wasi-libc` will have these symbols. This then additionally fixes the target to actually build with a modern LLVM by passing a necessary flag to `wasm-ld`. This flag isn't supported until LLVM 23, but the `wasm32-wasip3` target isn't fully supported until LLVM 23 anyway (hence its Tier 3 status currently). [tier 2 status]: rust-lang/compiler-team#1001
… `automatically_derived` attribute
also add regression test for rmeta reproducibility when unrelated `rlib` are in the search path Co-authored-by: mejrs <59372212+mejrs@users.noreply.github.com>
Implements MCP 982 via issue 156191
…adata The recent Cargo submodule update picked up <rust-lang/cargo#17149> However, bootstrap was still using the old name, resulting in: ``` Building stage1 library artifacts (stage1 -> stage1, arm64ec-pc-windows-msvc) error: unknown `-Z` flag specified: no-embed-metadata ``` Fix is to switch to the rename. I also removed the diff in the Cranelift setup script, since they must have already hit this issue and no longer need the workaround.
These changes involve the error messages produced in `check_attribute_stability`, plus some related ones. The basic idea: - Use "the `foo` attribute" in `error` lines as much as possible, where `foo` is the attribute's path. - Point carets at just the attribute's path, to match the `error` line.
Mostly in a fashion similar to the previous commit. There is one exceptional case: for errors involving `repr` the argument is significant. For these, the argument is included in the error line and the caret highlighting, e.g. ``` error: the `repr(C)` attribute cannot be used on functions --> $DIR/naked-with-invalid-repr-attr.rs:10:3 | LL | #[repr(C)] | ^^^^^^^ | = help: the `repr(C)` attribute can only be applied to data types ``` Contrast this with a more typical argument-excluding case used everywhere else: ``` error: the `rustc_abi` attribute cannot be used on associated consts --> $DIR/debug.rs:46:7 | LL | #[rustc_abi(debug)] | ^^^^^^^^^ | = help: the `rustc_abi` attribute can be applied to functions and type aliases ```
This comment has been minimized.
This comment has been minimized.
Rollup of 14 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-*
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 1498f99 (parent) -> 29e68fe (this PR) Test differencesShow 353 test diffsStage 1
Stage 2
Additionally, 330 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 29e68fe2295f8fc2feb52b8cb0b61a055842fdcf --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: 1498f9968f In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (29e68fe): 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 (secondary -2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 486.272s -> 488.104s (0.38%) |
Successful merges:
cfg_select!#158372 (rustfmt: Discover modules viacfg_select!)DocLinkResMapanFxIndexMap#159718 (MakeDocLinkResMapanFxIndexMap)cfg_attrinformation for derived impls fordoc_cfgfeature #159722 ( [rustdoc] Retrievecfg_attrinformation for derived impls fordoc_cfgfeature)vec![1, 2, 3]macro #155795 (constifyvec![1, 2, 3]macro)r? @ghost
Create a similar rollup