diff options
| author | bors <bors@rust-lang.org> | 2025-07-09 16:37:20 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-07-09 16:37:20 +0000 |
| commit | e3fccdd4a16bf3aa223749efef1fa981589e43ae (patch) | |
| tree | 33e44cdf5f8ea4a7f750381c695dd4c3e3e39df6 /tests/ui/async-await/issues/issue-54752-async-block.rs | |
| parent | 6b3ae3f6e45a33c2d95fa0362c9b2593e567fd34 (diff) | |
| parent | 8cf2c71243f8c093e7728370e6653aa940dbaf22 (diff) | |
| download | rust-e3fccdd4a16bf3aa223749efef1fa981589e43ae.tar.gz rust-e3fccdd4a16bf3aa223749efef1fa981589e43ae.zip | |
Auto merge of #143502 - scottmcm:aggregate-simd, r=oli-obk
Let `rvalue_creates_operand` return true for *all* `Rvalue::Aggregate`s ~~Draft for now because it's built on Ralf's rust-lang/rust#143291~~ Inspired by https://github.com/rust-lang/rust/pull/138759#discussion_r2156375342 where I noticed that we were nearly at this point, plus the comments I was writing in rust-lang/rust#143410 that reminded me a type-dependent `true` is fine. This PR splits the `OperandRef::builder` logic out to a separate type, with the updates needed to handle SIMD as well. In doing so, that makes the existing `Aggregate` path in `codegen_rvalue_operand` capable of handing SIMD values just fine. As a result, we no longer need to do layout calculations for aggregate result types when running the analysis to determine which things can be SSA in codegen.
Diffstat (limited to 'tests/ui/async-await/issues/issue-54752-async-block.rs')
0 files changed, 0 insertions, 0 deletions