From: Liao Shihua <shihua@iscas.ac.cn>
To: Jin Ma <jinma@linux.alibaba.com>, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com
Subject: Re: [RFC] RISC-V: Support risc-v bfloat16 This patch support bfloat16 in riscv like x86_64 and arm.
Date: Thu, 1 Jun 2023 17:07:55 +0800 [thread overview]
Message-ID: <f8106b69-7ec1-edb4-647e-eedf08d07346@iscas.ac.cn> (raw)
In-Reply-To: <20230601065110.1308-1-jinma@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Hi, Ma Jin
1. There are few developments since May in GCC because the spec of
Zfbf <https://github.com/riscv/riscv-bfloat16> is constantly changing.
2. We (PLCT lab) will implement Zvfbfmin and Zvfbfwma after Zvfh
has been merged in GCC.
3. I will send a patch to support bfloat16_t in RISC-V port, but
Zfbf extension's patch will be sent after it released.
Liao Shihua
在 2023/6/1 14:51, Jin Ma 写道:
> hi,
>
> Are there any new developments about Zfb? Are there any plans to implement
> the Zvfbfmin and Zvfbfwma expansion? I see that Zfb is being reviewed in
> llvm, maybe we should do the same on gcc.
>
> Ref:https://reviews.llvm.org/D151313
> https://reviews.llvm.org/D150929
next prev parent reply other threads:[~2023-06-01 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 9:12 Liao Shihua
2023-04-25 13:23 ` Kito Cheng
2023-06-01 6:51 ` Jin Ma
[not found] ` <MW5PR11MB59081DA700F563D0DD24161FA9499@MW5PR11MB5908.namprd11.prod.outlook.com>
2023-06-01 7:01 ` FW: " juzhe.zhong
2023-06-01 16:48 ` Jeff Law
2023-06-01 16:56 ` Palmer Dabbelt
2023-06-01 17:53 ` Jeff Law
2023-06-01 16:59 ` Philipp Tomsich
2023-06-01 9:07 ` Liao Shihua [this message]
2023-06-15 7:51 ` Jin Ma
2023-06-15 9:52 ` Jin Ma
2023-06-17 15:31 ` Jeff Law
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=f8106b69-7ec1-edb4-647e-eedf08d07346@iscas.ac.cn \
--to=shihua@iscas.ac.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=jinma@linux.alibaba.com \
--cc=kito.cheng@gmail.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).