From: Jeff Law <jeffreyalaw@gmail.com>
To: Xiao Zeng <zengxiao@eswincomputing.com>, gcc-patches@gcc.gnu.org
Subject: Re: [NOT CODE REVIEW] [PATCH v3 1/1] [RISC-V] Add support for _Bfloat16
Date: Mon, 6 May 2024 15:40:39 -0600 [thread overview]
Message-ID: <379b6dfc-5979-4a63-8e74-ecbc670f14cc@gmail.com> (raw)
In-Reply-To: <20240506003845.70280-2-zengxiao@eswincomputing.com>
On 5/5/24 6:38 PM, Xiao Zeng wrote:
> 1 At point <https://github.com/riscv/riscv-bfloat16>,
> BF16 has already been completed "post public review".
>
> 2 LLVM has also added support for RISCV BF16 in
> <https://reviews.llvm.org/D151313> and
> <https://reviews.llvm.org/D150929>.
>
> 3 According to the discussion <https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/367>,
> this use __bf16 and use DF16b in riscv_mangle_type like x86.
>
> Below test are passed for this patch
> * The riscv fully regression test.
>
> gcc/ChangeLog:
>
> * config/riscv/iterators.md: New mode iterator HFBF.
> * config/riscv/riscv-builtins.cc (riscv_init_builtin_types):
> Initialize data type _Bfloat16.
> * config/riscv/riscv-modes.def (FLOAT_MODE): New.
> (ADJUST_FLOAT_FORMAT): New.
> * config/riscv/riscv.cc (riscv_mangle_type): Support for BFmode.
> (riscv_scalar_mode_supported_p): Ditto.
> (riscv_libgcc_floating_mode_supported_p): Ditto.
> (riscv_init_libfuncs): Set the conversion method for BFmode and
> HFmode.
> (riscv_block_arith_comp_libfuncs_for_mode): Set the arithmetic
> and comparison libfuncs for the mode.
> * config/riscv/riscv.md (mode" ): Add BF.
> (movhf): Support for BFmode.
> (mov<mode>): Ditto.
> (*movhf_softfloat): Ditto.
> (*mov<mode>_softfloat): Ditto.
>
> libgcc/ChangeLog:
>
> * config/riscv/sfp-machine.h (_FP_NANFRAC_B): New.
> (_FP_NANSIGN_B): Ditto.
> * config/riscv/t-softfp32: Add support for BF16 libfuncs.
> * config/riscv/t-softfp64: Ditto.
> * soft-fp/floatsibf.c: For si -> bf16.
> * soft-fp/floatunsibf.c: For unsi -> bf16.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/bf16_arithmetic.c: New test.
> * gcc.target/riscv/bf16_call.c: New test.
> * gcc.target/riscv/bf16_comparison.c: New test.
> * gcc.target/riscv/bf16_float_libcall_convert.c: New test.
> * gcc.target/riscv/bf16_integer_libcall_convert.c: New test.
Given we were only looking to have the CI system check the formatting
nit and that has passed. I've pushed this to the trunk.
jeff
next prev parent reply other threads:[~2024-05-06 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 0:38 [NOT CODE REVIEW] [PATCH v3 0/1] " Xiao Zeng
2024-05-06 0:38 ` [NOT CODE REVIEW] [PATCH v3 1/1] " Xiao Zeng
2024-05-06 21:40 ` Jeff Law [this message]
2024-05-14 8:05 ` Andreas Schwab
2024-05-16 8:55 ` Kito Cheng
2024-05-16 9:25 ` Xiao Zeng
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=379b6dfc-5979-4a63-8e74-ecbc670f14cc@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=zengxiao@eswincomputing.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).