qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/9] decodetree: Add non-overlapping groups
Date: Sat, 1 Aug 2020 18:42:34 +0100	[thread overview]
Message-ID: <CAFEAcA_nOx=HNat6mQpt-LGBJzLUgphMSeWChGGVN0kwprXQmw@mail.gmail.com> (raw)
In-Reply-To: <20200609162504.780080-1-richard.henderson@linaro.org>

On Tue, 9 Jun 2020 at 17:25, Richard Henderson
<richard.henderson@linaro.org> wrote:
> ----------------------------------------------------------------
> Add non-overlapping groups
>
> ----------------------------------------------------------------
> Richard Henderson (9):
>       decodetree: Tidy error_with_file
>       decodetree: Rename MultiPattern to IncMultiPattern
>       decodetree: Split out MultiPattern from IncMultiPattern
>       decodetree: Allow group covering the entire insn space
>       decodetree: Move semantic propagation into classes
>       decodetree: Implement non-overlapping groups
>       tests/decode: Test non-overlapping groups
>       decodetree: Drop check for less than 2 patterns in a group
>       target/arm: Use a non-overlapping group for misc control
>
>  target/arm/t32.decode                        |   4 +-
>  tests/decode/err_pattern_group_nest1.decode  |  11 +-
>  tests/decode/err_pattern_group_nest2.decode  |   6 +
>  tests/decode/err_pattern_group_nest3.decode  |  14 +
>  tests/decode/succ_pattern_group_nest2.decode |  13 +
>  tests/decode/succ_pattern_group_nest3.decode |  11 +
>  tests/decode/succ_pattern_group_nest4.decode |  13 +
>  scripts/decodetree.py                        | 513 +++++++++++++++------------

Hi, Richard. I've just noticed that when we added non-overlapping
group support to decodetree we forgot to update docs/devel/decodetree.rst,
which still thinks the only kind of group is the overlapping kind.
Any chance of a patch to update the docs?

thanks
-- PMM


      parent reply	other threads:[~2020-08-01 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 16:24 [PULL 0/9] decodetree: Add non-overlapping groups Richard Henderson
2020-06-09 16:24 ` [PULL 1/9] decodetree: Tidy error_with_file Richard Henderson
2020-06-09 16:24 ` [PULL 2/9] decodetree: Rename MultiPattern to IncMultiPattern Richard Henderson
2020-06-09 16:24 ` [PULL 3/9] decodetree: Split out MultiPattern from IncMultiPattern Richard Henderson
2020-06-09 16:24 ` [PULL 4/9] decodetree: Allow group covering the entire insn space Richard Henderson
2020-06-09 16:25 ` [PULL 5/9] decodetree: Move semantic propagation into classes Richard Henderson
2020-06-09 16:25 ` [PULL 6/9] decodetree: Implement non-overlapping groups Richard Henderson
2020-06-09 16:25 ` [PULL 7/9] tests/decode: Test " Richard Henderson
2020-06-09 16:25 ` [PULL 8/9] decodetree: Drop check for less than 2 patterns in a group Richard Henderson
2020-06-09 16:25 ` [PULL 9/9] target/arm: Use a non-overlapping group for misc control Richard Henderson
2020-06-11 12:07 ` [PULL 0/9] decodetree: Add non-overlapping groups Peter Maydell
2020-08-01 17:42 ` Peter Maydell [this message]

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_nOx=HNat6mQpt-LGBJzLUgphMSeWChGGVN0kwprXQmw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).