From: Vineet Gupta <vineetg@rivosinc.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Jan Beulich <jbeulich@suse.com>,
Kito Cheng <kito.cheng@sifive.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: Wed, 27 Oct 2021 20:24:09 -0700 [thread overview]
Message-ID: <1ac21974-e519-81b6-2a44-71eafff40398@rivosinc.com> (raw)
In-Reply-To: <CAJYME4HPaGciV=8Sqr6HJZ9-SEyvDMSVcnDAf37mpGArpMcNLg@mail.gmail.com>
Hi Nelson,
On 10/27/21 7:28 PM, Nelson Chu wrote:
> Hi Vineet,
>
> On Thu, Oct 28, 2021 at 7:54 AM Vineet Gupta <vineetg@rivosinc.com> wrote:
>> Hi Nelson, Kito, Jim
>>
>> Will it be possible to backport these 4 patches to
>> upstream/user/riscv/binutils-integration-branch.
> I have rebased the integration branch until 20211027, so it should
> include the v1.0 zba, zbb, zbc and zbs extensions for now.
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 ?
>> That way it becomes a single place where we could use all bleeding edge
>> features rather than downstream users/companies having to maintain forks ?
> Yes, this is the main purpose of the integration branch. However, I'm
> thinking about how to make maintenance more convenient for everyone,
> both in the mainline and integration branch. Perhaps it will be
> better that we move the released vendor stuff from the integration
> branch to the mainline, so that all the released things are maintained
> in the mainline, and they should be stable enough and must consider
> the compatible issues.
Totally agree.
> But for the integration branch, it will only
> have the purpose of temporarily putting the draft extensions, maybe we
> could also try to move them back to mainline, just that we could drop
> the draft things directly once they are updated. In other words, we
> only keep the implementation of the extensions if their versions are
> at least v1.0 (released), otherwise, we could drop them (< v1.0) and
> always keep the newest one.
Great, I'd say we run with this approach.
Thx,
-Vineet
[1] https://sourceware.org/pipermail/libc-alpha/2021-September/131051.html
next prev parent reply other threads:[~2021-10-28 3:24 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 [this message]
2021-10-28 8:08 ` Kito Cheng
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=1ac21974-e519-81b6-2a44-71eafff40398@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jimw@sifive.com \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.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).