From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: James Greenhalgh <james.greenhalgh@arm.com>, gcc-patches@gcc.gnu.org
Cc: nd@arm.com, marcus.shawcroft@arm.com
Subject: Re: [Patch AArch64 docs] Document the RcPc extension
Date: Mon, 03 Jul 2017 14:24:00 -0000 [thread overview]
Message-ID: <dfc92e39-0c40-431d-88e3-68cea1fcbb8a@arm.com> (raw)
In-Reply-To: <1498213303-20637-1-git-send-email-james.greenhalgh@arm.com>
On 23/06/17 11:21, James Greenhalgh wrote:
>
> Hi,
>
> Andrew pointed out that I did not document the new architecture extension
> flag I added the RcPc iextension. This was intentional, as enablihg the rcpc
> extension does not change GCC code generation, and is just an assembler flag.
> But for completeness, here is documentation for the new option.
>
> OK?
>
OK.
R.
> Thanks,
> James
>
> ---
> 2017-06-21 James Greenhalgh <james.greenhalgh@arm.com>
>
> * doc/invoke.texi (rcpc architecture extension): Document it.
>
>
> 0001-Patch-AArch64-docs-Document-the-RcPc-extension.patch
>
>
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index 7e7a16a5..db00e51 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -14172,6 +14172,10 @@ Enable Large System Extension instructions. This is on by default for
> @option{-march=armv8.1-a}.
> @item fp16
> Enable FP16 extension. This also enables floating-point instructions.
> +@item rcpc
> +Enable the RcPc extension. This does not change code generation from GCC,
> +but is passed on to the assembler, enabling inline asm statements to use
> +instructions from the RcPc extension.
>
> @end table
>
>
prev parent reply other threads:[~2017-07-03 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 10:22 James Greenhalgh
2017-07-03 10:44 ` James Greenhalgh
2017-07-03 14:24 ` 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=dfc92e39-0c40-431d-88e3-68cea1fcbb8a@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=marcus.shawcroft@arm.com \
--cc=nd@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).