在2024年12月26日十二月 下午10:55,Philippe Mathieu-Daudé写道:
> On 26/12/24 22:19, Jiaxun Yang wrote:
>> Introduce max32 CPU type as it's necessary to demonstrate all
>> features we have in LA32.
>> 
>> Signed-off-by: Jiaxun Yang <jiaxun.y...@flygoat.com>
>> ---
>>   target/loongarch/cpu.c | 92 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 92 insertions(+)
>
>
>>   #ifdef TARGET_LOONGARCH64
>>   static void loongarch_la464_initfn(Object *obj)
>>   {
>> @@ -923,6 +1014,7 @@ static const TypeInfo loongarch_cpu_type_infos[] = {
>>       },
>>   #endif
>>       DEFINE_LOONGARCH_CPU_TYPE(32, "la132", loongarch_la132_initfn),
>> +    DEFINE_LOONGARCH_CPU_TYPE(32, "max32", loongarch_max32_initfn),
>
> What about "la32max"?

I'm actually thinking about "max32" for la32 and "max32r" la32r to keep it 
concise
(and somehow aligned with existing RISC-V naming).

Thanks
>
>>   #ifdef TARGET_LOONGARCH64
>>       DEFINE_LOONGARCH_CPU_TYPE(64, "la464", loongarch_la464_initfn),
>>       DEFINE_LOONGARCH_CPU_TYPE(64, "max", loongarch_max_initfn),
>>

-- 
- Jiaxun

Reply via email to