From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) by sourceware.org (Postfix) with ESMTPS id D92CF3858C52 for ; Thu, 3 Nov 2022 07:57:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D92CF3858C52 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-yb1-xb2a.google.com with SMTP id z192so1368631yba.0 for ; Thu, 03 Nov 2022 00:57:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vNg7Jf6Bguq5TQRYIfuq/FXvNy7EEy2n9ZBNqWBUlF8=; b=PTA8v5D6USOzatCFMWNrWhozT5U8qAKo/me0XIkNZsZ0hCSqyU1ehHbhdfiafmDzcF dMs5pDL3Afz1ETxxj5sl8K9Yz8PUFe+O9zG3N1HcN8c8cQzHZ5/arIYLB8TRTWTJR9qO HteGjPb/toRfB0nBhukI36rqaviJ2LlLP9s5y2NkcbcTVnTlERI3ixAKGxnhJvQEeQQo r+hG2cU8AoNlg2QjoSkk7PBGNrAtAbwZWi87//1QleUh/xcFYfjL7TTzRZaGadClP9qZ yFQePXV6QBtcF6Sx83+n8ILz0e2ZsrwcJWWFaURoROOQwjOzRvUBoZFNOKNkN0R/zzmP XYFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vNg7Jf6Bguq5TQRYIfuq/FXvNy7EEy2n9ZBNqWBUlF8=; b=ODuAYmbMbpeF9fn0oW7Q18nwW6DpOVjgBX409v3eJk3HFsLEq6THFCRVCxQofhY1rv PT4gkWAwCoFe4+/njqroS+BZOJ8zO2GXm5lxWdvov+2M3dXNQlKIMRxaU5ruoqFAvK3+ 1CdvWbMvTv+QeElc8OytJX5i9rsHT1F1LWrvoEVNdAbD2qYH1oJfPPJFmmp15faOo0u6 ul1Qmh8+K2j1nfMwSuLQYUSWfrbPy11+UvX8yOaag7gZXeupOA8wU6/pj/HIeSGjZPGv 7L/hfuC3eHSE+Bk3tBDFxLjdXksG0rgFGt2+bQToDew5DIK3om9cHUPqR1+HPD6cTjC2 PBTQ== X-Gm-Message-State: ACrzQf0lkRQfhoPGI/HWwFkkjpioK15nZAgUGVdJ9TPrTkqulKpehf8C wigAAGK0plOaC77eTivJ+g1QJO+VgKKIVMpjDZg= X-Google-Smtp-Source: AMsMyM6lh3OPpgxEKpnHKvEzM/dX0z3vlBNhhb27Mol6fZpHObRaY4nVgX4/YlCjX6Hpd0g+HKbdwcSa0+ATvNKw82Q= X-Received: by 2002:a05:6902:102f:b0:6d1:6170:2934 with SMTP id x15-20020a056902102f00b006d161702934mr845042ybt.92.1667462252186; Thu, 03 Nov 2022 00:57:32 -0700 (PDT) MIME-Version: 1.0 References: <20221101011756.3818109-1-lingling.kong@intel.com> In-Reply-To: From: Hongtao Liu Date: Thu, 3 Nov 2022 15:57:20 +0800 Message-ID: Subject: Re: [wwwdocs] [GCC13] Mention Intel __bf16 support in AVX512BF16 intrinsics. To: "Kong, Lingling" Cc: "Liu, Hongtao" , "gcc-patches@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-7.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,GIT_PATCH_0,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, Nov 3, 2022 at 2:53 PM Kong, Lingling wrote: > > > > > 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.

> > > >
  • For both C and C++ the __bf16 type is supported on > > > > x86 systems with SSE2 and above enabled. > > > >
    • > > > > +
  • Use __bf16 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. > > > > +
    • > > > > > > > > > > > > > > > > -- > > > > 2.18.2 > > > > > > Yes, changed it. Thanks a lot! > > > > Subject: [PATCH] Mention Intel __bf16 support in AVX512BF16 intrinsics. > > > > --- > > htdocs/gcc-13/changes.html | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index > > 7c6bfa6e..a35f4fab 100644 > > --- a/htdocs/gcc-13/changes.html > > +++ b/htdocs/gcc-13/changes.html > > @@ -230,6 +230,12 @@ a work-in-progress.

    > >
  • For both C and C++ the __bf16 type is supported on > > x86 systems with SSE2 and above enabled. > >
    • > > +
  • Use __bf16 type for AVX512BF16 intrinsics. > > + Previously we use short to represent bf16. Now we introduced > > __bf16 to x86 psABI. > > + So we switch intrinsics in AVX512BF16 to the new type __bf16. > > + When users compile the same source code contains AVX512BF16 > > + intrinsics with > > + GCC13 need to support SSE2, which is different to GCC12 (and before). > > +
    • > > > > > > > > -- > > 2.18.2 > > > > BRs, > > Lingling > > Sorry, modified again. New patch is as below. Ok, thanks. > > htdocs/gcc-13/changes.html | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 7c6bfa6e..7a5d2ab6 100644 > --- a/htdocs/gcc-13/changes.html > +++ b/htdocs/gcc-13/changes.html > @@ -230,6 +230,11 @@ a work-in-progress.

    >
  • For both C and C++ the __bf16 type is supported on > x86 systems with SSE2 and above enabled. >
    • > +
  • Use real __bf16 type for AVX512BF16 intrinsics. > + Previously we use __bfloat16 which is typedef of short. Now we > + introduced real __bf16 type to x86 psABI. Users need to > + adjust their AVX512BF16-related source code when upgrading GCC12 to GCC13. > +
    • > > > > -- > 2.18.2 > > BRs, > Lingling -- BR, Hongtao