From: Kito Cheng <kito.cheng@sifive.com>
To: Vineet Gupta <vineetg@rivosinc.com>
Cc: Nelson Chu <nelson.chu@sifive.com>,
Jan Beulich <jbeulich@suse.com>,
Binutils <binutils@sourceware.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Jim Wilson <jimw@sifive.com>
Subject: Re: [PATCH v3 4/4] RISC-V: Support aliases for Zbs instructions
Date: Thu, 28 Oct 2021 16:08:01 +0800 [thread overview]
Message-ID: <CALLt3TjjN2=oTXT-HX1rV0x=5y9GDQj9BQ=wBvko5cNJGFBdjg@mail.gmail.com> (raw)
In-Reply-To: <1ac21974-e519-81b6-2a44-71eafff40398@rivosinc.com>
Hi Vineet:
> Awesome, thx for that. I saw earlier that it has vector stuff in there
> too - Last month Jim had some concerns [1] about vector support in gcc,
> how is that coming along ?
My plan is only to add minimal support for RVV on GCC before next GCC release,
As Jim mentioned we didn't invest RVV intrinsic function on GCC, but
for glibc support,
that only requires minimal support on GCC.
next prev parent reply other threads:[~2021-10-28 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 20:26 [PATCH v3 1/4] RISC-V: Split Zb[abc] into commented sections Philipp Tomsich
2021-10-06 20:26 ` [PATCH v3 2/4] RISC-V: Update extension version for Zb[abc] to 1.0.0 Philipp Tomsich
2021-10-07 4:02 ` Nelson Chu
2021-10-06 20:26 ` [PATCH v3 3/4] RISC-V: Add support for Zbs instructions Philipp Tomsich
2021-10-07 4:02 ` Nelson Chu
2021-10-07 6:57 ` Jan Beulich
2021-10-07 11:51 ` Delivery delayed:Re: " postmaster
2021-10-06 20:26 ` [PATCH v3 4/4] RISC-V: Support aliases " Philipp Tomsich
2021-10-07 4:05 ` Nelson Chu
2021-10-07 6:58 ` Jan Beulich
2021-10-07 9:13 ` Nelson Chu
2021-10-27 23:54 ` Vineet Gupta
2021-10-28 2:28 ` Nelson Chu
2021-10-28 3:24 ` Vineet Gupta
2021-10-28 8:08 ` Kito Cheng [this message]
2021-10-07 11:06 ` Delivery delayed:Re: " postmaster
2021-10-07 4:01 ` [PATCH v3 1/4] RISC-V: Split Zb[abc] into commented sections Nelson Chu
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='CALLt3TjjN2=oTXT-HX1rV0x=5y9GDQj9BQ=wBvko5cNJGFBdjg@mail.gmail.com' \
--to=kito.cheng@sifive.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jimw@sifive.com \
--cc=nelson.chu@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=vineetg@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).