On Sat, Apr 30, 2022 at 2:31 PM Anup Patel wrote:
>
> On Sat, Apr 30, 2022 at 8:39 AM Frank Chang wrote:
> >
> > Hi Anup,
> >
> > If we want to limit the generated ISA string to/after a specific privilege
> > spec version.
> > Shouldn't we also check the privilege spec version when these
On Sat, Apr 30, 2022 at 12:30 PM Anup Patel wrote:
> On Sat, Apr 30, 2022 at 8:39 AM Frank Chang
> wrote:
> >
> > Hi Anup,
> >
> > If we want to limit the generated ISA string to/after a specific
> privilege spec version.
> > Shouldn't we also check the privilege spec version when these
On Sat, Apr 30, 2022 at 8:39 AM Frank Chang wrote:
>
> Hi Anup,
>
> If we want to limit the generated ISA string to/after a specific privilege
> spec version.
> Shouldn't we also check the privilege spec version when these extensions are
> enabled?
> Otherwise, it's possible that one extension
Hi Anup,
If we want to limit the generated ISA string to/after a specific privilege
spec version.
Shouldn't we also check the privilege spec version when these extensions
are enabled?
Otherwise, it's possible that one extension is enabled,
but the privilege spec version is smaller than the one in
Most of the multi-letter extensions (such as Svpbmt, Svnapot, Svinval,
etc) are only available after Priv spec v1.12 so ISA string generation
should check the minimum required priv spec version for all extensions.
Fixes: a775398be2e ("target/riscv: Add isa extenstion strings to the
device tree")
