Report UB instead of ICEing when SIMD operands have incompatible size about miri HOT 6 CLOSED

This now prints

warning: the feature `link_llvm_intrinsics` is internal to the compiler or standard library
 --> src/main.rs:1:12
  |
1 | #![feature(link_llvm_intrinsics, simd_ffi)]
  |            ^^^^^^^^^^^^^^^^^^^^
  |
  = note: using it is strongly discouraged
  = note: using it is strongly discouraged
  = note: `#[warn(internal_features)]` on by default

FWIW with a regular rustc build it doesn't even ICE, it hits an LLVM assertion. So I don't think there is anything else we want to do in the Miri side here.

rust-lang/rust#116217 tracks the ICE message.

from miri.

We generally ICE when intrinsics are used the wrong way. I don't think we should make an exception for SIMD intrinsics.

link_llvm_intrinsics sounds like a feature on par with feature(intrinsics): if you use it wrong, don't expect the compiler to give nice error messages.

from miri.

Hm. My concern is that we attach this text to an ICE:

error: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/miri/issues/new

Which is not appropriate if the ICE is actually user error.

from miri.

Yeah, that text is wrong when intrinsics are involved (and possibly with other internal features as well), see e.g. this example.

I'm fairly sure it's also possible to ICE rustc by misusing intrinsics, so this is not really a Miri issue.

from miri.

Here's a rustc ICE that's not-a-bug due to being related to intrinsics.

We should clarify the message printed on an ICE (but getting access to enough state to figure out if any internal feature was enabled might be tricky). But that's a rustc issue, not a Miri issue.

from miri.

Thanks! I agree that making this an internal feature is a good improvement.

from miri.