From: Jim Wilson <jim.wilson@linaro.org>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [ARM/Aarch64] add initial Qualcomm support
Date: Fri, 13 Nov 2015 16:59:00 -0000 [thread overview]
Message-ID: <CABXYE2Xto9V0oCi6yhpZZh0kjVGNA8B+7CRYZ5dZyLgG-Uho3w@mail.gmail.com> (raw)
In-Reply-To: <CAJA7tRZXNOePGikGfG3qBRMmYOHs6Q7NYGS45U3uNhrk7wdfxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Thu, Nov 12, 2015 at 8:15 AM, Ramana Radhakrishnan
<ramana.gcc@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
[-- Attachment #2: aprofile.patch --]
[-- Type: text/x-patch, Size: 804 bytes --]
2015-11-12 Jim Wilson <jim.wilson@linaro.org>
* gcc/config/arm/t-aprofile (MULTILIB_MATCHES): Add lines for exynos-m1
and qdf24xx to match -march=armv8-a.
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
# Arch Matches
MULTILIB_MATCHES += march?armv8-a=march?armv8-a+crc
next prev parent reply other threads:[~2015-11-13 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 18:34 Jim Wilson
2015-11-11 19:55 ` Jim Wilson
2015-11-12 11:42 ` James Greenhalgh
2015-11-12 16:15 ` Ramana Radhakrishnan
2015-11-13 16:59 ` Jim Wilson [this message]
2015-11-13 17:02 ` Kyrill Tkachov
2015-11-13 17:20 ` Jim Wilson
2015-11-13 17:53 ` Jim Wilson
2015-11-16 9:04 ` Kyrill Tkachov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABXYE2Xto9V0oCi6yhpZZh0kjVGNA8B+7CRYZ5dZyLgG-Uho3w@mail.gmail.com \
--to=jim.wilson@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.gcc@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).