diff mbox series

[wwwdocs,GCC13] Mention Intel __bf16 support in AVX512BF16 intrinsics.

Message ID DM4PR11MB5487305F99BDE4F531490D69EC369@DM4PR11MB5487.namprd11.prod.outlook.com
State New
Headers
Series [wwwdocs,GCC13] Mention Intel __bf16 support in AVX512BF16 intrinsics. |

Commit Message

Li, Pan2 via Gcc-patches Nov. 1, 2022, 1:20 a.m. UTC 
  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(+)

--
2.18.2

Comments

Hongtao Liu Nov. 1, 2022, 1:28 a.m. UTC | #1 
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
>
Li, Pan2 via Gcc-patches Nov. 2, 2022, 2:15 a.m. UTC | #2 
> > 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
> >
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.</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. Previously we use
+  short to represent bf16. Now we introduced <code>__bf16</code> to x86 psABI.
+  So we switch intrinsics in AVX512BF16 to the new type <code>__bf16</code>.
+  When users compile the same source code contains AVX512BF16 intrinsics with
+  GCC13 need to support SSE2, which is different to GCC12 (and before).
+  </li>
 </ul>

 <!-- <h3 id="mips">MIPS</h3> -->
--
2.18.2

BRs,
Lingling
Li, Pan2 via Gcc-patches Nov. 3, 2022, 6:52 a.m. UTC | #3 
> > > 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
> > >
> 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.</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.
> + Previously we use  short to represent bf16. Now we introduced
> <code>__bf16</code> to x86 psABI.
> +  So we switch intrinsics in AVX512BF16 to the new type <code>__bf16</code>.
> +  When users compile the same source code contains AVX512BF16
> + intrinsics with
> +  GCC13 need to support SSE2, which is different to GCC12 (and before).
> +  </li>
>  </ul>
> 
>  <!-- <h3 id="mips">MIPS</h3> -->
> --
> 2.18.2
> 
> BRs,
> Lingling

Sorry, modified again. New patch is as below.

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.</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> -->
--
2.18.2

BRs,
Lingling
Hongtao Liu Nov. 3, 2022, 7:57 a.m. UTC | #4 
On Thu, Nov 3, 2022 at 2:53 PM Kong, Lingling <lingling.kong@intel.com> 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.</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
> > > >
> > 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.</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.
> > + Previously we use  short to represent bf16. Now we introduced
> > <code>__bf16</code> to x86 psABI.
> > +  So we switch intrinsics in AVX512BF16 to the new type <code>__bf16</code>.
> > +  When users compile the same source code contains AVX512BF16
> > + intrinsics with
> > +  GCC13 need to support SSE2, which is different to GCC12 (and before).
> > +  </li>
> >  </ul>
> >
> >  <!-- <h3 id="mips">MIPS</h3> -->
> > --
> > 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.</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> -->
> --
> 2.18.2
>
> BRs,
> Lingling
diff mbox series

Patch

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.
+  </li>
 </ul>
 
 <!-- <h3 id="mips">MIPS</h3> -->