https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106833
--- Comment #9 from Segher Boessenkool <segher at gcc dot gnu.org> --- Although, preferably we should not allow assigning one opaque type to another opaque type just because they will eventually use the same mode, not without warning anyway? Or is that unavoidable? Compare assigning a V4SI to a V4SF. I don't know if your patch does this, btw, and it isn't so easy to test, we currently have only one type for each of our opaque modes. Maybe test by adding an extra builtin type :-)
