From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PULL 0/9] decodetree: Add non-overlapping groups
Date: Tue, 9 Jun 2020 09:24:55 -0700 [thread overview]
Message-ID: <20200609162504.780080-1-richard.henderson@linaro.org> (raw)
The following changes since commit 49ee11555262a256afec592dfed7c5902d5eefd2:
Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-5.1-pull-request' into staging (2020-06-08 11:04:57 +0100)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-dt-20200609
for you to fetch changes up to d6084fba47bb9aef79775c1102d4b647eb58c365:
target/arm: Use a non-overlapping group for misc control (2020-06-09 09:21:19 -0700)
----------------------------------------------------------------
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 +++++++++++++++------------
8 files changed, 360 insertions(+), 225 deletions(-)
create mode 100644 tests/decode/err_pattern_group_nest2.decode
create mode 100644 tests/decode/err_pattern_group_nest3.decode
create mode 100644 tests/decode/succ_pattern_group_nest2.decode
create mode 100644 tests/decode/succ_pattern_group_nest3.decode
create mode 100644 tests/decode/succ_pattern_group_nest4.decode
next reply other threads:[~2020-06-09 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:24 Richard Henderson [this message]
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
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=20200609162504.780080-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).