From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
Subject: Re: [PATCH][ARM][wwwdocs] Mention Cortex-A32 and Cortex-A35 support in changes.html for GCC 6
Date: Fri, 26 Feb 2016 14:49:00 -0000 [thread overview]
Message-ID: <56D065FA.50101@arm.com> (raw)
In-Reply-To: <56D0604C.4080706@foss.arm.com>
On 26/02/16 14:25, Kyrill Tkachov wrote:
> Hi all,
>
> This patch adds a note to changes.html about the added support for
> Cortex-A32 and Cortex-A35.
>
> Ok to commit?
>
OK.
R.
> Thanks,
> Kyrill
>
> wwwdocs-a32-a35.patch
>
>
> Index: htdocs/gcc-6/changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
> retrieving revision 1.62
> diff -U 3 -r1.62 changes.html
> --- htdocs/gcc-6/changes.html 24 Feb 2016 09:36:06 -0000 1.62
> +++ htdocs/gcc-6/changes.html 25 Feb 2016 10:51:14 -0000
> @@ -345,6 +345,15 @@
> documentation</a> for details of available attributes and
> pragmas as well as usage instructions.
> </li>
> + <li>
> + Support has been added for the following processors
> + (GCC identifiers in parentheses): ARM Cortex-A32
> + (<code>cortex-a32</code>), ARM Cortex-A35 (<code>cortex-a35</code>).
> + The GCC identifiers can be used
> + as arguments to the <code>-mcpu</code> or <code>-mtune</code> options,
> + for example: <code>-mcpu=cortex-a32</code> or
> + <code>-mtune=cortex-a35</code>.
> + </li>
> </ul>
> <!-- <h3 id="avr">AVR</h3> -->
>
>
prev parent reply other threads:[~2016-02-26 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 14:25 Kyrill Tkachov
2016-02-26 14:49 ` Richard Earnshaw (lists) [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=56D065FA.50101@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=ramana.radhakrishnan@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).