From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING^3 PATCH 1/1] sim/riscv: PR29595, Fix multiply instructions
Date: Fri, 7 Oct 2022 01:14:37 +0900 [thread overview]
Message-ID: <0e52b6e0-b012-4e77-970c-ae3ba507adae@irq.a4lg.com> (raw)
In-Reply-To: <mhng-bdc9be88-28bf-406f-8cd8-9f259000f3af@palmer-ri-x1c9>
On 2022/10/07 0:58, Palmer Dabbelt wrote:
> On Thu, 06 Oct 2022 03:33:00 PDT (-0700), research_trasio@irq.a4lg.com
> wrote:
>> Because of recent 'Zmmul' support, the simulator is now broken. This is
>> caused by instruction classification changes:
>>
>> [Before]
>> - INSN_CLASS_M : multiply / divide
>> [After Zmmul]
>> - INSN_CLASS_M : divide
>> - INSN_CLASS_ZMMUL : multiply
>>
>> The simulator checks the instruction class to execute an instruction:
>>
>> - INSN_CLASS_I : 'I'
>> - INSN_CLASS_M : 'M' (multiply / divide)
>> - INSN_CLASS_A : 'A'
>>
>> 'Zmmul' moved multiply instructions to INSN_CLASS_ZMMUL and that
>> instruction
>> class is not handled by the simulator.
>>
>> This commit handles INSN_CLASS_ZMMUL for all 'M' instructions and adds a
>> testcase to test all RV32M instructions run without any faults.
>> ---
>> sim/riscv/sim-main.c | 1 +
>> sim/testsuite/riscv/m-ext.s | 18 ++++++++++++++++++
>> 2 files changed, 19 insertions(+)
>> create mode 100644 sim/testsuite/riscv/m-ext.s
>>
>> diff --git a/sim/riscv/sim-main.c b/sim/riscv/sim-main.c
>> index 30d2f1e1c9a..0156f791d4b 100644
>> --- a/sim/riscv/sim-main.c
>> +++ b/sim/riscv/sim-main.c
>> @@ -936,6 +936,7 @@ execute_one (SIM_CPU *cpu, unsigned_word iw, const
>> struct riscv_opcode *op)
>> case INSN_CLASS_I:
>> return execute_i (cpu, iw, op);
>> case INSN_CLASS_M:
>> + case INSN_CLASS_ZMMUL:
>> return execute_m (cpu, iw, op);
>> default:
>> TRACE_INSN (cpu, "UNHANDLED EXTENSION: %d", op->insn_class);
>> diff --git a/sim/testsuite/riscv/m-ext.s b/sim/testsuite/riscv/m-ext.s
>> new file mode 100644
>> index 00000000000..b85397a32a0
>> --- /dev/null
>> +++ b/sim/testsuite/riscv/m-ext.s
>> @@ -0,0 +1,18 @@
>> +# check that the RV32M instructions run without any fault.
>> +# mach: riscv
>> +
>> +.include "testutils.inc"
>> +
>> + start
>> +
>> + .option arch, +m
>> + mul x0, x1, x2
>> + mulh x0, x1, x2
>> + mulhu x0, x1, x2
>> + mulhsu x0, x1, x2
>> + div x0, x1, x2
>> + divu x0, x1, x2
>> + rem x0, x1, x2
>> + remu x0, x1, x2
>> +
>> + pass
>
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> though as we're talking about in this meeting, I'm not actually a gdbsim
> maintainer so I'm not sure I can formally approve it.
>
Palmer,
I saw following files and thought you are one of the person who can
formally approve my patch.
Quoting sim/MAINTAINERS:
> SIM Maintainers
>
> The simulator is part of the GDB project, so see the file
> gdb/MAINTAINERS for general information about maintaining these files....
> common Frank Ch. Eigler <fche@redhat.com>
> * (target, then global maintainers)
I know that Andrew and Palmer are RISC-V target maintainers of GDB so I
assumed you are responsible for this area. But it seems... no one knows
exactly. It seems very few people is interested in the simulator so...
well... for now, I will continue pinging until someone who thinks
responsible notices.
Thanks,
Tsukasa
next prev parent reply other threads:[~2022-10-06 16:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1657793406.git.research_trasio@irq.a4lg.com>
2022-08-09 3:37 ` [PATCH v4 0/3] RISC-V: Add 'Zmmul' extension Tsukasa OI
2022-08-09 3:37 ` [PATCH v4 1/3] RISC-V: Add 'M' extension testcases Tsukasa OI
2022-08-09 3:37 ` [PATCH v4 2/3] RISC-V: Add 'Zmmul' extension Tsukasa OI
2022-08-09 3:37 ` [PATCH v4 3/3] RISC-V: Add 'Zmmul' failure testcases Tsukasa OI
2022-08-29 1:58 ` [PATCH v5 0/3] RISC-V: Add 'Zmmul' extension Tsukasa OI
2022-08-29 1:58 ` [PATCH v5 1/3] RISC-V: Add 'M' extension testcases Tsukasa OI
2022-08-29 1:58 ` [PATCH v5 2/3] RISC-V: Add 'Zmmul' extension Tsukasa OI
2022-08-29 1:58 ` [PATCH v5 3/3] RISC-V: Add 'Zmmul' failure testcases Tsukasa OI
2022-08-30 9:55 ` [PATCH v5 0/3] RISC-V: Add 'Zmmul' extension Nelson Chu
2022-09-01 7:47 ` Tsukasa OI
2022-08-31 1:46 ` [PATCH 0/1] sim: Fix RISC-V multiply instructions on simulator Tsukasa OI
2022-08-31 1:46 ` [PATCH 1/1] " Tsukasa OI
2022-09-14 10:55 ` [PING^1 PATCH 0/1] " Tsukasa OI
2022-09-14 10:55 ` [PING^1 PATCH 1/1] sim/riscv: Fix RISC-V multiply instructions on the simulator Tsukasa OI
2022-09-21 16:01 ` [PING^2 PATCH 0/1] sim/riscv: Fix broken RISC-V simulater after implementing 'Zmmul' Tsukasa OI
2022-09-21 16:01 ` [PING^2 PATCH 1/1] sim/riscv: Fix RISC-V multiply instructions on the simulator Tsukasa OI
2022-10-06 10:32 ` [PING^3 PATCH 0/1] sim/riscv: PR29595, Fix broken RISC-V simulater after implementing 'Zmmul' Tsukasa OI
2022-10-06 10:33 ` [PING^3 PATCH 1/1] sim/riscv: PR29595, Fix multiply instructions Tsukasa OI
2022-10-06 15:58 ` Palmer Dabbelt
2022-10-06 16:14 ` Tsukasa OI [this message]
2022-10-06 18:27 ` Palmer Dabbelt
2022-10-11 11:43 ` Andrew Burgess
2022-10-11 11:41 ` Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e52b6e0-b012-4e77-970c-ae3ba507adae@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=gdb-patches@sourceware.org \
--cc=palmer@dabbelt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).