From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Alex Coplan <Alex.Coplan@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 2/2] aarch64: Add support for Cortex-R82
Date: Wed, 9 Sep 2020 10:29:09 +0000 [thread overview]
Message-ID: <DB7PR08MB3002B56074CE2F1E04B1836493260@DB7PR08MB3002.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200909101527.6alfmstq365bxqqh@arm.com>
> -----Original Message-----
> From: Alex Coplan <Alex.Coplan@arm.com>
> Sent: 09 September 2020 11:15
> 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 2/2] aarch64: Add support for Cortex-R82
>
> This patch adds support for Arm's Cortex-R82 CPU to GCC. For more
> information about this CPU, see [0].
>
> Testing:
> * Bootstrapped and regtested on aarch64-none-linux-gnu, no regressions.
>
> [0] : https://developer.arm.com/ip-products/processors/cortex-r/cortex-r82
>
> OK for trunk?
Ok.
Thanks,
Kyrill
>
> ---
>
> gcc/ChangeLog:
>
> * config/aarch64/aarch64-cores.def: Add Cortex-R82.
> * config/aarch64/aarch64-tune.md: Regenerate.
> * doc/invoke.texi: Add entry for Cortex-R82.
>
> ---
> gcc/config/aarch64/aarch64-cores.def | 3 +++
> gcc/config/aarch64/aarch64-tune.md | 2 +-
> gcc/doc/invoke.texi | 4 ++--
> 3 files changed, 6 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2020-09-09 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 10:15 Alex Coplan
2020-09-09 10:29 ` Kyrylo Tkachov [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=DB7PR08MB3002B56074CE2F1E04B1836493260@DB7PR08MB3002.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Alex.Coplan@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).