public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114272] SCHEDULER_IDENT incorrect for Cortex-A520 and Cortex-A510 Date: Fri, 26 Apr 2024 17:22:11 +0000 [thread overview] Message-ID: <bug-114272-4-WcCv1Coi1g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114272-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114272 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Ball <ricbal02@gcc.gnu.org>: https://gcc.gnu.org/g:751a0f54345b7e037db7f0389c19c1f87e0ae4de commit r12-10397-g751a0f54345b7e037db7f0389c19c1f87e0ae4de Author: Richard Ball <richard.ball@arm.com> Date: Fri Apr 26 18:21:07 2024 +0100 aarch64: Fix SCHEDULER_IDENT for Cortex-A510 The SCHEDULER_IDENT for this CPU was incorrectly set to cortexa55. This can cause sub-optimal asm to be generated. gcc/ChangeLog: PR target/114272 * config/aarch64/aarch64-cores.def (AARCH64_CORE): Change SCHEDULER_IDENT from cortexa55 to cortexa53 for Cortex-A510.
next prev parent reply other threads:[~2024-04-26 17:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-07 16:54 [Bug target/114272] New: " ricbal02 at gcc dot gnu.org 2024-03-07 16:55 ` [Bug target/114272] " ricbal02 at gcc dot gnu.org 2024-03-07 17:00 ` pinskia at gcc dot gnu.org 2024-03-07 17:02 ` ricbal02 at gcc dot gnu.org 2024-03-26 13:57 ` cvs-commit at gcc dot gnu.org 2024-03-26 13:58 ` ricbal02 at gcc dot gnu.org 2024-04-26 17:16 ` cvs-commit at gcc dot gnu.org 2024-04-26 17:22 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-26 17:25 ` ricbal02 at gcc dot gnu.org
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=bug-114272-4-WcCv1Coi1g@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).