From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 7/8] decodetree: Implement non-overlapping groups
Date: Tue, 2 Jun 2020 12:19:55 -0700 [thread overview]
Message-ID: <e52bbe8e-8da3-8527-ea08-3f895e8fba77@linaro.org> (raw)
In-Reply-To: <CAFEAcA9goz6quKG7zEGtOkYEUhfX10PB_MNMr6Vzvfz1OCZgSw@mail.gmail.com>
On 6/2/20 12:13 PM, Peter Maydell wrote:
> On Mon, 18 May 2020 at 17:41, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> Intended to be nested within overlapping groups.
>>
>> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> scripts/decodetree.py | 21 ++++++++++++++-------
>> 1 file changed, 14 insertions(+), 7 deletions(-)
>>
>> diff --git a/scripts/decodetree.py b/scripts/decodetree.py
>> index 0ba01e049c..a9739f671d 100755
>> --- a/scripts/decodetree.py
>> +++ b/scripts/decodetree.py
>> @@ -1021,21 +1021,22 @@ def parse_file(f, parent_pat):
>> del toks[0]
>>
>> # End nesting?
>> - if name == '}':
>> + if name == '}' or name == ']':
>> if len(toks) != 0:
>> error(start_lineno, 'extra tokens after close brace')
>> if len(parent_pat.pats) < 2:
>> error(lineno, 'less than two patterns within braces')
>>
>> + # Make sure { } and [ ] nest properly.
>> + if (name == '}') != isinstance(parent_pat, IncMultiPattern):
>> + error(lineno, 'mismatched close brace')
>> +
>> try:
>> parent_pat = nesting_pats.pop()
>> except:
>> - error(lineno, 'mismatched close brace')
>> + error(lineno, 'extra close brace')
>>
>> nesting -= 2
>> - if indent != nesting:
>> - error(lineno, 'indentation ', indent, ' != ', nesting)
>> -
>
> Why do we lose this error check ?
Hmm, wasn't supposed to. Will fix.
r~
next prev parent reply other threads:[~2020-06-02 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 16:40 [PATCH 0/8] decodetree: Add non-overlapping groups Richard Henderson
2020-05-18 16:40 ` [PATCH 1/8] decodetree: Remove python 3.4 check Richard Henderson
2020-05-18 16:46 ` Philippe Mathieu-Daudé
2020-05-29 9:35 ` Philippe Mathieu-Daudé
2020-05-18 16:40 ` [PATCH 2/8] decodetree: Tidy error_with_file Richard Henderson
2020-06-02 14:24 ` Peter Maydell
2020-05-18 16:40 ` [PATCH 3/8] decodetree: Rename MultiPattern to IncMultiPattern Richard Henderson
2020-05-18 16:47 ` Philippe Mathieu-Daudé
2020-05-18 16:40 ` [PATCH 4/8] decodetree: Split out MultiPattern from IncMultiPattern Richard Henderson
2020-05-18 16:47 ` Philippe Mathieu-Daudé
2020-05-18 16:40 ` [PATCH 5/8] decodetree: Allow group covering the entire insn space Richard Henderson
2020-06-02 14:35 ` Peter Maydell
2020-06-02 15:15 ` Richard Henderson
2020-06-02 19:11 ` Peter Maydell
2020-05-18 16:40 ` [PATCH 6/8] decodetree: Move semantic propagation into classes Richard Henderson
2020-06-02 19:12 ` Peter Maydell
2020-05-18 16:40 ` [PATCH 7/8] decodetree: Implement non-overlapping groups Richard Henderson
2020-05-18 16:53 ` Philippe Mathieu-Daudé
2020-06-02 19:13 ` Peter Maydell
2020-06-02 19:19 ` Richard Henderson [this message]
2020-05-18 16:40 ` [PATCH 8/8] target/arm: Use a non-overlapping group for misc control Richard Henderson
2020-05-18 16:56 ` Philippe Mathieu-Daudé
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=e52bbe8e-8da3-8527-ea08-3f895e8fba77@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).