Hi Richard > -----Original Message----- > From: Richard Sandiford <richard.sandif...@arm.com> > Sent: Friday, January 8, 2021 7:04 PM > To: Qian, Jianhua/钱 建华 <qia...@cn.fujitsu.com> > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH v2] aarch64: Add cpu cost tables for A64FX > > Qian Jianhua <qia...@cn.fujitsu.com> writes: > > This patch add cost tables for A64FX. > > > > ChangeLog: > > 2021-01-08 Qian jianhua <qia...@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 >
