From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Richard Ball <richard.ball@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <richard.earnshaw@arm.com>,
Richard Sandiford <richard.sandiford@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>
Subject: Re: [PATCH][GCC] aarch64: Fix SCHEDULER_IDENT for Cortex-A520
Date: Wed, 13 Mar 2024 11:34:58 +0000 [thread overview]
Message-ID: <2f7432d2-e17c-4b0d-9e8a-5c9a0338a299@foss.arm.com> (raw)
In-Reply-To: <f9928601-7d52-4489-bb65-c9b85f434829@arm.com>
On 12/03/2024 14:08, Richard Ball wrote:
> The SCHEDULER_IDENT for this CPU was incorrectly
> set to cortexa55, which is incorrect. This can cause
> sub-optimal asm to be generated.
>
> Ok for trunk?
>
> gcc/ChangeLog:
> PR target/114272
> * config/aarch64/aarch64-cores.def (AARCH64_CORE):
> Change SCHEDULER_IDENT from cortexa55 to cortexa53
> for Cortex-A520.
I don't see having this as a separate patch to the one for Cortex-A510
as having any value.
Please merge the two together. A merged patch is pre-approved.
R.
prev parent reply other threads:[~2024-03-13 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 14:08 Richard Ball
2024-03-13 11:34 ` Richard Earnshaw [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=2f7432d2-e17c-4b0d-9e8a-5c9a0338a299@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marcus.shawcroft@arm.com \
--cc=richard.ball@arm.com \
--cc=richard.earnshaw@arm.com \
--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).