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] RISC-V simulator cannot run multiply instructions (but can division instructions)
Date: Thu, 22 Sep 2022 04:16:25 +0000 [thread overview]
Message-ID: <bug-29595-4717-NdhyI0DaYS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29595-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29595
Tsukasa OI <research_trasio at irq dot a4lg.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|RISC-V simulator cannot run |RISC-V simulator cannot run
|multiply instructions |multiply instructions (but
| |can division instructions)
--- Comment #1 from Tsukasa OI <research_trasio at irq dot a4lg.com> ---
As far I know, Nelson approved the Binutils part (and committed the original
patchset) but he said he cannot approve the GDB part (since he's not a
maintainer).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-22 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 4:13 [Bug sim/29595] New: RISC-V simulator cannot run multiply instructions research_trasio at irq dot a4lg.com
2022-09-22 4:14 ` [Bug sim/29595] " research_trasio at irq dot a4lg.com
2022-09-22 4:16 ` research_trasio at irq dot a4lg.com [this message]
2022-09-22 4:17 ` [Bug sim/29595] RISC-V simulator cannot run multiply instructions (but can run division instructions) 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-NdhyI0DaYS@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).