https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112698
--- Comment #5 from Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> --- OK, I can follow that reasoning. It's still a breaking change for everyone that was using int up to this point. I guess the argument is that using int was wrong in the first place and it just happened to work by chance. The right type to use would have been int32_t instead of int. However, if I use int32_t for interacting with NEON intrinsics, will this work everywhere (older GCC, Clang, etc.)? Or is the only portable solution decltype(int32x2t()[0])?
