public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: gcc-patches@gcc.gnu.org
Cc: philipp.tomsich@theobroma-systems.com
Subject: [AArch64 13/14] Initial tuning description for XGene-1 core.
Date: Tue, 18 Feb 2014 21:28:00 -0000	[thread overview]
Message-ID: <1392757787-25629-14-git-send-email-philipp.tomsich@theobroma-systems.com> (raw)
In-Reply-To: <1392757787-25629-1-git-send-email-philipp.tomsich@theobroma-systems.com>

The generic cost model for AArch64 can not be used to capture the
microarchitectural cost of XGene-1 in full detail.  For this reason,
we use the basic tuning model of the Cortex-A53 for now.
---
 gcc/config/aarch64/aarch64-cores.def |  2 +-
 gcc/config/aarch64/aarch64.c         | 28 ++++++++++++++++++++++++++++
 2 files changed, 29 insertions(+), 1 deletion(-)

diff --git a/gcc/config/aarch64/aarch64-cores.def b/gcc/config/aarch64/aarch64-cores.def
index b4f6c16..abbfea9 100644
--- a/gcc/config/aarch64/aarch64-cores.def
+++ b/gcc/config/aarch64/aarch64-cores.def
@@ -36,7 +36,7 @@
 
 AARCH64_CORE("cortex-a53",  cortexa53, cortexa53, 8,  AARCH64_FL_FPSIMD | AARCH64_FL_CRC | AARCH64_FL_CRYPTO, cortexa53)
 AARCH64_CORE("cortex-a57",  cortexa15, cortexa15, 8,  AARCH64_FL_FPSIMD | AARCH64_FL_CRC | AARCH64_FL_CRYPTO, generic)
-AARCH64_CORE("xgene1",      xgene1,    xgene1,    8,  AARCH64_FL_FPSIMD, generic)
+AARCH64_CORE("xgene1",      xgene1,    xgene1,    8,  AARCH64_FL_FPSIMD, xgene1)
 
 /* V8 big.LITTLE implementations.  */
 
diff --git a/gcc/config/aarch64/aarch64.c b/gcc/config/aarch64/aarch64.c
index 4327eb3..4c06f9b 100644
--- a/gcc/config/aarch64/aarch64.c
+++ b/gcc/config/aarch64/aarch64.c
@@ -192,6 +192,20 @@ static const struct cpu_regmove_cost generic_regmove_cost =
   NAMED_PARAM (FP2FP, 4)
 };
 
+static const struct cpu_regmove_cost xgene1_regmove_cost =
+{
+  NAMED_PARAM (GP2GP, 1),
+  /* We want all GP2FP and FP2GP moves to be handled by a reload.
+     A direct move instruction will have similar microarchitectural
+     cost to a store/load combination.  */
+  NAMED_PARAM (GP2FP, 4),
+  NAMED_PARAM (FP2GP, 4),
+  /* We currently do not provide direct support for TFmode Q->Q move.
+     Therefore we need to raise the cost above 2 in order to have
+     reload handle the situation.  */
+  NAMED_PARAM (FP2FP, 4)
+};
+
 /* Generic costs for vector insn classes.  */
 #if HAVE_DESIGNATED_INITIALIZERS && GCC_VERSION >= 2007
 __extension__
@@ -237,6 +251,20 @@ static const struct tune_params cortexa53_tunings =
   NAMED_PARAM (branch_cost, 2)
 };
 
+/* We can't model the microarchitectural costs on XGene using  the default
+   cost model for AArch64.  So we leave the extra cost structure pointing
+   to the default cost model for the time being.  */
+static const struct tune_params xgene1_tunings =
+{
+  &cortexa53_extra_costs,
+  &generic_addrcost_table,
+  &xgene1_regmove_cost,
+  &generic_vector_cost,
+  NAMED_PARAM (memmov_cost, 4),
+  NAMED_PARAM (issue_rate, 4),
+  NAMED_PARAM (branch_cost, 2)
+};
+
 /* A processor implementing AArch64.  */
 struct processor
 {
-- 
1.9.0

  parent reply	other threads:[~2014-02-18 21:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 21:10 [AArch64 00/14] Pipeline-independent changes for XGene-1 Philipp Tomsich
2014-02-18 21:10 ` [AArch64 04/14] Correct the maximum shift amount for shifted operands Philipp Tomsich
2014-02-18 21:20   ` Andrew Pinski
2014-02-18 21:10 ` [AArch64 03/14] Retrieve BRANCH_COST from tuning structure Philipp Tomsich
2014-02-18 21:10 ` [AArch64 02/14] Add "xgene1" core identifier Philipp Tomsich
2014-02-18 21:10 ` [AArch64 07/14] Define additional patterns for adds/subs Philipp Tomsich
2014-02-18 21:19   ` Andrew Pinski
2014-02-18 21:10 ` [AArch64 06/14] Extend '*tb<optab><mode>1' Philipp Tomsich
2014-02-18 21:19   ` Andrew Pinski
2014-02-18 21:10 ` [AArch64 01/14] Use "generic" target, if no other default Philipp Tomsich
2014-02-21 14:02   ` Kyrill Tkachov
2014-02-18 21:10 ` [AArch64 05/14] Add AArch64 'prefetch'-pattern Philipp Tomsich
2014-02-18 21:18   ` Andrew Pinski
2014-02-28  8:58   ` Gopalasubramanian, Ganesh
2014-02-28  9:14   ` Gopalasubramanian, Ganesh
2014-02-28  9:28     ` Dr. Philipp Tomsich
2014-05-28 14:25       ` Gopalasubramanian, Ganesh
2014-05-28 14:41         ` Dr. Philipp Tomsich
2014-02-18 21:26 ` [AArch64 10/14] Add mov<mode>cc definition for GPF case Philipp Tomsich
2014-02-18 21:40   ` Andrew Pinski
2014-02-18 21:27 ` [AArch64 11/14] Optimize and(s) patterns for HI/QI operands Philipp Tomsich
2014-02-18 21:41   ` Andrew Pinski
2014-02-18 21:28 ` [AArch64 14/14] Add cost-model for XGene-1 Philipp Tomsich
2014-02-18 21:28 ` Philipp Tomsich [this message]
2014-02-18 21:29 ` [AArch64 08/14] Define a variant of cmp for the CC_NZ case Philipp Tomsich
2014-02-18 21:42   ` Andrew Pinski
2014-02-18 21:29 ` [AArch64 09/14] Add special cases of zero-extend w/ compare operations Philipp Tomsich
2014-02-18 21:42   ` Andrew Pinski
2014-02-18 21:30 ` [AArch64 12/14] Generate 'bics', when only interested in CC_NZ Philipp Tomsich
2014-02-18 21:43   ` Andrew Pinski
2014-02-19 14:02 ` [AArch64 00/14] Pipeline-independent changes for XGene-1 Richard Earnshaw
2014-02-19 14:41 ` Ramana Radhakrishnan

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=1392757787-25629-14-git-send-email-philipp.tomsich@theobroma-systems.com \
    --to=philipp.tomsich@theobroma-systems.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).