https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89104
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Wilco from comment #5) > 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. I'd say it belongs to -fopt-info or similar stuff, when one wants to investigate why something isn't vectorized etc. > 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. That is the standard behavior of most of the testsuites (except for gcc.c-torture/* which uses -w), and it is a good idea to FAIL for unexpected warnings.
