public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Kong Lingling <konglin1@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d41f7632f1b6f0fbdebb5b7c9ef27055264b4018
Date: Thu,  3 Nov 2022 09:43:08 +0000 (GMT)	[thread overview]
Message-ID: <20221103094308.275E63858D39@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  d41f7632f1b6f0fbdebb5b7c9ef27055264b4018 (commit)
      from  b3a5eb89800f8683b2c9f37c70954d517b8c0b9a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d41f7632f1b6f0fbdebb5b7c9ef27055264b4018
Author: konglin1 <lingling.kong@intel.com>
Date:   Tue Nov 1 09:17:18 2022 +0800

    gcc-13: Mention Intel __bf16 support in AVX512BF16 intrinsics.

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 5e6e054b..f5fa97e5 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -230,6 +230,11 @@ 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 real <code>__bf16</code> type for AVX512BF16 intrinsics. Previously
+  we use __bfloat16 which is typedef of short. Now we introduced real
+  <code>__bf16</code> type to x86 psABI. Users need to adjust their
+  AVX512BF16-related source code when upgrading GCC12 to GCC13.
+  </li>
 </ul>
 
 <!-- <h3 id="mips">MIPS</h3> -->

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-13/changes.html | 5 +++++
 1 file changed, 5 insertions(+)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2022-11-03  9:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221103094308.275E63858D39@sourceware.org \
    --to=konglin1@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).