public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jin Ma" <jinma@linux.alibaba.com>
To: "wangfeng" <wangfeng@eswincomputing.com>
Cc: "Kito Cheng" <kito.cheng@gmail.com>,
	"juzhe.zhong" <juzhe.zhong@rivai.ai>,
	"jinma.contrib" <jinma.contrib@gmail.com>,
	"zengxiao" <zengxiao@eswincomputing.com>,
	"gcc-patches" <gcc-patches@gcc.gnu.org>,
	"Fei Gao" <gaofei@eswincomputing.com>
Subject: Re: [RE] [v2] RISC-V: Add Zfbfmin extension
Date: Tue, 18 Jun 2024 18:25:45 +0800	[thread overview]
Message-ID: <2ef67064-e44f-4038-a012-6def40f9f833.jinma@linux.alibaba.com> (raw)
In-Reply-To: <202406071734475481603@eswincomputing.com>


Hi, Feng
  Any new developments here on zvfbfmin and zvfbfwma?

BR,
Jin



















------------------------------------------------------------------
From:Fei Gao <gaofei@eswincomputing.com>
Send Time:2024 Jun. 7 (Fri.) 17:34
To:jinma<jinma@linux.alibaba.com>; "gcc-patches"<gcc-patches@gcc.gnu.org>; zengxiao<zengxiao@eswincomputing.com>; wangfeng<wangfeng@eswincomputing.com>
Cc:jeffreyalaw<jeffreyalaw@gmail.com>; Kito Cheng<kito.cheng@gmail.com>; "juzhe.zhong"<juzhe.zhong@rivai.ai>; "jinma.contrib"<jinma.contrib@gmail.com>; jinma<jinma@linux.alibaba.com>
Subject:Re: [RE] [v2] RISC-V: Add Zfbfmin extension







Hi Jin


We have completed zvfbfmin and zvfbfwma in GCC. 
Wang Feng will post after dragon boat festival. 


BR, 
Fei
From: Jin Ma
Date: 2024-06-07 15:35
To: gcc-patches; zengxiao
CC: jeffreyalaw; kito.cheng; juzhe.zhong; jinma.contrib; Jin Ma
Subject: [RE] [v2] RISC-V: Add Zfbfmin extension

Hi,
 
Is there a plan to implement zvfbfmin and zvfbfwma? Or how can I get the relevant patches
in advance for testing? By the way, The LLVM seems to be fully implemented now :-)
 
Ref:
 
https://github.com/riscv-non-isa/rvv-intrinsic-doc/pull/293
 
https://github.com/riscv-non-isa/rvv-intrinsic-doc/blob/main/auto-generated/bfloat16/intrinsic_funcs.adoc
 
 
 
Thanks,
Jin





  reply	other threads:[~2024-06-18 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01  7:45 [PATCH v2] " Xiao Zeng
2024-06-03 20:30 ` Jeff Law
2024-06-05  1:11   ` [COMMITTED] " Xiao Zeng
2024-06-07  7:35 ` [RE] [v2] " Jin Ma
2024-06-07  9:34   ` Fei Gao
2024-06-18 10:25     ` Jin Ma [this message]
2024-06-19  0:18       ` wangfeng
2024-06-19  2:45         ` Jin Ma

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=2ef67064-e44f-4038-a012-6def40f9f833.jinma@linux.alibaba.com \
    --to=jinma@linux.alibaba.com \
    --cc=gaofei@eswincomputing.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jinma.contrib@gmail.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=wangfeng@eswincomputing.com \
    --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).