From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: peer.adelt@c-lab.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/4] target-tricore: Added new MOV instruction variant
Date: Tue, 31 May 2016 10:49:34 +0200 [thread overview]
Message-ID: <92c149c5-db96-a48e-1be7-75e56b4aae69@mail.uni-paderborn.de> (raw)
In-Reply-To: <1464673721-14578-1-git-send-email-peer.adelt@c-lab.de>
On 05/31/2016 07:48 AM, peer.adelt@c-lab.de wrote:
> From: Peer Adelt <peer.adelt@c-lab.de>
>
> Puts the content of data register D[a] into E[c][63:32] and the
> content of data register D[b] into E[c][31:0].
>
> Signed-off-by: Peer Adelt <peer.adelt@c-lab.de>
> ---
> target-tricore/translate.c | 8 ++++++++
> target-tricore/tricore-opcodes.h | 1 +
> 2 files changed, 9 insertions(+)
>
> diff --git a/target-tricore/translate.c b/target-tricore/translate.c
> index e66b433..960ee33 100644
> --- a/target-tricore/translate.c
> +++ b/target-tricore/translate.c
> @@ -6224,6 +6224,14 @@ static void decode_rr_accumulator(CPUTriCoreState *env, DisasContext *ctx)
> case OPC2_32_RR_MOV:
> tcg_gen_mov_tl(cpu_gpr_d[r3], cpu_gpr_d[r2]);
> break;
> + case OPC2_32_RR_MOV_EXT:
> + if (tricore_feature(env, TRICORE_FEATURE_16)) {
> + tcg_gen_mov_tl(cpu_gpr_d[r3], cpu_gpr_d[r1]);
> + tcg_gen_mov_tl(cpu_gpr_d[(r3+1)], cpu_gpr_d[r2]);
If r2 == r3 you would move r1 into r3+1 which is wrong. Use temporaries
instead of directly writing to r3.
Cheers,
Bastian
prev parent reply other threads:[~2016-05-31 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 5:48 [Qemu-devel] [PATCH v2 3/4] target-tricore: Added new MOV instruction variant peer.adelt
2016-05-31 8:49 ` Bastian Koppelmann [this message]
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=92c149c5-db96-a48e-1be7-75e56b4aae69@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=peer.adelt@c-lab.de \
--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).