From: liuhongt <hongtao.liu@intel.com>
To: gcc-patches@gcc.gnu.org
Cc: gerald@pfeifer.com
Subject: [PATCH] Change AVX512FP16 to AVX512-FP16 which is official name.
Date: Sun, 29 Jan 2023 09:23:52 +0800 [thread overview]
Message-ID: <20230129012352.930881-1-hongtao.liu@intel.com> (raw)
In-Reply-To: <6481635f-dd61-8c06-4841-4e1bf9aa5133@pfeifer.com>
Ready to push to trunk.
---
htdocs/gcc-12/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 30fa4d6e..49055ffe 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -754,7 +754,7 @@ function Multiply (S1, S2 : Sign) return Sign is
<h3 id="x86">IA-32/x86-64</h3>
<ul>
<li>New ISA extension support for Intel AVX512-FP16 was added.
- AVX512FP16 intrinsics are available via the <code>-mavx512fp16</code>
+ AVX512-FP16 intrinsics are available via the <code>-mavx512fp16</code>
compiler switch.
</li>
<li>For both C and C++ the <code>_Float16</code> type is supported on
--
2.31.1
next prev parent reply other threads:[~2023-01-29 1:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 5:38 [PATCH] wwwdocs: [GCC12] Mention Intel AVX512-FP16 liuhongt
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 ` liuhongt [this message]
2023-01-29 9:55 ` [PATCH] Change AVX512FP16 to AVX512-FP16 which is official name 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=20230129012352.930881-1-hongtao.liu@intel.com \
--to=hongtao.liu@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).