public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christoph Muellner <cmuellner@ventanamicro.com>
To: Jim Wilson <jimw@sifive.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 Kito Cheng <kito.cheng@gmail.com>, jiawei <jiawei@iscas.ac.cn>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Andrew Waterman <andrew@sifive.com>,
	 Philipp Tomsich <philipp.tomsich@vrull.eu>
Subject: Re: [RFC PATCH 0/8] RISC-V: Bit-manipulation extension.
Date: Wed, 29 Sep 2021 00:05:34 +0200	[thread overview]
Message-ID: <CAHYeh+qHpcUtJx-AGQA9cURHYnmCG=iEKEKOX3ZoASy=PtypVw@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVab10g9b-fMatURxUX6RSK6MMeXo8qwhcsma3HHWUzBk0A@mail.gmail.com>

On Wed, Sep 29, 2021 at 12:01 AM Jim Wilson <jimw@sifive.com> wrote:
>
> On Thu, Sep 23, 2021 at 12:57 AM Kito Cheng <kito.cheng@sifive.com> wrote:
>>
>> Bit manipulation extension[1] is finishing the public review and waiting for
>> the rest of the ratification process, I believe that will become a ratified
>> extension soon, so I think it's time to submit to upstream for review now :)
>
>
> We still don't have upstream zbs assembler support.  We have rejected other patches because they didn't upstream the assembler support first.  We should be following the same rule here for bitmanip.
>
> Maybe we can ask PLCT to write the missing assembler support?

We talked about this in the T&R meeting on Monday.
Philipp Tomsich mentioned, that he has a patchset from earlier this
year, which adds support for Zbs.
He proposed to rebase it and send it to the list in the next days.

  reply	other threads:[~2021-09-28 22:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  7:57 Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 1/8] RISC-V: Minimal support of bitmanip extension Kito Cheng
2021-09-27 11:16   ` Christoph Muellner
2021-10-18  8:48     ` Kito Cheng
2021-10-18 10:10       ` Christoph Muellner
2021-10-18 12:15         ` Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 2/8] RISC-V: Implement instruction patterns for ZBA extension Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 3/8] RISC-V: Cost model for zba extension Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 4/8] RISC-V: Implement instruction patterns for ZBB extension Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 5/8] RISC-V: Cost model for zbb extension Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 6/8] RISC-V: Use li and rori to load constants Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 7/8] RISC-V: Implement instruction patterns for ZBS extension Kito Cheng
2021-09-23  7:57 ` [RFC PATCH 8/8] RISC-V: Cost model " Kito Cheng
2021-09-27 11:20 ` [RFC PATCH 0/8] RISC-V: Bit-manipulation extension Christoph Muellner
2021-09-28 22:02   ` Jim Wilson
2021-09-28 22:00 ` Jim Wilson
2021-09-28 22:05   ` Christoph Muellner [this message]
2021-09-28 23:40     ` Jim Wilson
2021-10-13 20:22 ` Vineet Gupta
2021-10-18  3:23   ` Kito Cheng
2021-10-25  9:14     ` Kito Cheng

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='CAHYeh+qHpcUtJx-AGQA9cURHYnmCG=iEKEKOX3ZoASy=PtypVw@mail.gmail.com' \
    --to=cmuellner@ventanamicro.com \
    --cc=andrew@sifive.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jiawei@iscas.ac.cn \
    --cc=jimw@sifive.com \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    /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).