From: Mike Frysinger <vapier@gentoo.org>
To: jaydeep.patil@imgtec.com
Cc: gdb-patches@sourceware.org, aburgess@redhat.com,
joseph.faulls@imgtec.com, bhushan.attarde@imgtec.com
Subject: Re: [PATCH v4 1/2] [sim/riscv] Fix crash during instruction decoding
Date: Thu, 21 Dec 2023 07:48:09 -0500 [thread overview]
Message-ID: <ZYQ0CZbbXMkEzyy-@vapier> (raw)
In-Reply-To: <20231221111139.26341-2-jaydeep.patil@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 21 bytes --]
sim looks fine
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-21 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 11:11 [PATCH v4 0/2] sim: riscv: Compressed instruction simulation jaydeep.patil
2023-12-21 11:11 ` [PATCH v4 1/2] [sim/riscv] Fix crash during instruction decoding jaydeep.patil
2023-12-21 12:48 ` Mike Frysinger [this message]
2023-12-21 11:13 ` [PATCH v4 2/2] [sim/riscv] Add support for compressed integer instructions jaydeep.patil
2023-12-21 15:07 ` Mike Frysinger
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=ZYQ0CZbbXMkEzyy-@vapier \
--to=vapier@gentoo.org \
--cc=aburgess@redhat.com \
--cc=bhushan.attarde@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=jaydeep.patil@imgtec.com \
--cc=joseph.faulls@imgtec.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).