From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/3] decodetree improvements
Date: Sun, 18 Aug 2019 07:39:56 +0100 [thread overview]
Message-ID: <20190818063959.14533-1-richard.henderson@linaro.org> (raw)
Changes from v1:
* Drop unintended hunk from MultiField constructor.
* Typo fixed in ParameterField documentation.
Blurb from v1:
These are split out from my decodetree coversion of the AArch32
base instruction sets.
The first patch has been tidied per review from Peter. I now
diagnose nonsense fields containing no bits. I eliminated the
unused integer argument passed to the named function. I improved
the documentation.
The second patch is new, a suggestion from Phillipe. This then
enables the third patch, tidying up the existing usage in riscv.
r~
Richard Henderson (3):
decodetree: Allow !function with no input bits
decodetree: Suppress redundant declaration warnings
target/riscv: Remove redundant declaration pragmas
target/riscv/translate.c | 19 +--------
docs/devel/decodetree.rst | 8 +++-
scripts/decodetree.py | 71 ++++++++++++++++++++++++++-----
tests/decode/err_field6.decode | 5 +++
tests/decode/succ_function.decode | 6 +++
5 files changed, 79 insertions(+), 30 deletions(-)
create mode 100644 tests/decode/err_field6.decode
create mode 100644 tests/decode/succ_function.decode
--
2.17.1
next reply other threads:[~2019-08-18 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 6:39 Richard Henderson [this message]
2019-08-18 6:39 ` [Qemu-devel] [PATCH v2 1/3] decodetree: Allow !function with no input bits Richard Henderson
2019-08-18 21:49 ` Philippe Mathieu-Daudé
2019-08-18 6:39 ` [Qemu-devel] [PATCH v2 2/3] decodetree: Suppress redundant declaration warnings Richard Henderson
2019-08-18 6:39 ` [Qemu-devel] [PATCH v2 3/3] target/riscv: Remove redundant declaration pragmas Richard Henderson
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=20190818063959.14533-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).