https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115713
--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <li...@gcc.gnu.org>: https://gcc.gnu.org/g:04da747a063850333b062e48d0531debe314dff9 commit r15-2214-g04da747a063850333b062e48d0531debe314dff9 Author: Kewen Lin <li...@linux.ibm.com> Date: Tue Jul 23 00:47:49 2024 -0500 rs6000: Escalate warning to error for VSX with explicit no-altivec etc. As the discussion in PR115688, for now when users specify -mvsx and -mno-altivec explicitly, compiler emits warning rather than error, but considering both options are given explicitly, emitting hard error should be better. So this patch is to escalate some related warning to error when both are incompatible. PR target/115713 gcc/ChangeLog: * config/rs6000/rs6000.cc (rs6000_option_override_internal): Emit error messages when explicit VSX encounters explicit soft-float, no-altivec or avoid-indexed-addresses. gcc/testsuite/ChangeLog: * gcc.target/powerpc/warn-1.c: Move to ... * gcc.target/powerpc/error-1.c: ... here. Adjust dg-warning with dg-error and remove ineffective scan.
