From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Andrew Pinski <apinski@cavium.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH/AARCH64] Add ThunderX -mcpu support
Date: Tue, 21 Oct 2014 09:49:00 -0000 [thread overview]
Message-ID: <CAFqB+Pzchhy0ao28JR+fQbvT+HgZdgh9FGTKgHkcBCsv84DVFA@mail.gmail.com> (raw)
In-Reply-To: <CADASvAMn1sMXAHjF7E0xCZxsyHA3WfFDfq5wt2_dpxHo-SHR3w@mail.gmail.com>
On 20 October 2014 21:45, Andrew Pinski <apinski@cavium.com> wrote:
> Hi,
> This adds simple -mcpu=thunderx support. Right now we use the
> schedule model of cortex-a53 but we will submit a schedule model for
> ThunderX later on. Note ThunderX is an AARCH64 only processor so I
> created a new file to hold the cost tables for it rather than adding
> it to aarch-cost-tables.h.
>
> OK? Built and tested for aarch64-elf.
OK, thanks!
Couple of minor nits:
+/* RTX cost tables for aarch64.
s/aarch64/AArch64/
+/* ThunderX does not have implement AARCH32. */
s/AARCH32/AArch32/
Cheers
/Marcus
> Thanks,
> Andrew Pinski
>
> PS The corresponding binutils patch is located at
> https://sourceware.org/ml/binutils/2014-10/msg00170.html .
>
>
> ChangeLog:
> * doc/invoke.texi (AARCH64/mtune): Document thunderx as an available
> option also.
> * config/aarch64/aarch64-cost-tables.h: New file.
> * config/aarch64/aarch64-cores.def (thunderx): New core.
> * config/aarch64/aarch64-tune.md: Regenerate.
> * config/aarch64/aarch64.c: Include aarch64-cost-tables.h instead of
> config/arm/aarch-cost-tables.h.
> (thunderx_regmove_cost): New variable.
> (thunderx_tunings): New variable.
prev parent reply other threads:[~2014-10-21 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADASvAPtt4gpKLUyq42rOtKKTA9Pwj5=+-bmx+rJFHANHMfX_A@mail.gmail.com>
2014-10-20 20:46 ` Fwd: " Andrew Pinski
2014-10-20 22:02 ` Evandro Menezes
2014-10-21 9:49 ` Marcus Shawcroft [this message]
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=CAFqB+Pzchhy0ao28JR+fQbvT+HgZdgh9FGTKgHkcBCsv84DVFA@mail.gmail.com \
--to=marcus.shawcroft@gmail.com \
--cc=apinski@cavium.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).