From: yulong <shiyulong@iscas.ac.cn>
To: Jeff Law <jeffreyalaw@gmail.com>, libc-alpha@sourceware.org
Cc: palmer@dabbelt.com, darius@bluespec.com, andrew@sifive.com,
maskray@google.com, kito.cheng@sifive.com, wuwei2016@iscas.ac.cn,
jiawei@iscas.ac.cn, shihua@iscas.ac.cn, chenyixuan@iscas.ac.cn
Subject: Re: [RFC V4] Enable libmvec support for RISC-V
Date: Mon, 29 Apr 2024 09:12:47 +0800 [thread overview]
Message-ID: <771311da-76fd-41d6-8f87-b60a0940db95@iscas.ac.cn> (raw)
In-Reply-To: <ed1a89d4-d3fb-49fe-b776-aec2ea8023e9@gmail.com>
在 2024/4/25 13:07, Jeff Law 写道:
>
>
> On 4/15/24 1:21 AM, shiyulong@iscas.ac.cn wrote:
>> From: yulong <shiyulong@iscas.ac.cn>
>>
>> Diff: Chande the version from GLIBC_2.39 to GLIBC_2.40.
>> This patch tries to enable libmvec on RISC-V. I also have demonstrated
>> how this all fits together by adding implementations for vector cos.
>> This patch is a try and we hope to receive valuable comments.
> Just an FYI -- Palmer's team over at Rivos have implementations for a
> number of routines that would fit into libmvec. You might reach out
> to Ping Tak Peter Tang <ptpt@rivosinc.com> for information in his
> implementation.
>
>> https://github.com/rivosinc/veclibm/
>
>
> THeir implementations may provide good guidance on performant
> implementations of various routines that libmvec typically provides.
>
> jeff
Thanks Jeff for your advice, I'm working on a new implementation after
reading the above code.
next prev parent reply other threads:[~2024-04-29 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 7:21 shiyulong
2024-04-25 5:07 ` Jeff Law
2024-04-29 1:12 ` yulong [this message]
2024-04-30 16:26 ` Palmer Dabbelt
2024-05-10 13:06 ` yulong
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=771311da-76fd-41d6-8f87-b60a0940db95@iscas.ac.cn \
--to=shiyulong@iscas.ac.cn \
--cc=andrew@sifive.com \
--cc=chenyixuan@iscas.ac.cn \
--cc=darius@bluespec.com \
--cc=jeffreyalaw@gmail.com \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.com \
--cc=palmer@dabbelt.com \
--cc=shihua@iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
/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).