Rollup of 21 pull requests#155979
Conversation
The previously pinned versions of openssl-sys and curl-sys are not compatible with OpenSSL 4.0.x. - `curl-sys`: 0.4.84+curl-8.17.0 -> 0.4.87+curl-8.19.0 - `openssl-sys`: 0.9.111 -> 0.9.114
Wire IsProcessorFeaturePresent for the PF_ARM_* constants exposed in Windows SDK 26100 (Win11 24H2): fp16 PF_ARM_V82_FP16_INSTRUCTIONS_AVAILABLE (67) i8mm PF_ARM_V82_I8MM_INSTRUCTIONS_AVAILABLE (66) bf16 PF_ARM_V86_BF16_INSTRUCTIONS_AVAILABLE (68) sha3 PF_ARM_SHA3 (64) AND PF_ARM_SHA512 (65) lse2 PF_ARM_LSE2_AVAILABLE (62) f32mm PF_ARM_SVE_F32MM_INSTRUCTIONS_AVAILABLE (58) f64mm PF_ARM_SVE_F64MM_INSTRUCTIONS_AVAILABLE (59) Also derive `rdm` from FEAT_DotProd. There is no PF_ARM_RDM_* constant; FEAT_DotProd is an optional v8.2-A feature only present on cores that implement at least v8.1-A, and v8.1-A with AdvSIMD mandates FEAT_RDM (Arm ARM K.a §D17.2.91). AdvSIMD is universal on Windows-on-ARM. See PR description for full rationale and .NET 10 precedent. All eight feature names have been stable in `is_aarch64_feature_detected!` on Linux/Darwin/BSD since Rust 1.60.
…pport Add `stat` and `lstat` shims for all Unixes
…x2var_epi64 Implement `_mm512_permutex2var_epi64` shim
Co-authored-by: bjorn3 <17426603+bjorn3@users.noreply.github.com>
Make FileMetadata track Unix-specific fields as optional data. Advertise STATX_* bits only for metadata that is actually available. Add libc-fs coverage for statx on file paths, file descriptors, and AT_EMPTY_PATH on pipes
…ts, allowing to use `FnOnce` instead of `Fn`
Because the memory safety of `FlatMapInPlace::flat_map_in_place` depends on `FlatMapInPlaceVec` impls behaving correctly.
shims: improve Linux statx
…tcp-proto Allow setting `IPPROTO_TCP` as protocol in `socket` syscall
And use it in `partial_cmp` implementation for visibilities
This PR tries to address rust-lang/unsafe-code-guidelines#584 (comment). It is part of a bachelor thesis supervised by @JoJoDeveloping and @RalfJung, for more information, see: https://github.com/user-attachments/files/26537277/Project_Description.pdf. This implements the checking for implicit writes for Tree Borrows. It is disabled by default but can be enabled using the `-Zmiri-tree-borrows-implicit-writes` flag. When it is enabled, Miri inserts a write for all mutable borrows on function entry. This enables the optimization implemented here: rust-lang#155207
tree borrows: implicit writes
|
@bors r+ rollup=never p=5 Trying commonly failed jobs For debugging help: this rollup consists of: 12 PRs which already passed full CI (but github did a github): Rollup of 12 pull requests #155964 |
This comment has been minimized.
This comment has been minimized.
Rollup of 21 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 c935696 (parent) -> a021a77 (this PR) Test differencesShow 79 test diffsStage 1
Stage 2
Additionally, 62 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 a021a7796f66600f46013d6c8d1dfc9e8d7f4a92 --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: c935696dd0 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
|
Finished benchmarking commit (a021a77): comparison URL. Overall result: ❌✅ regressions and improvements - 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 -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis perf run didn't have relevant results for this metric. Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 487.214s -> 480.95s (-1.29%) |
Successful merges:
ambiguous_import_visibilitiesdeprecation lint to glob-vs-glob ambiguities #154149 (resolve: Extendambiguous_import_visibilitiesdeprecation lint to glob-vs-glob ambiguities)GenericTypeVisitable, and avoid having interner traits forFnSigKindandAbi#155562 (Add a missingGenericTypeVisitable, and avoid having interner traits forFnSigKindandAbi)partial_cmpoperation forDefIds #155608 (rustc_middle: Implement thepartial_cmpoperation forDefIds)[const] Traitbounds in more places #155861 (Suggest[const] Traitbounds in more places)dlltool: Set the working directory to workaround--temp-prefixbug #155899 (dlltool: Set the working directory to workaround--temp-prefixbug)wasm32-wali-linux-musltarget #155916 (Update with new LLVM 22 target forwasm32-wali-linux-musltarget)//@ needs-asm-mnemonic: retmore #155950 (use the new//@ needs-asm-mnemonic: retmore)AcceptContext::expect_key_value#155831 (AddAcceptContext::expect_key_value)Fncallees #155877 (Avoid misleading return-type note for foreignFncallees)opt_ast_lowering_delayed_lintsquery to allow "stealing" lints, allowing to useFnOnceinstead ofFn#155949 (Updateopt_ast_lowering_delayed_lintsquery to allow "stealing" lints, allowing to useFnOnceinstead ofFn)FlatMapInPlaceVecan unsafe trait. #155951 (MakeFlatMapInPlaceVecan unsafe trait.)doc_cfgfeature for extern items #155967 (Fixdoc_cfgfeature for extern items)r? @ghost
Create a similar rollup