public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: SRINATH PARVATHANENI <sripar01@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. c0cb380cbff9eb7f8c4a8964fba09a8af0ecc6f6
Date: Fri, 15 May 2020 10:53:25 +0000 (GMT)	[thread overview]
Message-ID: <20200515105325.D108E397A4AE@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  c0cb380cbff9eb7f8c4a8964fba09a8af0ecc6f6 (commit)
      from  7ec1397664d785019347a06903e89d8a7ff71d79 (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 c0cb380cbff9eb7f8c4a8964fba09a8af0ecc6f6
Author: Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Date:   Fri May 15 11:51:37 2020 +0100

    [ARM]: Document Armv8.1-M Mainline, MVE Intrinsics and Cortex-M55 changes.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index b9fae2c6..0d9e97f7 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -786,6 +786,7 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512)));
          <li>Arm Cortex-A77 (<code>cortex-a77</code>).</li>
          <li>Arm Cortex-A76AE (<code>cortex-a76ae</code>).</li>
          <li>Arm Cortex-M35P (<code>cortex-m35p</code>).</li>
+         <li>Arm Cortex-M55 (<code>cortex-m55</code>).</li>
        </ul>
        The GCC identifiers can be used
        as arguments to the <code>-mcpu</code> or <code>-mtune</code> options,
@@ -802,6 +803,16 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512)));
   added: this M-profile feature is no longer restricted to targets
   with <code>MOVT</code>. For example, <code>-mcpu=cortex-m0</code>
   now supports this option.</li>
+  <li>Support for the
+  <a href="https://developer.arm.com/architectures/cpu-architecture/m-profile">
+  Armv8.1-M Mainline</a> Architecture has been added.</li>
+  <ul>
+    <li> Armv8.1-M Mainline can be enabled by using the <code>-march=armv8.1-m.main<code> command line option.
+  <ul>
+  <li>Support for the
+  <a href="https://developer.arm.com/architectures/instruction-sets/simd-isas/helium/helium-intrinsics">
+  MVE</a> beta ACLE intrinsics has been added. These intrinsics can be enabled by including the arm_mve.h header file
+  and passing the <code>+mve<code> or <code>+mve.fp<code> option extensions (for example: <code>-march=armv8.1-m.main+mve<code>).</li>
   <li>Support for the Custom Datapath Extension beta ACLE
   <a href="https://developer.arm.com/docs/101028/0010/custom-datapath-extension">
   intrinsics</a> has been added.</li>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-15 10: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=20200515105325.D108E397A4AE@sourceware.org \
    --to=sripar01@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).