From: Zhangshaokun <zhangshaokun@hisilicon.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"kyrylo.tkachov@foss.arm.com" <kyrylo.tkachov@foss.arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
"zbo.zhou@hisilicon.com" <zbo.zhou@hisilicon.com>, <nd@arm.com>
Subject: Re: [PATCH v4] [aarch64] Add HiSilicon tsv110 CPU support
Date: Thu, 20 Sep 2018 15:13:00 -0000 [thread overview]
Message-ID: <80f8c297-5e5e-c760-90e7-5ea2ec84634f@hisilicon.com> (raw)
In-Reply-To: <20180920142235.GA31720@arm.com>
Hi James,
On 2018/9/20 22:22, James Greenhalgh wrote:
> On Wed, Sep 19, 2018 at 04:53:52AM -0500, Shaokun Zhang wrote:
>> This patch adds HiSilicon's an mcpu: tsv110, which supports v8_4A.
>> It has been tested on aarch64 and no regressions from this patch.
>
> This patch is OK for Trunk.
>
> Do you need someone to commit it on your behalf?
>
Sure, it is great.
Thanks in advance,
Shaokun
> Thanks,
> James
>
>>
>> ---
>> gcc/ChangeLog | 9 +++
>> gcc/config/aarch64/aarch64-cores.def | 3 +
>> gcc/config/aarch64/aarch64-cost-tables.h | 104 +++++++++++++++++++++++++++++++
>> gcc/config/aarch64/aarch64-tune.md | 2 +-
>> gcc/config/aarch64/aarch64.c | 82 ++++++++++++++++++++++++
>> gcc/doc/invoke.texi | 2 +-
>> 6 files changed, 200 insertions(+), 2 deletions(-)
>>
>> diff --git a/gcc/ChangeLog b/gcc/ChangeLog
>> index 69e2e14..a040daa 100644
>> --- a/gcc/ChangeLog
>> +++ b/gcc/ChangeLog
>> @@ -1,3 +1,12 @@
>> +2018-09-19 Shaokun Zhang <zhangshaokun@hisilicon.com>
>> + Bo Zhou <zbo.zhou@hisilicon.com>
>> +
>> + * config/aarch64/aarch64-cores.def (tsv110): New CPU.
>> + * config/aarch64/aarch64-tune.md: Regenerated.
>> + * doc/invoke.texi (AArch64 Options/-mtune): Add "tsv110".
>> + * config/aarch64/aarch64.c (tsv110_tunings): New tuning table.
>> + * config/aarch64/aarch64-cost-tables.h: Add "tsv110" extra costs.
>> +
>> 2018-09-18 Marek Polacek <polacek@redhat.com>
>>
>> P1064R0 - Allowing Virtual Function Calls in Constant Expressions
>
>
> .
>
next prev parent reply other threads:[~2018-09-20 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 10:41 Shaokun Zhang
2018-09-20 14:25 ` James Greenhalgh
2018-09-20 15:13 ` Zhangshaokun [this message]
2018-09-21 13:48 ` Kyrill Tkachov
2018-09-22 7:14 ` Zhangshaokun
2018-09-25 13:44 ` Zhangshaokun
2018-09-26 12:05 ` Kyrill Tkachov
2018-09-27 2:04 ` Zhangshaokun
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=80f8c297-5e5e-c760-90e7-5ea2ec84634f@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=nd@arm.com \
--cc=zbo.zhou@hisilicon.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).