rust/tests/codegen/issues, branch try

Describe lifetime of call argument temporaries passed indirectly

2025-05-17T07:49:03+00:00

Rollup merge of #139261 - RalfJung:msvc-align-mitigation, r=oli-obk

2025-04-24T09:40:35+00:00

mitigate MSVC alignment issue on x86-32 This implements mitigation for https://github.com/rust-lang/rust/issues/112480 by stopping to emit `align` attributes on loads and function arguments when building for a win32 MSVC target. MSVC is known to not properly align `u64` and similar types, and claiming to LLVM that everything is properly aligned increases the chance that this will cause problems. Of course, the misalignment is still a bug, but we can't fix that bug, only MSVC can. Also add an errata note to the platform support page warning users about this known problem. try-job: `i686-msvc*`

tests: adjust 101082 test for LLVM 21 fix

2025-04-17T19:11:21+00:00

Fixes #139987.

Auto merge of #139430 - scottmcm:polymorphic-array-into-iter, r=cuviper

2025-04-11T23:21:31+00:00

Polymorphize `array::IntoIter`'s iterator impl Today we emit all the iterator methods for every different array width. That's wasteful since the actual array length never even comes into it -- the indices used are from the separate `alive: IndexRange` field, not even the `N` const param. This PR switches things so that an `array::IntoIter` stores a `PolymorphicIter<[MaybeUninit; N]>`, which we *unsize* to `PolymorphicIter<[MaybeUninit]>` and call methods on that non-`Sized` type for all the iterator methods. That also necessarily makes the layout consistent between the different lengths of arrays, because of the unsizing. Compare that to today , where different widths can't even be deduped because the offset to the indices is different for different array widths.

replace `//@ compile-flags: --edition` with `//@ edition`

2025-04-10T07:56:37+00:00

PR feedback

2025-04-10T04:44:59+00:00

mitigate MSVC unsoundness by not emitting alignment attributes on win32-msvc targets

2025-04-07T21:30:55+00:00

also mention the MSVC alignment issue in platform-support.md

Rollup merge of #139438 - Zalathar:fix-test-122600, r=scottmcm

2025-04-06T06:21:03+00:00

Prevent a test from seeing forbidden numbers in the rustc version The final CHECK-NOT directive in this test was able to see past the end of the enclosing function, and find the substring `753` or `754` in the git hash in the rustc version number, causing false failures in CI whenever the git hash happens to contain those digits in sequence. Adding an explicit check for `ret` prevents the CHECK-NOT directive from seeing past the end of the function. --- Manually tested by adding `// CHECK-NOT: rustc` after the existing CHECK-NOT directives, and demonstrating that the new check prevents it from seeing the rustc version string.

Prevent a test from seeing forbidden numbers in the rustc version

2025-04-06T02:38:20+00:00

The final CHECK-NOT directive in this test was able to see past the end of the enclosing function, and find the substring 753 or 754 in the git hash in the rustc version number, causing false failures in CI. Adding an explicit check for `ret` prevents the CHECK-NOT directive from seeing past the end of the function.

Polymorphize `array::IntoIter`'s iterator impl

2025-04-06T00:55:24+00:00