[PATCH] RISC-V: Branches of vector extension are not merged into binutils mainline

[jiejie_rong@c-sky.com]

Hi,

	From version rule of RISCV extension, we should include stable version from the first v0.7.1,

	riscv official announce that stable version can be used for implementation and evaluation.

	We could set the latest as default and absorb other implementation who follow the old vector spec also :)

—Jojo
在 2020年7月8日 +0800 PM5:47，Kito Cheng <kito.cheng@gmail.com>，写道：
> 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