public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Xiao Zeng" <zengxiao@eswincomputing.com>
To: kito.cheng <kito.cheng@gmail.com>,  "Andreas Schwab" <schwab@suse.de>
Cc: jeffreyalaw <jeffreyalaw@gmail.com>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Re: [NOT CODE REVIEW] [PATCH v3 1/1] [RISC-V] Add support for _Bfloat16
Date: Thu, 16 May 2024 17:25:44 +0800	[thread overview]
Message-ID: <2024051617254463447211@eswincomputing.com> (raw)
In-Reply-To: <CA+yXCZChxtp+ogbX_70KBmh16QcLmMDHqqetaOvx5rA8GQqWxA@mail.gmail.com>

2024-05-16 16:55  Kito Cheng <kito.cheng@gmail.com> wrote:
>
>Hi Xiao Zeng:
>
>Just wondering why use _Bfloat16 rather than __bf16? you mention
>__bf16 in comment, but implementation use _Bfloat16?
Obviously, this is a mistake.
This patch has spanned a considerable amount of time locally.

I will submit a new patch to correct it.
> I would like to use __bf16 to make it consistent between LLVM and psABI if possible :)
Thanks Kito for pointing out this point. Meanwhile, due to my issue, I did not see
Andreas Schwab's email. He had already sent me an email earlier, pointing out the existing issues.
<https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651529.html>

By the way, if I don't reply to the email in a timely manner, it must be my problem.
Please send me another email to remind me.
I will reset the email to avoid missing any emails

Thanks
Xiao Zeng


      reply	other threads:[~2024-05-16  9:25 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
2024-05-14  8:05     ` Andreas Schwab
2024-05-16  8:55       ` Kito Cheng
2024-05-16  9:25         ` Xiao Zeng [this message]

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=2024051617254463447211@eswincomputing.com \
    --to=zengxiao@eswincomputing.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=schwab@suse.de \
    /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).