From: Richard Henderson <richard.henderson@linaro.org>
To: Craig Janeczek <jancraig@amazon.com>, qemu-devel@nongnu.org
Cc: aurelien@aurel32.net, amarkovic@wavecomp.com
Subject: Re: [Qemu-devel] [PATCH 2/7] target/mips: Add MXU instructions S32I2M and S32M2I
Date: Sat, 25 Aug 2018 10:07:29 -0700 [thread overview]
Message-ID: <231c38e4-8ad4-0f73-69ab-7a66d20716d3@linaro.org> (raw)
In-Reply-To: <f1e92127959ffb3df713a06452328a71170bda93.1535133089.git.jancraig@amazon.com>
On 08/24/2018 12:44 PM, Craig Janeczek via Qemu-devel wrote:
> Adds support for emulating the S32I2M and S32M2I MXU instructions.
>
> Signed-off-by: Craig Janeczek <jancraig@amazon.com>
> ---
> target/mips/translate.c | 55 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/target/mips/translate.c b/target/mips/translate.c
> index 50f0cb558f..381dfad36e 100644
> --- a/target/mips/translate.c
> +++ b/target/mips/translate.c
> @@ -364,6 +364,9 @@ enum {
> OPC_CLO = 0x21 | OPC_SPECIAL2,
> OPC_DCLZ = 0x24 | OPC_SPECIAL2,
> OPC_DCLO = 0x25 | OPC_SPECIAL2,
> + /* MXU */
> + OPC_MXU_S32I2M = 0x2F | OPC_SPECIAL2,
> + OPC_MXU_S32M2I = 0x2E | OPC_SPECIAL2,
I haven't been able to find any documentation of the bit
layout of these instructions. Any pointers?
> +typedef union {
> + struct {
> + uint32_t op:6;
> + uint32_t xra:5;
> + uint32_t:5;
> + uint32_t rb:5;
> + uint32_t:5;
> + uint32_t special2:6;
> + } S32I2M;
> +
> + struct {
> + uint32_t op:6;
> + uint32_t xra:5;
> + uint32_t:5;
> + uint32_t rb:5;
> + uint32_t:5;
> + uint32_t special2:6;
> + } S32M2I;
> +} MXU_OPCODE;
Do not use bitfields. The layout differs by host compiler.
Use extract32(input, pos, len).
> +
> +/* MXU Instructions */
> +static void gen_mxu(DisasContext *ctx, uint32_t opc)
> +{
> +#ifndef TARGET_MIPS64 /* Only works in 32 bit mode */
> + TCGv t0;
> + t0 = tcg_temp_new();
> + MXU_OPCODE *opcode = (MXU_OPCODE *)&ctx->opcode;
> +
> + switch (opc) {
> + case OPC_MXU_S32I2M:
> + gen_load_gpr(t0, opcode->S32I2M.rb);
> + gen_store_mxu_gpr(t0, opcode->S32I2M.xra);
> + break;
> +
> + case OPC_MXU_S32M2I:
> + gen_load_mxu_gpr(t0, opcode->S32M2I.xra);
> + gen_store_gpr(t0, opcode->S32M2I.rb);
> + break;
> + }
> +
> + tcg_temp_free(t0);
> +#else
> + generate_exception_end(ctx, EXCP_RI);
> +#endif
> +}
There's nothing here (yet, I suppose) that won't compile for MIPS64.
I'd suggest avoiding ifdefs as much as possible.
r~
next prev parent reply other threads:[~2018-08-25 17:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 19:44 [Qemu-devel] [PATCH 0/7] Add limited MXU instruction support Craig Janeczek
2018-08-24 19:44 ` [Qemu-devel] [PATCH 1/7] target/mips: Add MXU register support Craig Janeczek
2018-08-25 16:50 ` Richard Henderson
2018-08-27 12:35 ` Aleksandar Markovic
2018-08-27 12:41 ` Aleksandar Markovic
2018-08-24 19:44 ` [Qemu-devel] [PATCH 2/7] target/mips: Add MXU instructions S32I2M and S32M2I Craig Janeczek
2018-08-25 17:07 ` Richard Henderson [this message]
2018-08-27 12:14 ` Janeczek, Craig
2018-08-27 13:21 ` Aleksandar Markovic
2018-08-27 12:22 ` Janeczek, Craig
2018-08-27 13:25 ` Aleksandar Markovic
2018-08-24 19:44 ` [Qemu-devel] [PATCH 3/7] target/mips: Add MXU instruction S8LDD Craig Janeczek
2018-08-25 17:17 ` Richard Henderson
2018-08-24 19:44 ` [Qemu-devel] [PATCH 4/7] target/mips: Add MXU instruction D16MUL Craig Janeczek
2018-08-25 17:23 ` Richard Henderson
2018-08-24 19:44 ` [Qemu-devel] [PATCH 5/7] target/mips: Add MXU instruction D16MAC Craig Janeczek
2018-08-24 19:44 ` [Qemu-devel] [PATCH 6/7] target/mips: Add MXU instructions Q8MUL and Q8MULSU Craig Janeczek
2018-08-24 19:44 ` [Qemu-devel] [PATCH 7/7] target/mips: Add MXU instructions S32LDD and S32LDDR Craig Janeczek
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=231c38e4-8ad4-0f73-69ab-7a66d20716d3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=jancraig@amazon.com \
--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).