From: Philipp Tomsich <philipp.tomsich@vrull.eu>
To: gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Tamar Christina <tamar.christina@arm.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Manolis Tsamis <manolis.tsamis@vrull.eu>
Subject: [PATCH] aarch64: update ampere1 vectorization cost
Date: Mon, 27 Mar 2023 09:46:54 +0200 [thread overview]
Message-ID: <20230327074654.1126912-1-philipp.tomsich@vrull.eu> (raw)
The original submission of AmpereOne (-mcpu=ampere1) costs occurred
prior to exhaustive testing of vectorizable workloads against
hardware.
Adjust the vector costs to achieve the best results and more closely
match the underlying hardware.
gcc/ChangeLog:
* config/aarch64/aarch64.cc: Update vector costs for ampere1.
Co-Authored-By: Manolis Tsamis <manolis.tsamis@vrull.eu>
Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
---
We would like to get this into GCC 13 to avoid having to backport at
the start of the next cycle.
OK for backports?
gcc/config/aarch64/aarch64.cc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
index b27f4354031..661fff65cea 100644
--- a/gcc/config/aarch64/aarch64.cc
+++ b/gcc/config/aarch64/aarch64.cc
@@ -1132,7 +1132,7 @@ static const struct cpu_vector_cost thunderx3t110_vector_cost =
static const advsimd_vec_cost ampere1_advsimd_vector_cost =
{
- 3, /* int_stmt_cost */
+ 1, /* int_stmt_cost */
3, /* fp_stmt_cost */
0, /* ld2_st2_permute_cost */
0, /* ld3_st3_permute_cost */
@@ -1148,17 +1148,17 @@ static const advsimd_vec_cost ampere1_advsimd_vector_cost =
8, /* store_elt_extra_cost */
6, /* vec_to_scalar_cost */
7, /* scalar_to_vec_cost */
- 5, /* align_load_cost */
- 5, /* unalign_load_cost */
- 2, /* unalign_store_cost */
- 2 /* store_cost */
+ 4, /* align_load_cost */
+ 4, /* unalign_load_cost */
+ 1, /* unalign_store_cost */
+ 1 /* store_cost */
};
/* Ampere-1 costs for vector insn classes. */
static const struct cpu_vector_cost ampere1_vector_cost =
{
1, /* scalar_int_stmt_cost */
- 1, /* scalar_fp_stmt_cost */
+ 3, /* scalar_fp_stmt_cost */
4, /* scalar_load_cost */
1, /* scalar_store_cost */
1, /* cond_taken_branch_cost */
--
2.34.1
next reply other threads:[~2023-03-27 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 7:46 Philipp Tomsich [this message]
2023-03-27 8:44 ` Kyrylo Tkachov
2023-03-27 8:49 ` Philipp Tomsich
2023-03-27 9:23 ` Kyrylo Tkachov
2023-04-03 11:45 ` Philipp Tomsich
2023-04-04 12:49 ` Kyrylo Tkachov
2023-03-27 9:13 ` Philipp Tomsich
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=20230327074654.1126912-1-philipp.tomsich@vrull.eu \
--to=philipp.tomsich@vrull.eu \
--cc=gcc-patches@gcc.gnu.org \
--cc=manolis.tsamis@vrull.eu \
--cc=richard.sandiford@arm.com \
--cc=tamar.christina@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).