From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Sebastian Mitterle <smitterl@redhat.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Laurent Vivier <laurent@vivier.eu>,
Thomas Huth <thuth@redhat.com>
Subject: [risu PATCH 0/2] Add support for instructions with length > 32 bit
Date: Fri, 27 Oct 2023 12:04:39 +0200 [thread overview]
Message-ID: <20231027100441.375223-1-thuth@redhat.com> (raw)
RISU currently only supports instructions with a length of
16 bit or 32 bit, however classical CISC systems like s390x
also have instructions that are longer than 32 bit. The first
patch improves the generator to support instructions with
more than 32 bits, and the second patch adds some 48-bit
instructions to the s390x.risu file.
Thomas Huth (2):
risugen: allow instructions with length > 32 bit
s390x.risu: Add some instructions with a length of 48 bits
risugen | 48 +++++++++++++++++++++++++++++-------------
risugen_arm.pm | 6 +++---
risugen_common.pm | 2 +-
risugen_loongarch64.pm | 4 ++--
risugen_m68k.pm | 6 +++---
risugen_ppc64.pm | 4 ++--
risugen_s390x.pm | 17 +++++++++++----
s390x.risu | 20 ++++++++++++++++++
8 files changed, 77 insertions(+), 30 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-27 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 10:04 Thomas Huth [this message]
2023-10-27 10:04 ` [risu PATCH 1/2] risugen: allow instructions with length > 32 bit Thomas Huth
2023-10-31 15:34 ` Peter Maydell
2023-10-27 10:04 ` [risu PATCH 2/2] s390x.risu: Add some instructions with a length of 48 bits Thomas Huth
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=20231027100441.375223-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=smitterl@redhat.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 NNTP newsgroup(s).