From: Richard Henderson <richard.henderson@linaro.org>
To: Zack Buhman <zack@buhman.org>, qemu-devel@nongnu.org
Cc: ysato@users.sourceforge.jp
Subject: Re: [PATCH] target/sh4: add missing CHECK_NOT_DELAY_SLOT
Date: Sun, 7 Apr 2024 09:23:54 -1000 [thread overview]
Message-ID: <6012a84f-155b-440d-aeb8-0df0678c3ee7@linaro.org> (raw)
In-Reply-To: <20240407150705.5965-1-zack@buhman.org>
On 4/7/24 05:07, Zack Buhman wrote:
> CHECK_NOT_DELAY_SLOT is correctly applied to the branch-related
> instructions, but not to the PC-relative mov* instructions.
>
> I verified the existence of an illegal slot exception on a SH7091 when
> any of these instructions are attempted inside a delay slot.
>
> This also matches the behavior described in the SH-4 ISA manual.
>
> Signed-off-by: Zack Buhman<zack@buhman.org>
> ---
> target/sh4/translate.c | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-04-07 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 15:07 [PATCH] target/sh4: add missing CHECK_NOT_DELAY_SLOT Zack Buhman
2024-04-07 19:23 ` Richard Henderson [this message]
2024-04-08 8:57 ` 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=6012a84f-155b-440d-aeb8-0df0678c3ee7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ysato@users.sourceforge.jp \
--cc=zack@buhman.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).