From: Tejas Belagod <tejas.belagod@arm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [AArch64, Docs, Patch] Add reference to ACLE in docs.
Date: Tue, 04 Nov 2014 13:17:00 -0000 [thread overview]
Message-ID: <5458D202.5080001@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1411031756170.26067@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On 03/11/14 17:58, Joseph Myers wrote:
> On Mon, 3 Nov 2014, Tejas Belagod wrote:
>
>> If I mention in a couple of sentences the level of ACLE support there is in
>> GCC currently, this section will need to be updated every time there is an
>> improvement in ACLE support - I guess we'll just have to remember to remove
>> parts of this section as we do that.
>
> Yes, it's generally the case when adding new user-visible features that
> documentation needs updating. The release notes (gcc-N/changes.html in
> htdocs) should be updated for any significant new features as well.
>
Thanks. The AArch64 ACLE CRC32 intrinsics were introduced in 4.9, so its
not new in 5.0 - https://gcc.gnu.org/gcc-4.9/changes.html. But we've
improved AArch64 NEON Intrinsics in 5.0 significantly which deserves a
mention. I'll do that in a separate patch.
Revised patch to fix extend.texi for ACLE attached. OK for trunk?
Thanks,
Tejas.
2014-11-04 Tejas Belagod <tejas.belagod@arm.com>
gcc/
* Makefile.in (TEXI_GCC_FILES): Remove arm-acle-intrinsics.texi,
arm-neon-intrinsics.texi, aarch64-acle-intrinsics.texi.
* doc/aarch64-acle-intrinsics.texi: Remove.
* doc/arm-acle-intrinsics.texi: Remove.
* doc/arm-neon-intrinsics.texi: Remove.
* doc/extend.texi: Consolidate sections AArch64 intrinsics,
ARM NEON Intrinsics, ARM ACLE Intrinsics into one ARM C Language
Extension section. Add references to public ACLE specification.
[-- Attachment #2: intrinsics-doc-3.txt.gz --]
[-- Type: application/gzip, Size: 20096 bytes --]
next prev parent reply other threads:[~2014-11-04 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 15:28 Tejas Belagod
2014-10-29 1:23 ` Joseph S. Myers
2014-11-03 11:51 ` Tejas Belagod
2014-11-03 17:59 ` Joseph Myers
2014-11-04 13:17 ` Tejas Belagod [this message]
2014-11-07 13:09 ` Richard Earnshaw
2014-11-12 8:51 ` Tejas Belagod
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=5458D202.5080001@arm.com \
--to=tejas.belagod@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).