From: "Qian, Jianhua" <qianjh@cn.fujitsu.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH v2] aarch64: Add cpu cost tables for A64FX
Date: Mon, 11 Jan 2021 04:36:17 +0000 [thread overview]
Message-ID: <b358b2ccf71c493081ec8168de31b0d7@G08CNEXMBPEKD06.g08.fujitsu.local> (raw)
In-Reply-To: <mpth7nrelm3.fsf@arm.com>
Hi Richard
> -----Original Message-----
> From: Richard Sandiford <richard.sandiford@arm.com>
> Sent: Friday, January 8, 2021 7:04 PM
> To: Qian, Jianhua/钱 建华 <qianjh@cn.fujitsu.com>
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH v2] aarch64: Add cpu cost tables for A64FX
>
> Qian Jianhua <qianjh@cn.fujitsu.com> writes:
> > This patch add cost tables for A64FX.
> >
> > ChangeLog:
> > 2021-01-08 Qian jianhua <qianjh@cn.fujitsu.com>
> >
> > gcc/
> > * config/aarch64/aarch64-cost-tables.h (a64fx_extra_costs): New.
> > * config/aarch64/aarch64.c (a64fx_addrcost_table): New.
> > (a64fx_regmove_cost, a64fx_vector_cost): New.
> > (a64fx_tunings): Use the new added cost tables.
>
> OK for trunk, thanks. The v1 patch is OK for branches that support
> -mcpu=a64fx.
>
> Would you like commit access, so that you can commit it yourself?
> If so, please fill out the form mentioned at the beginning of
> https://gcc.gnu.org/gitwrite.html listing me as sponsor.
>
It‘s my pleasure. I've applied it.
Thank you so much.
I don't quite know the process of gcc source committing.
If I have the commit access, how will process be different?
And which branch, which range(aarch64?) could I commit patches to?
Regards,
Qian
> Alternatively, if you'd rather not for any reason, I'm happy to apply it for you.
>
> Thanks,
> Richard
>
next prev parent reply other threads:[~2021-01-11 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:53 Qian Jianhua
2021-01-08 11:03 ` Richard Sandiford
2021-01-11 4:36 ` Qian, Jianhua [this message]
2021-01-11 12:17 ` Richard Sandiford
2021-01-12 8:01 ` Qian, Jianhua
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=b358b2ccf71c493081ec8168de31b0d7@G08CNEXMBPEKD06.g08.fujitsu.local \
--to=qianjh@cn.fujitsu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).