public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
	Richard Sandiford <Richard.Sandiford@arm.com>,
	Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: RE: [PATCH][GCC] aarch64: enable cortex-a510 CPU
Date: Fri, 1 Oct 2021 21:47:34 +0000	[thread overview]
Message-ID: <PAXPR08MB66212429F2AB78578C991A47E4AB9@PAXPR08MB6621.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PAXPR08MB692685FEAD138C68C0FD544A93AB9@PAXPR08MB6926.eurprd08.prod.outlook.com>

> Hi Przemek,
> 
> > -----Original Message-----
> > From: Przemyslaw Wirkus <Przemyslaw.Wirkus@arm.com>
> > Sent: Wednesday, September 22, 2021 9:35 AM
> > To: gcc-patches@gcc.gnu.org
> > Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>; Richard Sandiford
> > <Richard.Sandiford@arm.com>; Marcus Shawcroft
> > <Marcus.Shawcroft@arm.com>; Kyrylo Tkachov
> <Kyrylo.Tkachov@arm.com>
> > Subject: [PATCH][GCC] aarch64: enable cortex-a510 CPU
> >
> > Patch is adding 'cortex-a510' to -mcpu command line option.
> >
> > gcc/ChangeLog:
> >
> > 2021-09-02  Przemyslaw Wirkus  <przemyslaw.wirkus@arm.com>
> >
> > 	* config/aarch64/aarch64-cores.def (AARCH64_CORE): New
> > 	Cortex-A510 core.
> > 	* config/aarch64/aarch64-tune.md: Regenerate.
> > 	* doc/invoke.texi: Update docs.
> 
> +/* Arm9.0-A Architecture Processors.  */
> 
> Typo, should be "Armv9.0-a".
> 
> +
> +/* Arm ('A') cores. */
> +AARCH64_CORE("cortex-a510",  cortexa510, cortexa55, 9A,
> +AARCH64_FL_FOR_ARCH9 | AARCH64_FL_SVE2_BITPERM |
> AARCH64_FL_MEMTAG |
> +AARCH64_FL_I8MM | AARCH64_FL_BF16, neoversen2, 0x41, 0xd46, -1)
> +
> 
> We'll need to update the tuning anyway once we do it properly, but for now I
> think for the COSTS field (4th to last) we should go with cortexa53 rather
> than neoversen2.
> Ok with those changes.

commit 8aa3ab5a47664023d83ea5097a53a66bd6cbb978

> Thanks,
> Kyrill

      reply	other threads:[~2021-10-01 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  8:35 Przemyslaw Wirkus
2021-10-01 11:26 ` Kyrylo Tkachov
2021-10-01 21:47   ` Przemyslaw Wirkus [this message]

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=PAXPR08MB66212429F2AB78578C991A47E4AB9@PAXPR08MB6621.eurprd08.prod.outlook.com \
    --to=przemyslaw.wirkus@arm.com \
    --cc=Kyrylo.Tkachov@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).