From: James Greenhalgh <james.greenhalgh@arm.com>
To: Virendra Pathak <virendra.pathak@broadcom.com>
Cc: <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>, <nd@arm.com>
Subject: Re: [PATCH/AARCH64] Accept vulcan as a cpu name for the AArch64 port of GCC
Date: Tue, 21 Jun 2016 13:47:00 -0000 [thread overview]
Message-ID: <20160621134640.GA31439@arm.com> (raw)
In-Reply-To: <CANx+fTD5Jc-ZQTB9Cf4own4B0TebVPO7WXHkAvs+Rp90cHxpkA@mail.gmail.com>
On Sat, Jun 18, 2016 at 01:57:43AM +0530, Virendra Pathak wrote:
> Hi,
>
> Please find the patch for introducing vulcan as a cpu name for the
> AArch64 port of GCC.
> Broadcom's vulcan is an armv8.1-a aarch64 server processor.
>
> Since vulcan is the first armv8.1-a processor to be introduced in
> aarch64-cores.def,
> I have created a new section in the file for the armv8.1 based processors.
> Kindly let me know if that is okay.
>
> Tested the patch with cross aarch64-linux-gnu, bootstrapped native
> aarch64-unknown-linux-gnu
> and make check (gcc, ld, gas, binutils, gdb).
> No new regression failure is added by this patch.
>
> In addition, tested -mcpu=vulcan -mtune=vulcan flags by passing them
> via command line.
> Also verified that above flags passes armv8.1-a option to assembler(as).
>
> At present we are using schedule & cost model of cortex-a57 but
> soon we will be submitting one for vulcan.
>
> Please review the patch.
> Ok for trunk?
>
This patch is OK for trunk.
I couldn't spot your name in the MAINTAINERS file, so I've applied this
on your behalf as revision 237645.
Thank you for the patch.
Thanks,
James
> gcc/ChangeLog:
>
> Virendra Pathak <virendra.pathak@broadcom.com>
>
> * config/aarch64/aarch64-cores.def (vulcan): New core.
> * config/aarch64/aarch64-tune.md: Regenerate.
> * doc/invoke.texi: Document vulcan as an available option.
>
next prev parent reply other threads:[~2016-06-21 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 20:28 Virendra Pathak
2016-06-21 13:47 ` James Greenhalgh [this message]
2016-06-21 14:16 ` Virendra Pathak
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=20160621134640.GA31439@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marcus.shawcroft@arm.com \
--cc=nd@arm.com \
--cc=virendra.pathak@broadcom.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).