https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103627
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Kewen Lin <li...@gcc.gnu.org>: https://gcc.gnu.org/g:2c9485a496f2faa294e7849a1d9c582c015605cc commit r11-9572-g2c9485a496f2faa294e7849a1d9c582c015605cc Author: Kewen Lin <li...@linux.ibm.com> Date: Sun Feb 6 21:30:02 2022 -0600 rs6000: Move the hunk affecting VSX/ALTIVEC ahead [PR103627] The modified hunk can update VSX and ALTIVEC flag, we have some codes to check/warn for some flags related to VSX and ALTIVEC sitting where the hunk is proprosed to be moved to. Without this adjustment, the VSX and ALTIVEC update is too late, it can cause the incompatibility and result in unexpected behaviors, the associated test case is one typical case. Since we already have the code which sets TARGET_FLOAT128_TYPE and lays after the moved place, and OPTION_MASK_FLOAT128_KEYWORD will rely on TARGET_FLOAT128_TYPE, so it just simply remove them. gcc/ChangeLog: PR target/103627 * config/rs6000/rs6000.c (rs6000_option_override_internal): Move the hunk affecting VSX and ALTIVEC to appropriate place. gcc/testsuite/ChangeLog: PR target/103627 * gcc.target/powerpc/pr103627-3.c: New test. (cherry picked from commit e66ba0f55c000152df63fc67c11a64f79122ef86)
