Skip to contentSkip to conversation

gcc-runtime: Avoid march conflicts with newer cortex-a55 CPUs

PATCH New Khem Raj 1 participant 1 message May 5, 2020

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH v2 2/2 gcc-runtime: Avoid march conflicts with newer cortex-a55 CPUs

gcc-runtime/libatomic explicitly add -march=armv8-a+lse for all arch64 but cortex-a55 is armv8.2-a, which essentially conflicts, so let gcc override it by not forcing the -mcpu option from TUNE_CCARGS

---
v2: Fix typo and mising -mcpu before cortex-a55

 meta/recipes-devtools/gcc/gcc-runtime.inc | 4 ++++
 1 file changed, 4 insertions(+)
meta/recipes-devtools/gcc/gcc-runtime.inc +4 -0
index ace706dbf4..d9a4e483cc 100644
@@ -18,6 +18,10 @@ EXTRA_OECONF_append_linuxstdbase = " --enable-clocale=gnu"
 EXTRA_OECONF_append = " --cache-file=${B}/config.cache"
 EXTRA_OECONF_append_libc-newlib = " --with-newlib"
 
+# cortex-a55 is ARMv8.2-a based but libatomic explicitly asks for -march=armv8.1-a
+# which caused -march conflicts in gcc
+TUNE_CCARGS_remove = "-mcpu=cortex-a55+crc -mcpu=cortex-a55 -mcpu=cortex-a55+crc+crypto"
+
 # Disable ifuncs for libatomic on arm conflicts -march/-mcpu
 EXTRA_OECONF_append_arm = " libat_cv_have_ifunc=no "
 EXTRA_OECONF_append_armeb = " libat_cv_have_ifunc=no "
Signature · 1 line
2.26.2