On Sat, Sep 5, 2026 at 1:27 AM Daniel Henrique Barboza <[email protected]> wrote: > > We want to configure other CPU types to use profiles as an alternative > to adding every profile extension explicitly, i.e. a profile is nothing > more than an extension bundle. > > This means that a vendor CPU can set .profile=rva23s64 while having the > same handling as any other vendor CPU. Same thing with all other CPU > types. > > Signed-off-by: Daniel Henrique Barboza <[email protected]> > Reviewed-by: Andrew Jones <[email protected]> > Reviewed-by: Alistair Francis <[email protected]> > Reviewed-by: Chao Liu <[email protected]> > --- > target/riscv/cpu.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c > index 652311ddef..185474a8cf 100644 > --- a/target/riscv/cpu.c > +++ b/target/riscv/cpu.c > @@ -3096,7 +3096,6 @@ static void riscv_cpu_class_base_init(ObjectClass *c, > const void *data) > mcc->def->bare |= def->bare; > if (def->profile) { > assert(profile_extends(def->profile, mcc->def->profile)); > - assert(mcc->def->bare); > mcc->def->profile = def->profile; > } > if (def->misa_mxl_max) { > -- > 2.43.0 > Reviewed-by: Sunil V L <[email protected]>
