Kito Cheng kito.cheng@gmail.com
Wed Jul 8 09:47:23 GMT 2020

• Previous message (by thread): [PATCH] RISC-V: Branches of vector extension are not merged into binutils mainline
• Next message (by thread): [PATCH] RISC-V: Branches of vector extension are not merged into binutils mainline
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hi Jojo:

I am not the maintainer for binutils, but I think the consensus
between RISC-V GNU toolchain maintainer is don't upstream any
non-ratified extension, so the timing for upstream RISC-V vector
extension is when vector extension reaches version 1.9 or 2.0.


On Wed, Jul 8, 2020 at 3:25 PM <jiejie_rong@c-sky.com> wrote:
>
> Hi Kito,
>
> Some of vector spec versions are stable for using in productions as official says :
>         This is a draft of a stable proposal for the vector
>         specification to be used for implementation and evaluation. Once the
>         draft label is removed, version 0.7 is intended to be stable enough to
>         begin developing toolchains, functional simulators, and initial
>         implementations, though will continue to evolve with minor changes and
>         updates.
>
> I can not find any code in the binutils mainline :(
>
> Is there any plan to merge these branches into binutils mainline ?
>
> —Jojo

---

• Previous message (by thread): [PATCH] RISC-V: Branches of vector extension are not merged into binutils mainline
• Next message (by thread): [PATCH] RISC-V: Branches of vector extension are not merged into binutils mainline
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list