diff options
| author | bors <bors@rust-lang.org> | 2024-04-10 16:32:41 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-10 16:32:41 +0000 |
| commit | c2239bca5b89a8d3573cc0fc0f2fa65c50edb79c (patch) | |
| tree | a4a7023541f6318e82116ac328a7850e53357732 /tests/codegen/function-arguments.rs | |
| parent | 5974fe87c4d711949caa64fc1e8366685c8fc190 (diff) | |
| parent | 593e900ad25f1b21cc218ea8bcce3c5e3e94ceac (diff) | |
| download | rust-c2239bca5b89a8d3573cc0fc0f2fa65c50edb79c.tar.gz rust-c2239bca5b89a8d3573cc0fc0f2fa65c50edb79c.zip | |
Auto merge of #123185 - scottmcm:more-typed-copy, r=compiler-errors
Remove my `scalar_copy_backend_type` optimization attempt I added this back in https://github.com/rust-lang/rust/pull/111999 , but I no longer think it's a good idea - It had to get scaled back to only power-of-two things to not break a bunch of targets - LLVM seems to be getting better at memcpy removal anyway - Introducing vector instructions has seemed to sometimes (https://github.com/rust-lang/rust/pull/115515#issuecomment-1750069529) make autovectorization worse So this removes it from the codegen crates entirely, and instead just tries to use <https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_ssa/traits/builder/trait.BuilderMethods.html#method.typed_place_copy> instead of direct `memcpy` so things will still use load/store when a type isn't `OperandValue::Ref`.
Diffstat (limited to 'tests/codegen/function-arguments.rs')
0 files changed, 0 insertions, 0 deletions