Re: [PATCH 05/22] target/riscv: move RISCVCPUConfig fields to a header file

On Fri, Feb 7, 2025 at 4:27 AM Paolo Bonzini wrote: > > To support merging a subclass's RISCVCPUDef into the superclass, a list > of all the CPU features is needed. Put them into a header file that > can be included multiple times, expanding the macros BOOL_FIELD and > TYPE_FIELD to different ope

[PATCH 05/22] target/riscv: move RISCVCPUConfig fields to a header file

To support merging a subclass's RISCVCPUDef into the superclass, a list of all the CPU features is needed. Put them into a header file that can be included multiple times, expanding the macros BOOL_FIELD and TYPE_FIELD to different operations. Signed-off-by: Paolo Bonzini --- target/riscv/cpu_c