From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PULL 0/3] decodetree: Support variable-length ISAs
Date: Mon, 6 May 2019 11:29:37 -0700 [thread overview]
Message-ID: <20190506182940.2200-1-richard.henderson@linaro.org> (raw)
This is a pre-requisite for the RX port.
r~
The following changes since commit a6ae23831b05a11880b40f7d58e332c45a6b04f7:
Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2019-05-03 15:26:09 +0100)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-dt-20190506
for you to fetch changes up to 451e4ffdb0003ab5ed0d98bd37b385c076aba183:
decodetree: Add DisasContext argument to !function expanders (2019-05-06 11:18:34 -0700)
----------------------------------------------------------------
Add support for variable-length ISAs
----------------------------------------------------------------
Richard Henderson (3):
decodetree: Initial support for variable-length ISAs
decodetree: Expand a decode_load function
decodetree: Add DisasContext argument to !function expanders
target/arm/translate-sve.c | 24 ++--
target/hppa/translate.c | 16 +--
target/riscv/insn_trans/trans_rvc.inc.c | 10 +-
target/riscv/translate.c | 4 +-
scripts/decodetree.py | 233 +++++++++++++++++++++++++++++---
5 files changed, 241 insertions(+), 46 deletions(-)
next reply other threads:[~2019-05-06 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 18:29 Richard Henderson [this message]
2019-05-06 18:29 ` [Qemu-devel] [PULL 1/3] decodetree: Initial support for variable-length ISAs Richard Henderson
2019-05-06 18:29 ` [Qemu-devel] [PULL 2/3] decodetree: Expand a decode_load function Richard Henderson
2019-05-06 18:29 ` [Qemu-devel] [PULL 3/3] decodetree: Add DisasContext argument to !function expanders Richard Henderson
2019-05-07 20:39 ` [Qemu-devel] [PULL 0/3] decodetree: Support variable-length ISAs Peter Maydell
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=20190506182940.2200-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).