From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: Alex Zuepke <alexander.zuepke@hs-rm.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/4] target-tricore: add missing 64-bit MOV in RLC format
Date: Fri, 12 Dec 2014 16:30:48 +0000 [thread overview]
Message-ID: <548B1838.9040309@mail.uni-paderborn.de> (raw)
In-Reply-To: <5e864091-ecd0-4a22-abbb-be8c9cd28585@EXCHANGE-4K.hds.local>
On 12/12/2014 02:10 PM, Alex Zuepke wrote:
> Signed-off-by: Alex Zuepke <alexander.zuepke@hs-rm.de>
> ---
> target-tricore/translate.c | 12 ++++++++++++
> target-tricore/tricore-opcodes.h | 1 +
> 2 files changed, 13 insertions(+)
>
> diff --git a/target-tricore/translate.c b/target-tricore/translate.c
> index c132223..e3eeedb 100644
> --- a/target-tricore/translate.c
> +++ b/target-tricore/translate.c
> @@ -3781,6 +3781,17 @@ static void decode_rlc_opc(CPUTriCoreState *env, DisasContext *ctx,
> case OPC1_32_RLC_MOV:
> tcg_gen_movi_tl(cpu_gpr_d[r2], const16);
> break;
> + case OPC1_32_RLC_MOV_64:
> + if (tricore_feature(env, TRICORE_FEATURE_16)) {
> + if ((r2 & 0x1) != 0) {
> + /* TODO: raise OPD trap */
> + }
This reminds me, that there should be a mechanism, which can create
traps for all instructions that use two 32bit regs as one 64bit one.
> + tcg_gen_movi_tl(cpu_gpr_d[r2], const16);
> + tcg_gen_movi_tl(cpu_gpr_d[r2+1], const16 >> 15);
> + } else {
> + /* TODO: raise illegal opcode trap */
> + }
> + break;
> case OPC1_32_RLC_MOV_U:
> const16 = MASK_OP_RLC_CONST16(ctx->opcode);
> tcg_gen_movi_tl(cpu_gpr_d[r2], const16);
> @@ -4021,6 +4032,7 @@ static void decode_32Bit_opc(CPUTriCoreState *env, DisasContext *ctx)
> case OPC1_32_RLC_ADDIH_A:
> case OPC1_32_RLC_MFCR:
> case OPC1_32_RLC_MOV:
> + case OPC1_32_RLC_MOV_64:
> case OPC1_32_RLC_MOV_U:
> case OPC1_32_RLC_MOV_H:
> case OPC1_32_RLC_MOVH_A:
> diff --git a/target-tricore/tricore-opcodes.h b/target-tricore/tricore-opcodes.h
> index 7aa6aed..a76a7e4 100644
> --- a/target-tricore/tricore-opcodes.h
> +++ b/target-tricore/tricore-opcodes.h
> @@ -487,6 +487,7 @@ enum {
> OPC1_32_RLC_ADDIH_A = 0x11,
> OPC1_32_RLC_MFCR = 0x4d,
> OPC1_32_RLC_MOV = 0x3b,
> + OPC1_32_RLC_MOV_64 = 0xfb, /* 1.6 only */
> OPC1_32_RLC_MOV_U = 0xbb,
> OPC1_32_RLC_MOV_H = 0x7b,
> OPC1_32_RLC_MOVH_A = 0x91,
Looks good to me anyway.
Reviewed-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
next prev parent reply other threads:[~2014-12-12 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1418393430-12336-1-git-send-email-alexander.zuepke@hs-rm.de>
2014-12-12 14:10 ` [Qemu-devel] [PATCH 1/4] target-tricore: fix offset masking in BOL format Alex Zuepke
2014-12-12 16:26 ` Bastian Koppelmann
2014-12-12 14:10 ` [Qemu-devel] [PATCH 2/4] target-tricore: typo " Alex Zuepke
2014-12-12 16:26 ` Bastian Koppelmann
2014-12-12 14:10 ` [Qemu-devel] [PATCH 3/4] target-tricore: add missing 64-bit MOV in RLC format Alex Zuepke
2014-12-12 16:30 ` Bastian Koppelmann [this message]
2014-12-12 14:10 ` [Qemu-devel] [PATCH 4/4] target-tricore: pretty-print register dump and show more status registers Alex Zuepke
2014-12-12 16:35 ` Bastian Koppelmann
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=548B1838.9040309@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=alexander.zuepke@hs-rm.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).