From: Nelson Chu <nelson.chu@sifive.com>
To: binutils@sourceware.org, jimw@sifive.com, andrew@sifive.com
Subject: [integration v2 0/4] RISC-V/rvv: Update rvv from v01.0 to v1.0
Date: Tue, 5 Oct 2021 05:51:02 -0700 [thread overview]
Message-ID: <20211005125106.18038-1-nelson.chu@sifive.com> (raw)
Hi Guys,
There are four patches used to update the rvv from v1.0 to 1.0,
* [integration v2 1/4] RISC-V/rvv: Added assembly pseudo and changed assembler mnemonics.
* [integration v2 2/4] RISC-V/rvv: Update constraints for widening and narrowing instructions.
* [integration v2 3/4] RISC-V/rvv: Separate zvamo from v, and removed the zvlsseg extension name.
* [integration v2 4/4] RISC-V/rvv: Added zve* and zvl* extensions, and clarify the imply rules.
I still send the rvv patches to integration branch, since it should be
easier to review. After the reviewing, I will merge the whole rvv patches
into the one, and then move it from the integration branch to mainline,
since the rvv v1.0 is frozen and at the public review stage for now.
Thanks
Nelson
next reply other threads:[~2021-10-05 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 12:51 Nelson Chu [this message]
2021-10-05 12:51 ` [integration v2 1/4] RISC-V/rvv: Added assembly pseudo and changed assembler mnemonics Nelson Chu
2021-10-05 12:51 ` [integration v2 2/4] RISC-V/rvv: Update constraints for widening and narrowing instructions Nelson Chu
2021-10-05 12:51 ` [integration v2 3/4] RISC-V/rvv: Separate zvamo from v, and removed the zvlsseg extension name Nelson Chu
2021-10-05 12:51 ` [integration v2 4/4] RISC-V/rvv: Added zve* and zvl* extensions, and clarify the imply rules Nelson Chu
2021-10-25 6:04 ` [integration v2 0/4] RISC-V/rvv: Update rvv from v01.0 to v1.0 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=20211005125106.18038-1-nelson.chu@sifive.com \
--to=nelson.chu@sifive.com \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jimw@sifive.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).