Uninitialized bytes get copied to the buffer when creating an uninitialized tuple

[MSxDOS]

In this example:

use std::mem::MaybeUninit;

extern {
    fn fill(p: *mut u16);
}

pub unsafe fn test() {
    let (mut buffer, mut buffer2): ([u16; 512], [u16; 256]) = MaybeUninit::uninit().assume_init();
    fill(buffer.as_mut_ptr());
    fill(buffer2.as_mut_ptr())
}

there is a call to memcpy for one of the buffers that copies uninitialized data to it.
https://rust.godbolt.org/z/z1zcor

[MSxDOS]

cc @nikic

This started after #82806 was merged.

Also, this is a regression from stable to nightly.

[nikic]

Upstream fix: llvm/llvm-project@5556660

[pietroalbini]

This slipped up to stable 1.52.0, apparently we didn't label it regression-from-stable-to-beta losing track of it :/

[nikic]

@pietroalbini We don't plan to address this prior to the next LLVM upgrade anyway. It's just an optimization issue.

[apiraino]

Assigning priority as discussed in the Zulip thread of the Prioritization Working Group.

@rustbot label -I-prioritize +P-high +T-compiler