<saurabh....@arm.com> writes: > Earlier, we were gating SVE2 faminmax behind sve+faminmax. This was > incorrect and this patch changes it so that it is gated behind > sve2+faminmax. > > gcc/ChangeLog: > > * config/aarch64/aarch64-sve2.md: > (*aarch64_pred_faminmax_fused): Fix to use the correct flags. > * config/aarch64/aarch64.h > (TARGET_SVE_FAMINMAX): Remove. > * config/aarch64/iterators.md: Fix iterators so that famax and > famin use correct flags. > > gcc/testsuite/ChangeLog: > > * gcc.target/aarch64/sve/faminmax_1.c: Fix test to use the > correct flags. > * gcc.target/aarch64/sve/faminmax_2.c: Fix test to use the > correct flags. > * gcc.target/aarch64/sve/faminmax_3.c: New test.
OK, thanks. (The intrinsics are already correctly guarded.) Richard > > --- > Hey, > > This patch is in response to Andrew's review here: > https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672934.html. > > Regression tested on aarch64-none-linux-gnu and found no > regressions. > > Ok for master? > > Thanks, > Saurabh > --- > gcc/config/aarch64/aarch64-sve2.md | 2 +- > gcc/config/aarch64/aarch64.h | 1 - > gcc/config/aarch64/iterators.md | 8 ++++---- > gcc/testsuite/gcc.target/aarch64/sve/faminmax_1.c | 2 +- > gcc/testsuite/gcc.target/aarch64/sve/faminmax_2.c | 2 +- > gcc/testsuite/gcc.target/aarch64/sve/faminmax_3.c | 11 +++++++++++ > 6 files changed, 18 insertions(+), 8 deletions(-) > create mode 100644 gcc/testsuite/gcc.target/aarch64/sve/faminmax_3.c
