From: Andrew Pinski <quic_apinski@quicinc.com>
To: <gcc-patches@gcc.gnu.org>
Cc: Andrew Pinski <quic_apinski@quicinc.com>
Subject: [PATCH 0/2] aarch64: Small cleanups of the cavium cores
Date: Mon, 17 Jun 2024 20:40:30 -0700 [thread overview]
Message-ID: <20240618034032.84888-1-quic_apinski@quicinc.com> (raw)
While thinking the variant patch I had posted, I went back to
look at the original cores which used the variant and saw there
was small cleanup for them since thunderx was no longer considered
a V8.1-a core but rather just a V8-a one; when I did that change
I didn't do the cleanups like is done in this patch set.
Note there is a core which uses the variant selection so we can't
remove the code there.
Andrew Pinski (2):
aarch64: make thunderxt88p1 an alias of thunderxt88
aarch64: Add comment about thunderxt81/t83 being aliases
gcc/config/aarch64/aarch64-cores.def | 6 +++---
gcc/config/aarch64/aarch64-tune.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2024-06-18 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 3:40 Andrew Pinski [this message]
2024-06-18 3:40 ` [PATCH 1/2] aarch64: make thunderxt88p1 an alias of thunderxt88 Andrew Pinski
2024-06-18 3:40 ` [PATCH 2/2] aarch64: Add comment about thunderxt81/t83 being aliases Andrew Pinski
2024-06-18 7:21 ` [PATCH 0/2] aarch64: Small cleanups of the cavium cores Kyrylo Tkachov
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=20240618034032.84888-1-quic_apinski@quicinc.com \
--to=quic_apinski@quicinc.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).