From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: i@yvt.jp, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/4] target/rx: Track PSW.U in tb->flags
Date: Tue, 19 Apr 2022 16:40:59 +0900 [thread overview]
Message-ID: <87k0blmsfo.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20220417165130.695085-1-richard.henderson@linaro.org>
On Mon, 18 Apr 2022 01:51:26 +0900,
Richard Henderson wrote:
>
> This is a follow up to Kawada-san's patch for the problem
> of a missed update to the stack pointer in CLRPSW/SETPSW.
> This fixes the problem without movcond by tracking the
> current state of PSW.U within the TB.
>
>
> r~
>
>
> Richard Henderson (4):
> target/rx: Put tb_flags into DisasContext
> target/rx: Store PSW.U in tb->flags
> target/rx: Move DISAS_UPDATE check for write to PSW
> target/rx: Swap stack pointers on clrpsw/setpsw instruction
>
> target/rx/cpu.h | 1 +
> target/rx/translate.c | 67 +++++++++++++++++++++++--------------------
> 2 files changed, 37 insertions(+), 31 deletions(-)
>
> --
> 2.25.1
>
Reviewed-by: Yoshinori Sato <ysato@users.sourceforge.jp>
--
Yosinori Sato
next prev parent reply other threads:[~2022-04-19 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 16:51 [PATCH 0/4] target/rx: Track PSW.U in tb->flags Richard Henderson
2022-04-17 16:51 ` [PATCH 1/4] target/rx: Put tb_flags into DisasContext Richard Henderson
2022-04-17 16:51 ` [PATCH 2/4] target/rx: Store PSW.U in tb->flags Richard Henderson
2022-04-17 16:51 ` [PATCH 3/4] target/rx: Move DISAS_UPDATE check for write to PSW Richard Henderson
2022-04-17 16:51 ` [PATCH 4/4] target/rx: Swap stack pointers on clrpsw/setpsw instruction Richard Henderson
2022-04-19 7:40 ` Yoshinori Sato [this message]
2022-04-21 17:05 ` [PATCH 0/4] target/rx: Track PSW.U in tb->flags 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=87k0blmsfo.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=i@yvt.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.