From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, ysato@users.sourceforge.jp
Subject: Re: [Qemu-devel] [PATCH 1/2] decodetree: Initial support for variable-length ISAs
Date: Wed, 29 Jun 2022 14:07:38 +0100 [thread overview]
Message-ID: <CAFEAcA-rU-1xbk8qa6MdXOTtc6tSCN2_3sARum2sV80XzO4xow@mail.gmail.com> (raw)
In-Reply-To: <20190131210851.9842-2-richard.henderson@linaro.org>
On Thu, 31 Jan 2019 at 21:10, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> Assuming that the ISA clearly describes how to determine
> the length of the instruction, and the ISA has a reasonable
> maximum instruction length, the input to the decoder can be
> right-justified in an appropriate insn word.
>
> This is not 100% convenient, as out-of-line %fields are
> numbered relative to the maximum instruction length, but
> this appears to still be usable.
Prompted by a query on IRC I noticed that this patch from a few
years back added variable-insn-width support to decodetree,
including a new commandline argument --varinsnwidth, but
we don't document how to use it in docs/devel/decodetree.rst.
In fact decodetree.rst doesn't document decodetree.py's
commandline options at all. Could you maybe write up a
docs patch to describe them?
thanks
-- PMM
next prev parent reply other threads:[~2022-06-29 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 21:08 [Qemu-devel] [PATCH 0/2] decodetree: Support for variable-length ISAs Richard Henderson
2019-01-31 21:08 ` [Qemu-devel] [PATCH 1/2] decodetree: Initial support " Richard Henderson
2022-06-29 13:07 ` Peter Maydell [this message]
2019-01-31 21:08 ` [Qemu-devel] [PATCH 2/2] decodetree: Expand a decode_load function Richard Henderson
2019-02-02 8:16 ` [Qemu-devel] [PATCH 0/2] decodetree: Support for variable-length ISAs Yoshinori Sato
2019-03-02 6:39 ` [Qemu-devel] [PATCH] decodetree: Add DisasContext to function part Yoshinori Sato
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=CAFEAcA-rU-1xbk8qa6MdXOTtc6tSCN2_3sARum2sV80XzO4xow@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=ysato@users.sourceforge.jp \
/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).