diff options
| author | bors <bors@rust-lang.org> | 2025-07-28 11:53:15 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-07-28 11:53:15 +0000 |
| commit | 9ba00e0f9e00990fb88c1beac7172afe93b15609 (patch) | |
| tree | e2419f6bd8c111aa221b653c314c7193bdb9bffc /.editorconfig | |
| parent | 65b6cdb6a6d33987b9d642a4882283c71fbe3957 (diff) | |
| parent | 47bfa846f37cf053471656b572a35d2bfca16715 (diff) | |
| download | rust-9ba00e0f9e00990fb88c1beac7172afe93b15609.tar.gz rust-9ba00e0f9e00990fb88c1beac7172afe93b15609.zip | |
Auto merge of #144543 - scottmcm:more-sroa, r=cjgillot
Allow more MIR SROA This removes some guards on SROA that are no longer needed: - With https://github.com/rust-lang/compiler-team/issues/838 it no longer needs to check for SIMD - With https://github.com/rust-lang/compiler-team/issues/807 it no longer needs to check for niches - This means that `Wrapper(char)` and `Pin<&mut T>` can get SRoA'd now, where previously they weren't because the check was banning SRaA for anything with a niche -- not just things with `#[rustc_layout_scalar_valid_range_*]`. - Technically rust-lang/rust#133652 isn't complete yet, but `NonZero` and `NonNull` have already moved over, so this is fine. At worst this will mean that LLVM gets less `!range` metadata on something that wasn't already fixed by rust-lang/rust#133651 or rust-lang/rust#135236, but that's still sound, and unblocking general SRoA is worth that tradeoff.
Diffstat (limited to '.editorconfig')
0 files changed, 0 insertions, 0 deletions