From: Hongtao Liu <crazylht@gmail.com>
To: Haochen Jiang <haochen.jiang@intel.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com
Subject: Re: [PATCH] Add __m128bf16/__m256bf16/__m512bf16 type for bf16 abi test
Date: Tue, 23 Aug 2022 11:01:21 +0800 [thread overview]
Message-ID: <CAMZc-byFi1t=YJsEnDTaSsm6ZEkbnF74TniZqePtU32Xqa9MVA@mail.gmail.com> (raw)
In-Reply-To: <20220822021559.29312-1-haochen.jiang@intel.com>
On Mon, Aug 22, 2022 at 10:16 AM Haochen Jiang via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi all,
>
> This patch added __m128bf16/__m256bf16/__m512bf16 type in testcases.
Ok.
>
> BRs,
> Haochen
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/x86_64/abi/bf16/bf16-helper.h:
> Add _m128bf16/m256bf16/_m512bf16.
> * gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h:
> Include bf16-helper.h.
> ---
> gcc/testsuite/gcc.target/x86_64/abi/bf16/bf16-helper.h | 4 ++++
> .../gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/gcc/testsuite/gcc.target/x86_64/abi/bf16/bf16-helper.h b/gcc/testsuite/gcc.target/x86_64/abi/bf16/bf16-helper.h
> index 83d89fcf62c..e090a7254f4 100644
> --- a/gcc/testsuite/gcc.target/x86_64/abi/bf16/bf16-helper.h
> +++ b/gcc/testsuite/gcc.target/x86_64/abi/bf16/bf16-helper.h
> @@ -1,3 +1,7 @@
> +typedef __bf16 __m128bf16 __attribute__((__vector_size__(16), __aligned__(16)));
> +typedef __bf16 __m256bf16 __attribute__((__vector_size__(32), __aligned__(32)));
> +typedef __bf16 __m512bf16 __attribute__((__vector_size__(64), __aligned__(64)));
> +
> typedef union
> {
> float f;
> diff --git a/gcc/testsuite/gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h b/gcc/testsuite/gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h
> index 8379fcfaf8c..9cd39b878dd 100644
> --- a/gcc/testsuite/gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h
> +++ b/gcc/testsuite/gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h
> @@ -1,4 +1,5 @@
> #include <stdlib.h>
> +#include "../bf16-helper.h"
>
> static void do_test (void);
>
> --
> 2.18.1
>
--
BR,
Hongtao
prev parent reply other threads:[~2022-08-23 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 7:49 [PATCH] x86: Support vector __bf16 type Kong, Lingling
2022-08-17 5:56 ` Hongtao Liu
2022-08-18 7:34 ` [PATCH] Add ABI test for " Haochen Jiang
2022-08-19 0:58 ` Hongtao Liu
2022-08-19 17:30 ` H.J. Lu
2022-08-22 1:02 ` Hongtao Liu
2022-08-22 1:04 ` Hongtao Liu
2022-08-22 2:15 ` [PATCH] Add __m128bf16/__m256bf16/__m512bf16 type for bf16 abi test Haochen Jiang
2022-08-23 3:01 ` Hongtao Liu [this message]
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-byFi1t=YJsEnDTaSsm6ZEkbnF74TniZqePtU32Xqa9MVA@mail.gmail.com' \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=haochen.jiang@intel.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).