rust/tests/codegen/simd, branch master

Rename `tests/codegen` into `tests/codegen-llvm`

2025-07-22T12:28:48+00:00

Ban projecting into SIMD types [MCP838]

2025-07-20T17:22:09+00:00

So many test updates x_x

2025-07-20T17:15:14+00:00

Let `rvalue_creates_operand` return true for all `Rvalue::Aggregate`s

2025-07-08T06:08:10+00:00

Inspired by where I noticed that we were nearly at this point, plus the comments I was writing in 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.

x86 (32/64): go back to passing SIMD vectors by-ptr

2025-06-04T06:38:49+00:00

Fix test simd/extract-insert-dyn on s390x

2025-05-03T08:15:32+00:00

Fix the test for s390x by enabling s390x vector extension via `target_feature(enable = "vector")`(#127506). As this is is still gated by `#![feature(s390x_target_feature)]` we need that attribute also.

enable msa feature for mips in codegen tests

2025-04-29T08:20:25+00:00

wasm, arm, x86-without-SSE need simd to be explicitly enabled

2025-04-23T12:01:08+00:00

Auto merge of #139578 - ferrocene:pa-compiletest-edition, r=jieyouxu

2025-04-11T10:53:45+00:00

Fix breakage when running compiletest with `--test-args=--edition=2015` Compiletest has an `--edition` flag to change the default edition tests are run with. Unfortunately no test suite successfully executes when that flag is passed. If the edition is set to something greater than 2015 the breakage is expected, since the test suite currently supports only edition 2015 (Ferrous Systems will open an MCP about fixing that soonish). Surprisingly, the test suite is also broken if `--edition=2015` is passed to compiletest. This PR focuses on fixing the latter. This PR fixes the two categories of failures happening when `--edition=2015` is passed: * Some edition-specific tests set their edition through `//@ compile-flags` instead of `//@ edition`. Compiletest doesn't parse the compile flags, so it would see no `//@ edition` and add another `--edition` flag, leading to a rustc error. * Compiletest would add the edition after `//@ compile-flags`, while some tests depend on flags passed to `//@ compile-flags` being the last flags in the rustc invocation. Note that for the first category, I opted to manually go and replace all `//@ compile-flags` setting an edition with an explicit `//@ edition`. We could've changed compiletest to instead check whether an edition was set in `//@ compile-flags`, but I thought it was better to enforce a consistent way to set the edition in tests. I also added the edition to the stamp, so that changing `--edition` results in tests being re-executed. r? `@jieyouxu`

Rollup merge of #137447 - folkertdev:simd-extract-insert-dyn, r=scottmcm

2025-04-11T03:31:43+00:00

add `core::intrinsics::simd::{simd_extract_dyn, simd_insert_dyn}` fixes https://github.com/rust-lang/rust/issues/137372 adds `core::intrinsics::simd::{simd_extract_dyn, simd_insert_dyn}`, which contrary to their non-dyn counterparts allow a non-const index. Many platforms (but notably not x86_64 or aarch64) have dedicated instructions for this operation, which stdarch can emit with this change. Future work is to also make the `Index` operation on the `Simd` type emit this operation, but the intrinsic can't be used directly. We'll need some MIR shenanigans for that. r? `@ghost`