On 17/02/2026 13:09, Torbjorn SVENSSON wrote: > Hi, > > Can this be picked to releases/gcc-15? > In order for it to apply more cleanly, I would like to also pick > r16-3492-g3cb6c01d2a9ab0 and r16-7262-gf7f2b73b9c1e01. >
OK R. > Kind regards, > Torbjörn > > On 2026-01-29 18:30, Richard Earnshaw wrote: >> Several target-supports checks for Arm are still using the antiquated >> -mfpu=... setting rather than picking up FPU extensions via the >> architecture specification. This causes problems when tests are >> layered because they do not consistently override each other. >> >> Arguably, that is incorrect anyway: you can't test two sets of flag >> combinations independently and then expect to be able to apply both >> of them, but this change at least makes this behave in a reasonable >> way provided the second set of flags fully overrides the first. >> >> gcc/testsuite/ChangeLog: >> >> * lib/target-supports.exp: >> (check_effective_target_arm_v8_3a_complex_neon_ok_nocache): >> Split and fill in arm and aarch64 compile options. Remove the >> cpu_unset variable. >> (check_effective_target_arm_v8_2a_fp16_neon_ok_nocache): Likewise. >> (check_effective_target_arm_v8_3a_fp16_complex_neon_ok_nocache): >> Likewise. >> (check_effective_target_arm_neon_ok_nocache): Rework to use >> -mfpu=auto. >> (check_effective_target_arm_neon_fp16_ok_nocache): Likewise. >>
