public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Ball <Richard.Ball@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][GCC] aarch64: Fix SCHEDULER_IDENT for Cortex-A510
Date: Thu, 25 Apr 2024 14:59:28 +0000	[thread overview]
Message-ID: <DB9PR08MB6957EC19E77A9257BF33E2DB81172@DB9PR08MB6957.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <a04da397-59b1-4425-a07e-3a4298dd1e50@arm.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

Hi Richard,

I committed this combined patch (with Cortex-A520) for trunk https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=cab53aae43cf94171b01320c08302e47a5daa391

Am I ok to commit just the Cortex-A510 half into gcc-12 and gcc-13.

Thanks,
Richard Ball
________________________________
From: Richard Ball
Sent: 12 March 2024 14:08
To: 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: [PATCH][GCC] aarch64: Fix SCHEDULER_IDENT for Cortex-A510

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?

Can I also backport this to gcc-12 and gcc-13?

gcc/ChangeLog:
        PR target/114272
        * config/aarch64/aarch64-cores.def (AARCH64_CORE):
        Change SCHEDULER_IDENT from cortexa55 to cortexa53
        for Cortex-A510.

  reply	other threads:[~2024-04-25 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 14:07 Richard Ball
2024-04-25 14:59 ` Richard Ball [this message]
2024-04-26  9:20   ` Richard Earnshaw (lists)

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=DB9PR08MB6957EC19E77A9257BF33E2DB81172@DB9PR08MB6957.eurprd08.prod.outlook.com \
    --to=richard.ball@arm.com \
    --cc=Richard.Earnshaw@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).