From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH for-8.0] target/arm: Fix generated code for cpreg reads when HSTR is active
Date: Tue, 28 Mar 2023 12:14:55 -0700 [thread overview]
Message-ID: <5975067e-81bd-c67e-4ba6-01f0f3c6613b@linaro.org> (raw)
In-Reply-To: <CAFEAcA_TGN7qk8YQz8MPbdg=jcT-HQVFWBfnEO53AAPyXBmqTQ@mail.gmail.com>
On 3/28/23 11:27, Peter Maydell wrote:
> On Tue, 28 Mar 2023 at 18:27, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> On 3/28/23 09:28, Peter Maydell wrote:
>>> + /*
>>> + * gen_exception_insn() will set is_jmp to DISAS_NORETURN,
>>> + * but since we're conditionally branching over it, we want
>>> + * to retain the existing value.
>>> + */
>>> + old_is_jmp = s->base.is_jmp;
>>> gen_exception_insn(s, 0, EXCP_UDEF, syndrome);
>>> + s->base.is_jmp = old_is_jmp;
>>
>> A third solution is to simply set is_jmp = DISAS_NEXT here.
>
> I wasn't confident enough that the previous is_jmp had
> to be DISAS_NEXT to do that -- there are a lot of
> different values and it's not clear to me which are ones you
> might find lying around in is_jmp at the start of an insn.
At the very start of an insn, you will *only* find DISAS_NEXT.
Anything else will have exited the TB for the previous insn.
r~
next prev parent reply other threads:[~2023-03-28 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:28 [PATCH for-8.0] target/arm: Fix generated code for cpreg reads when HSTR is active Peter Maydell
2023-03-28 17:25 ` Richard Henderson
2023-03-28 17:27 ` Richard Henderson
2023-03-28 18:27 ` Peter Maydell
2023-03-28 19:14 ` Richard Henderson [this message]
2023-03-28 19:16 ` 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=5975067e-81bd-c67e-4ba6-01f0f3c6613b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).