public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: "Kong, Lingling" <lingling.kong@intel.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"Liu, Hongtao" <hongtao.liu@intel.com>
Subject: Re: [wwwdocs] [GCC13] Mention Intel __bf16 support in AVX512BF16 intrinsics.
Date: Tue, 1 Nov 2022 09:28:42 +0800	[thread overview]
Message-ID: <CAMZc-by8ofrNkie-xencwoGZB4AFoekTPUn+LAaORWcNx1kKEg@mail.gmail.com> (raw)
In-Reply-To: <DM4PR11MB5487305F99BDE4F531490D69EC369@DM4PR11MB5487.namprd11.prod.outlook.com>

On Tue, Nov 1, 2022 at 9:21 AM Kong, Lingling via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi
>
> The patch is for mention Intel __bf16 support in AVX512BF16 intrinsics.
> Ok for master ?
>
> Thanks,
> Lingling
>
> ---
>  htdocs/gcc-13/changes.html | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 7c6bfa6e..cd0282f1 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -230,6 +230,8 @@ a work-in-progress.</p>
>    <li>For both C and C++ the <code>__bf16</code> type is supported on
>        x86 systems with SSE2 and above enabled.
>    </li>
> +  <li>Use <code>__bf16</code> type for AVX512BF16 intrinsics.
Could you add more explanations. Like originally it's ..., now it's
..., and what's the difference when users compile the same source
code(which contains avx512bf16 intrinsics) with gcc12(and before) and
GCC13.
> +  </li>
>  </ul>
>
>  <!-- <h3 id="mips">MIPS</h3> -->
> --
> 2.18.2
>


-- 
BR,
Hongtao

  reply	other threads:[~2022-11-01  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221101011756.3818109-1-lingling.kong@intel.com>
2022-11-01  1:20 ` Kong, Lingling
2022-11-01  1:28   ` Hongtao Liu [this message]
2022-11-02  2:15     ` Kong, Lingling
2022-11-03  6:52       ` Kong, Lingling
2022-11-03  7:57         ` 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:
  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-by8ofrNkie-xencwoGZB4AFoekTPUn+LAaORWcNx1kKEg@mail.gmail.com \
    --to=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hongtao.liu@intel.com \
    --cc=lingling.kong@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).