================
@@ -334,8 +334,8 @@ ARM_CPU_NAME("cortex-r7", ARMV7R, FK_VFPV3_D16_FP16, false,
(ARM::AEK_MP | ARM::AEK_HWDIVARM))
ARM_CPU_NAME("cortex-r8", ARMV7R, FK_VFPV3_D16_FP16, false,
(ARM::AEK_MP | ARM::AEK_HWDIVARM))
-ARM_CPU_NAME("cortex-r52", ARMV8R, FK_NEON_FP_ARMV8, false, ARM::AEK_NONE)
-ARM_CPU_NAME("cortex-r52plus", ARMV8R, FK_NEON_FP_ARMV8, false, ARM::AEK_NONE)
+ARM_CPU_NAME("cortex-r52", ARMV8R, FK_NEON_FP_ARMV8, false, ARM::AEK_SIMD)
+ARM_CPU_NAME("cortex-r52plus", ARMV8R, FK_NEON_FP_ARMV8, false, ARM::AEK_SIMD)
----------------
Stylie777 wrote:
We support NEON on Cortex-R52 by default, rather than as an optional feature.
When `+simd`/`+nosimd` was linked to `+neon` and `-neon`, I found that once the
link between `simd` and `neon` was made, it was not passing `-target-feature
+neon` as part of the cc1 command.
Let me investigate and see if we need this change or if it can determine
`+neon` from the FPU, if not we may need to add `AEK_SIMD` to everything that
should support it as it may not just be cortex-r52 that is affected here.
https://github.com/llvm/llvm-project/pull/130623
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
