rikaken2004 opened a new pull request, #20402: URL: https://github.com/apache/nuttx/pull/20402
## Summary Every `ARCH_CORTEX_A5x` config selects `ARCH_ARMV8A` (arch/arm64/Kconfig), and both `arch/arm64/src/Toolchain.defs` and `arch/arm64/src/cmake/Toolchain.cmake` test `CONFIG_ARCH_ARMV8A` at the head of the chain — so the `-mcpu=cortex-a53/a55/a57/a72` branches were unreachable, and every Cortex-A target built with plain `-march=armv8-a`, losing per-core scheduling/tuning. Reported as #20400. This PR tests the specific cores first so `-mcpu` actually wins, while the generic `ARCH_ARMV8A` branch (with its armv8.5-a/MTE handling) still covers cores without a dedicated entry. The `ARCH_ARMV8R`/`cortex-r82` ordering is left untouched on purpose: `-mcpu=cortex-r82` would imply an FPU for `nofp` configurations, whereas the Cortex-A `-mcpu` values are safe supersets of `-march=armv8-a` here. Also adds the missing `cortex-a55` branch to the cmake toolchain for parity with the makefile. ## Impact Cortex-A53/A55/A57/A72 targets now compile with per-core tuning (`-mcpu=...`) in both make and cmake builds. No change for other arch variants or for targets already covered by the generic branch. ## Testing Verified the condition ordering against the `select` chains in arch/arm64/Kconfig; flag change only, no runtime behaviour change beyond compiler scheduling/tuning. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
