public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Richard Ball <ricbal02@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 7cd7e13e443da8e2aae389fa30eb547530c6e2c8
Date: Mon,  8 Apr 2024 15:53:06 +0000 (GMT)	[thread overview]
Message-ID: <20240408155306.14DA63858D28@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  7cd7e13e443da8e2aae389fa30eb547530c6e2c8 (commit)
      from  8765e9c73ae14cfad592b8a3885fe1bcc3ff96cd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7cd7e13e443da8e2aae389fa30eb547530c6e2c8
Author: Richard Ball <richard.ball@arm.com>
Date:   Mon Apr 8 16:52:00 2024 +0100

    [PATCH][wwwdocs] Add NEON-SVE bridge intrinsics to changes.html
    
    Adding the NEON-SVE bridge intrinsics that were missed
    in the last patch.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 2d8968cf..1b345b32 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -503,6 +503,12 @@ a work-in-progress.</p>
       <code>-march=armv8.2-a</code> or higher to be specified.  Likewise, the
       intrinsics enabled by <code>+memtag</code> no longer require
       <code>-march=armv8.5-a</code>.</li>
+      <li>Support for the
+      <a href="https://github.com/ARM-software/acle/blob/main/main/acle.md#neon-sve-bridge">
+      NEON-SVE Bridge intrinsics</a>.
+      These are intrinsics that allow conversions between NEON and SVE vectors,
+      enabled through the inclusion of the <code>arm_neon_sve_bridge.h</code> header.
+      </li>
     </ul></li>
   <li>The option <code>-mtp=</code> is now supported for changing the TPIDR
    register used for TLS accesses.  For more details please refer to the

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-14/changes.html | 6 ++++++
 1 file changed, 6 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2024-04-08 15:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240408155306.14DA63858D28@sourceware.org \
    --to=ricbal02@sourceware.org \
    --cc=gcc-cvs-wwwdocs@gcc.gnu.org \
    /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).