https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89104
--- Comment #5 from Wilco <wilco at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #4) > I really don't like these aarch64 warnings, declare simd is an optimization > (admittedly with ABI consequences) and warning about this by default is > weird, > + it is going to be a pain, any time any declare simd testcase is added > there is potential "regression" on aarch64. > Plus it really looks like a bug in this case, there is no mixed type at all, > the int * argument is uniform, so should be passed as any other pointer, and > all the others are int and so should use the same vector int type. I agree backend specific warnings are not ideal but it's unclear whether a better solution exists beyond just not emitting these warnings at all and letting the user figure it out. However the key question is why do testcases which do not specifically test for a specific warning fail if an extra warning is emitted? That's completely harmless in most cases.
