public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Haochen Jiang <jianghc@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 6e41ef3dbbc0e2a774e3fd0947857c75e0d16da2
Date: Mon, 14 Nov 2022 06:06:12 +0000 (GMT)	[thread overview]
Message-ID: <20221114060617.72C3E385840D@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  6e41ef3dbbc0e2a774e3fd0947857c75e0d16da2 (commit)
      from  11ebca554aa82f8f2a55f0a84ce18605a8232581 (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 6e41ef3dbbc0e2a774e3fd0947857c75e0d16da2
Author: Haochen Jiang <haochen.jiang@intel.com>
Date:   Mon Nov 14 13:57:03 2022 +0800

    gcc-13: Mention Intel new ISA and march support.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index bd11cbec..0daf921b 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -240,6 +240,56 @@ a work-in-progress.</p>
   <code>__bf16</code> type to x86 psABI. Users need to adjust their
   AVX512BF16-related source code when upgrading GCC12 to GCC13.
   </li>
+  <li>New ISA extension support for Intel AVX-IFMA was added to GCC.
+      AVX-IFMA intrinsics are available via the <code>-mavxifma</code>
+      compiler switch.
+  </li>
+  <li>New ISA extension support for Intel AVX-VNNI-INT8 was added to GCC.
+      AVX-VNNI-INT8 intrinsics are available via the <code>-mavxvnniint8</code>
+      compiler switch.
+  </li>
+  <li>New ISA extension support for Intel AVX-NE-CONVERT was added to GCC.
+      AVX-NE-CONVERT intrinsics are available via the
+      <code>-mavxneconvert</code> compiler switch.
+  </li>
+  <li>New ISA extension support for Intel CMPccXADD was added to GCC.
+      CMPccXADD intrinsics are available via the <code>-mcmpccxadd</code>
+      compiler switch.
+  </li>
+  <li>New ISA extension support for Intel AMX-FP16 was added to GCC.
+      AMX-FP16 intrinsics are available via the <code>-mamx-fp16</code>
+      compiler switch.
+  </li>
+  <li>New ISA extension support for Intel PREFETCHI was added to GCC.
+      PREFETCHI intrinsics are available via the <code>-mprefetchi</code>
+      compiler switch.
+  </li>
+  <li>New ISA extension support for Intel RAO-INT was added to GCC.
+      RAO-INT intrinsics are available via the <code>-mraoint</code>
+      compiler switch.
+  </li>
+  <li>GCC now supports the Intel CPU named Raptor Lake through
+    <code>-march=raptorlake</code>.
+    Raptor Lake is based on Alder Lake.
+  </li>
+  <li>GCC now supports the Intel CPU named Meteor Lake through
+    <code>-march=meteorlake</code>.
+    Meteor Lake is based on Alder Lake.
+  </li>
+  <li>GCC now supports the Intel CPU named Sierra Forest through
+    <code>-march=sierraforest</code>.
+    The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT and
+    CMPccXADD ISA extensions.
+  </li>
+  <li>GCC now supports the Intel CPU named Grand Ridge through
+    <code>-march=grandridge</code>.
+    The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD
+    and RAO-INT ISA extensions.
+  </li>
+  <li>GCC now supports the Intel CPU named Granite Rapids through
+    <code>-march=graniterapids</code>.
+    The switch enables the AMX-FP16 and PREFETCHI ISA extensions.
+  </li>
 </ul>
 
 <!-- <h3 id="mips">MIPS</h3> -->

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

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


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-14  6:06 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=20221114060617.72C3E385840D@sourceware.org \
    --to=jianghc@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).