public inbox for
 help / color / mirror / Atom feed
From: Haochen Jiang <>
Subject: [PATCH] gcc-13: Mention Intel AMX-COMPLEX ISA support and revise march support
Date: Mon, 10 Apr 2023 10:08:07 +0800	[thread overview]
Message-ID: <> (raw)

Hi all,

This patch mentions Intel AMX-COMPLEX ISA support in GCC 13.

Also it revises the march support according to newly released
Intel Architecture Instruction Set Extensions and Future Features.

Ok for trunk?


 htdocs/gcc-13/changes.html | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 71cb335d..84207104 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -520,6 +520,10 @@ a work-in-progress.</p>
       RAO-INT intrinsics are available via the <code>-mraoint</code>
       compiler switch.
+  <li>New ISA extension support for Intel AMX-COMPLEX was added.
+      AMX-COMPLEX intrinsics are available via the <code>-mamx-complex</code>
+      compiler switch.
+  </li>
   <li>GCC now supports the Intel CPU named Raptor Lake through
     Raptor Lake is based on Alder Lake.
@@ -538,9 +542,13 @@ a work-in-progress.</p>
     The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD
     and RAO-INT ISA extensions.
+  <li>GCC now supports the Intel CPU named Emerald Rapids through
+    <code>-march=emeraldrapids</code>.
+    Emerald Rapids is based on Sapphire Rapids.
+  </li>
   <li>GCC now supports the Intel CPU named Granite Rapids through
-    The switch enables the AMX-FP16 and PREFETCHI ISA extensions.
+    The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA extensions.
   <li>GCC now supports AMD CPUs based on the <code>znver4</code> core
     via <code>-march=znver4</code>.  The switch makes GCC consider

             reply	other threads:[~2023-04-10  2:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  2:08 Haochen Jiang [this message]
2023-04-13  1:59 ` Hongtao Liu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).