public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "research_trasio at irq dot a4lg.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/29595] New: RISC-V simulator cannot run multiply instructions
Date: Thu, 22 Sep 2022 04:13:35 +0000	[thread overview]
Message-ID: <bug-29595-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29595

            Bug ID: 29595
           Summary: RISC-V simulator cannot run multiply instructions
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: sim
          Assignee: unassigned at sourceware dot org
          Reporter: research_trasio at irq dot a4lg.com
                CC: vapier at gentoo dot org
  Target Milestone: ---

Created attachment 14343
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14343&action=edit
Reproduction source code + generated object files + simulator logs

[POSSIBLE RELEASE BLOCKER FOR GDB 13.1]

On the latest master, RISC-V simulator cannot run multiply instructions (but
CAN run division instructions).

I completely know the cause:
On the Binutils side, new multiply-only instruction subset extension 'Zmmul' is
being added.  I sent a patchset which spans *both Binutils and GDB* but *only
Binutils part is committed.*

This is the one (same but both to binutils and gdb-patches ML):
<https://sourceware.org/pipermail/binutils/2022-August/122653.html>
<https://sourceware.org/pipermail/gdb-patches/2022-August/191295.html>

I'm proposing remaining part (GDB / simulator part) as a separate patchset but
there's no response from the GDB side...
<https://sourceware.org/pipermail/gdb-patches/2022-August/191609.html>
<https://sourceware.org/pipermail/gdb-patches/2022-September/191841.html> (ping
1)
<https://sourceware.org/pipermail/gdb-patches/2022-September/191995.html> (ping
2)

Not being able to run the multiply instructions on the simulator is clearly a
release blocker for GDB 13.1.  So I'm reporting this to track this issue.

My copyright assignment to both Binutils and GDB is complete and I'm now even a
"write after approval" committer.  If a maintainer gives me an approval, I can
commit it in a day.


GitHub tracker of me:
<https://github.com/a4lg/binutils-gdb/wiki/sim_riscv_zmmul>
<https://github.com/a4lg/binutils-gdb/wiki/riscv_zmmul>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-09-22  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  4:13 research_trasio at irq dot a4lg.com [this message]
2022-09-22  4:14 ` [Bug sim/29595] " research_trasio at irq dot a4lg.com
2022-09-22  4:16 ` [Bug sim/29595] RISC-V simulator cannot run multiply instructions (but can division instructions) research_trasio at irq dot a4lg.com
2022-09-22  4:17 ` [Bug sim/29595] RISC-V simulator cannot run multiply instructions (but can run " research_trasio at irq dot a4lg.com
2022-09-22  4:50 ` research_trasio at irq dot a4lg.com
2022-09-22  5:22 ` research_trasio at irq dot a4lg.com
2022-10-11 11:47 ` aburgess at redhat dot com

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=bug-29595-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).