From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
kyrtka01@arm.com,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Richard Earnshaw <richard.earnshaw@arm.com>
Subject: Re: [Patch ARM] Add support for Cortex-A35
Date: Tue, 17 Nov 2015 09:06:00 -0000 [thread overview]
Message-ID: <CAJA7tRZKnL74xQaTmAiU7cTJpXQqx5voU7g-zXjGKSAvttRXGQ@mail.gmail.com> (raw)
In-Reply-To: <1447684941-37806-1-git-send-email-james.greenhalgh@arm.com>
On Mon, Nov 16, 2015 at 2:42 PM, James Greenhalgh
<james.greenhalgh@arm.com> wrote:
>
> Hi,
>
> This patch adds support to the ARM back-end for the Cortex-A35
> processor, as recently announced by ARM. The ARM Cortex-A35 provides
> full support for the ARMv8-A architecture, including the CRC extension,
> with optional Advanced-SIMD and Floating-Point support. We therefore set
> feature flags for this CPU to FL_FOR_ARCH8A and FL_CRC32 and FL_LDSCHED,
> in the same fashion as Cortex-A53 and Cortex-A57. While the Cortex-A35
> has dual issue capabilities, we model it with an issue rate of one, with
> the expectation that this will give better schedules when using the
> Cortex-A53 pipeline model.
>
> Bootstrapped with --with-tune=cortex-a35 with no issues.
>
> I'm sorry to have this upstream a little late for the close of Stage 1,
> I wanted to wait for binutils support to be committed. This happened
> on Thursday [1]. If it is OK with the ARM maintainers, I'd like to get
> this in to GCC 6.
>
> OK?
Can you also deal with an entry in the news for GCC6 page ?
Ramana
>
> Thanks,
> James
>
> [1]: https://sourceware.org/ml/binutils-cvs/2015-11/msg00065.html
>
> ---
> 2015-11-16 James Greenhalgh <james.greenhalgh@arm.com>
>
> * config/arm/arm-cores.def (cortex-a35): New.
> * config/arm/arm.c (arm_cortex_a35_tune): New.
> * config/arm/arm-tables.opt: Regenerate.
> * config/arm/arm-tune.md: Regenerate.
> * config/arm/bpabi.h (BE8_LINK_SPEC): Add cortex-a35.
> * config/arm/t-aprofile: Likewise.
> * doc/invoke.texi (-mcpu): Likewise.
>
next prev parent reply other threads:[~2015-11-17 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 14:37 [Patch AArch64] " James Greenhalgh
2015-11-16 14:42 ` [Patch ARM] " James Greenhalgh
2015-11-16 17:21 ` Kyrill Tkachov
2015-11-17 9:06 ` Ramana Radhakrishnan [this message]
2015-11-17 10:13 ` [Patch AArch64] " Marcus Shawcroft
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=CAJA7tRZKnL74xQaTmAiU7cTJpXQqx5voU7g-zXjGKSAvttRXGQ@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=kyrtka01@arm.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@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).