public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: Haochen Jiang <haochen.jiang@intel.com>,
	Hongtao Liu <hongtao.liu@intel.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add ABI test for __bf16 type
Date: Fri, 19 Aug 2022 10:30:30 -0700	[thread overview]
Message-ID: <CAMe9rOqsxcQneuwgEh-Ksxh6KNUuSh4Bdm4BSp=XKuCQXz2BBw@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-by_zh7NgxOweuRJA=cSHX6pGLMqMmh6JYbqLRiGwQP36A@mail.gmail.com>

On Thu, Aug 18, 2022 at 5:56 PM Hongtao Liu via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> On Thu, Aug 18, 2022 at 3:36 PM Haochen Jiang via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > Hi all,
> >
> > This patch aims to add bf16 abi test after the whole __bf16 type is added.
> >
> > Regtested on x86_64-pc-linux-gnu. Ok for trunk?
> Ok.

All BF16 ABI tests failed due to missing __m128bf16/__m256bf16/__m512bf16.
When will __bf16 types be added?

> >
> > BRs,
> > Haochen
> >
> > gcc/testsuite/ChangeLog:
> >
> >         * gcc.target/x86_64/abi/bf16/abi-bf16.exp: New test.
> >         * gcc.target/x86_64/abi/bf16/args.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/asm-support.S: Ditto.
> >         * gcc.target/x86_64/abi/bf16/bf16-check.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/bf16-helper.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/defines.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/abi-bf16-ymm.exp: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/args.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/asm-support.S: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/bf16-ymm-check.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/test_m256_returning.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/test_passing_m256.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/test_passing_structs.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/test_passing_unions.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m256bf16/test_varargs-m256.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/abi-bf16-zmm.exp: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/args.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/asm-support.S: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/bf16-zmm-check.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/test_m512_returning.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/test_passing_m512.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/test_passing_structs.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/test_passing_unions.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/m512bf16/test_varargs-m512.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/macros.h: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_3_element_struct_and_unions.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_alignment.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_array_size_and_align.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_returning.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_sizes.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_struct_size_and_align.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_basic_union_size_and_align.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_m128_returning.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_passing_floats.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_passing_m128.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_passing_structs.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_passing_unions.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_struct_returning.c: Ditto.
> >         * gcc.target/x86_64/abi/bf16/test_varargs-m128.c: Ditto.



-- 
H.J.

  reply	other threads:[~2022-08-19 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  7:49 [PATCH] x86: Support vector " 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 [this message]
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

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='CAMe9rOqsxcQneuwgEh-Ksxh6KNUuSh4Bdm4BSp=XKuCQXz2BBw@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=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).