public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: liuhongt <hongtao.liu@intel.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] wwwdocs: [GCC12] Mention Intel AVX512-FP16.
Date: Thu, 23 Sep 2021 13:38:25 +0800	[thread overview]
Message-ID: <20210923053825.89498-1-hongtao.liu@intel.com> (raw)

---
 htdocs/gcc-12/changes.html | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 81f62fe3..14149212 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -165,8 +165,12 @@ a work-in-progress.</p>
   </li>
 </ul>
 
-<!-- <h3 id="x86">IA-32/x86-64</h3> -->
-
+<h3 id="x86">IA-32/x86-64</h3>
+<ul>
+  <li>New ISA extension support for Intel AVX512-FP16 was added to GCC.
+      AVX512FP16 intrinsics are available via the <code>-mavx512fp16</code>
+      compiler switch.</li>
+</ul>
 <!-- <h3 id="mips">MIPS</h3> -->
 
 <!-- <h3 id="mep">MeP</h3> -->
-- 
2.18.1


             reply	other threads:[~2021-09-23  5:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  5:38 liuhongt [this message]
2021-09-23 20:42 ` Joseph Myers
2021-09-24  1:17   ` [PATCH] [GCC12] Mention Intel AVX512-FP16 and _Float16 support liuhongt
2021-09-24  1:20     ` H.J. Lu
2021-09-24  1:44       ` Hongtao Liu
2021-09-24  1:41         ` H.J. Lu
2021-09-24  2:04           ` Hongtao Liu
2021-09-24  2:12             ` H.J. Lu
2021-10-01 10:13             ` Gerald Pfeifer
2021-10-08  1:25               ` Hongtao Liu
2023-01-28 12:40                 ` Gerald Pfeifer
2023-01-29  1:20                   ` [PATCH] Change AVX512FP16 to AVX512-FP16 in the document liuhongt
2023-01-29  9:55                     ` Gerald Pfeifer
2023-01-29  1:23                   ` [PATCH] Change AVX512FP16 to AVX512-FP16 which is official name liuhongt
2023-01-29  9:55                     ` Gerald Pfeifer

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=20210923053825.89498-1-hongtao.liu@intel.com \
    --to=hongtao.liu@intel.com \
    --cc=gcc-patches@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).