From: Hongtao Liu <crazylht@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, liuhongt <hongtao.liu@intel.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [GCC12] Mention Intel AVX512-FP16 and _Float16 support.
Date: Fri, 8 Oct 2021 09:25:41 +0800 [thread overview]
Message-ID: <CAMZc-bxG1A_uqPdHtmKyAb_hBbuuorfTb8ffu-Rqv2KQ6f5OUw@mail.gmail.com> (raw)
In-Reply-To: <6feb6e5-878c-93ee-61ee-adb2b0c8e979@pfeifer.com>
On Fri, Oct 1, 2021 at 6:13 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Fri, 24 Sep 2021, Hongtao Liu via Gcc-patches wrote:
> > + <li>New ISA extension support for Intel AVX512-FP16 was added to GCC.
> > + AVX512FP16 intrinsics are available [...]
>
> So, is it AVX512-FP16 or AVX512FP16?
Sorry for the confusion, the official name is AVX512-FP16[1], and for
simplicity, AVX512FP16 is used in the mail thread.
[1] https://software.intel.com/content/www/us/en/develop/download/intel-avx512-fp16-architecture-specification.html
>
> Gerald
--
BR,
Hongtao
next prev parent reply other threads:[~2021-10-08 1:19 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 [this message]
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=CAMZc-bxG1A_uqPdHtmKyAb_hBbuuorfTb8ffu-Rqv2KQ6f5OUw@mail.gmail.com \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=hjl.tools@gmail.com \
--cc=hongtao.liu@intel.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).