public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org,
	jinma@linux.alibaba.com, Kito.cheng@sifive.com
Subject: Re: FW: [RFC] RISC-V: Support risc-v bfloat16 This patch support bfloat16 in riscv like x86_64 and arm.
Date: Thu, 1 Jun 2023 11:53:36 -0600	[thread overview]
Message-ID: <587e1260-fdeb-ea02-dae4-26fbcb3a37e4@gmail.com> (raw)
In-Reply-To: <mhng-8d5cd709-d237-486b-b6f0-55a700cc5089@palmer-ri-x1c9>



On 6/1/23 10:56, Palmer Dabbelt wrote:
> On Thu, 01 Jun 2023 09:48:47 PDT (-0700), jeffreyalaw@gmail.com wrote:
>>
>>
>> On 6/1/23 01:01, juzhe.zhong@rivai.ai wrote:
>>> I plan to implement BF16 vector in GCC but still waiting for ISA
>>> ratified since GCC policy doesn't allow un-ratified ISA.
>> Right.  So those specs need to move along further before we can start
>> integrating code.
>>
>>>
>>> Currently, we are working on INT8,INT16,INT32,INT64,FP16,FP32,FP64
>>> auto-vectorizaiton.
>>> It should very simple BF16 in current vector framework in GCC.
>> In prior architectures I've worked on the bulk of BF16 work was just
>> adding additional entries to existing iterators.  So I agree, it should
>> be very simple :-)
> 
> We should also have someone who's a bit more plugged in to floating 
> point check to make sure the RISC-V bfloat16 semantics match IEEE.  I 
> don't see any issues, but I'm not really a FP person so I'm not sure. 
> There were certainly a lot of subtlies for the other FP bits, so even if 
> the implementation just plumbs straight through IMO it's worth checking.
> 
> We have one FP person at Rivos, I can try and rope him in if you want? 
> Happy to have someone else do it, though, as he's usually pretty busy ;)
I don't really have an FP expert here.  I can't honestly pretend to be 
one myself.

jeff

  reply	other threads:[~2023-06-01 17:53 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 [this message]
2023-06-01 16:59         ` Philipp Tomsich
2023-06-01  9:07   ` Liao Shihua
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=587e1260-fdeb-ea02-dae4-26fbcb3a37e4@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=Kito.cheng@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jinma@linux.alibaba.com \
    --cc=juzhe.zhong@rivai.ai \
    --cc=palmer@rivosinc.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).