Hi Jim,
On 13/11/15 16:59, Jim Wilson wrote:
On Thu, Nov 12, 2015 at 8:15 AM, Ramana Radhakrishnan
<ramana....@googlemail.com> wrote:
This is OK to go in with a follow up to handle this cpu in t-aprofile
similar to the other cpus in there - for bonus points please deal with
the exynos core at the same time if not already done.
This was tested with a arm-eabi cross compiler build configured
--with-multilib-list=aprofile, and then using
./xgcc -B./ -mcpu=X --print-libgcc
to verify that processor names map to the correct libgcc multilib.
Jim
Index: gcc/config/arm/t-aprofile
===================================================================
--- gcc/config/arm/t-aprofile (revision 230283)
+++ gcc/config/arm/t-aprofile (working copy)
@@ -91,6 +91,8 @@ MULTILIB_MATCHES += march?armv8-a=mcpu?corte
MULTILIB_MATCHES += march?armv8-a=mcpu?cortex-a57.cortex-a53
MULTILIB_MATCHES += march?armv8-a=mcpu?cortex-a72
MULTILIB_MATCHES += march?armv8-a=mcpu?cortex-a72.cortex-a53
+MULTILIB_MATCHES += march?armv8-a=mcpu?exynos-m1
+MULTILIB_MATCHES += march?armv8-a=mcpu?qdf24xx
Sorry to chime in late on this, but while you're at it could
you please add an xgene1 entry?
You can either do it as part of this patch or as a separate
pre-approved patch if you don't want to re-test this one.
This patch is ok if you take the second route.
Thanks,
Kyrill
