From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Chung-Ju Wu <jasonwucj@gmail.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Jason.Wu@anshingtek.com.tw" <Jason.Wu@anshingtek.com.tw>
Subject: RE: [PATCH 1/3][ARM] STAR-MC1 CPU Support - arm: Add star-mc1 core
Date: Mon, 6 Jun 2022 14:10:06 +0000 [thread overview]
Message-ID: <PAXPR08MB6926EDFB0519CA5EDE449CD793A29@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <70e4f5ae-e59a-d0ba-68b9-72d27de09c44@gmail.com>
Hi jasonwucj,
> -----Original Message-----
> From: Gcc-patches <gcc-patches-
> bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On Behalf Of Chung-Ju Wu
> via Gcc-patches
> Sent: Thursday, May 26, 2022 8:18 AM
> To: Richard Earnshaw <Richard.Earnshaw@arm.com>; gcc-patches <gcc-
> patches@gcc.gnu.org>
> Cc: Jason.Wu@anshingtek.com.tw
> Subject: [PATCH 1/3][ARM] STAR-MC1 CPU Support - arm: Add star-mc1 core
>
> Hi,
>
> STAR-MC1 is an embedded processor with armv8m architecture. Majorly it
> is designed to meet the requirements of AIoT application performance,
> power consumption and security. Early this month, star-mc1 is supported by
> the latest releases of MDK and CMSIS. For the completeness of Arm
> ecosystem,
> it would be great if we can have star-mc1 support in official GCC as well.
>
> Attached is the patch to support star-mc1 cpu in GCC:
>
> * Fundamental of -mcpu=star-mc1 option
> - Based on latest upstream commit:
> https://gcc.gnu.org/g:3dff965cae6709a5fd1b7b05c51c3c8aba786961
> - Add star-mc1 cpu in arm-cpus.in and regenerate necessary
> implementation
>
> * Include VLLDM bugfix
> - CVE-2021-35465 also affects star-mc1 configuration [1]
> - We apply quirk_vlldm strategy for star-mc1 cpu
>
> Successfully bootstrapped and tested on arm-none-eabi.
>
> Is it OK for trunk?
This is okay (together with the documentation additions in 3/3)
Thanks for the patch,
Kyrill
>
> [1] https://www.cve.org/CVERecord?id=CVE-2021-35465
>
> Regards,
> jasonwucj
next prev parent reply other threads:[~2022-06-06 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 7:17 Chung-Ju Wu
2022-06-06 14:10 ` Kyrylo Tkachov [this message]
2022-06-08 8:34 ` Chung-Ju Wu
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=PAXPR08MB6926EDFB0519CA5EDE449CD793A29@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Jason.Wu@anshingtek.com.tw \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jasonwucj@gmail.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).