qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
	qemu-devel@nongnu.org
Cc: arikalo@wavecomp.com, amarkovic@wavecomp.com
Subject: Re: [Qemu-devel] [PATCH v2 1/4] target/mips: Fix emulation of ILVEV.<B|H|W> on big endian host
Date: Wed, 26 Jun 2019 18:02:14 +0200	[thread overview]
Message-ID: <31b602e7-bf33-ec29-d6e3-6a61abefa866@linaro.org> (raw)
In-Reply-To: <1561038349-17105-2-git-send-email-aleksandar.markovic@rt-rk.com>

On 6/20/19 3:45 PM, Aleksandar Markovic wrote:
> From: Aleksandar Markovic <amarkovic@wavecomp.com>
> 
> Fix emulation of ILVEV.<B|H|W> on big endian host by applying
> mapping of data element indexes from one endian to another.
> 
> Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> Reviewed-by: Aleksandar Rikalo <arikalo@wavecomp.com>
> ---
>  target/mips/msa_helper.c | 37 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 37 insertions(+)
> 
> diff --git a/target/mips/msa_helper.c b/target/mips/msa_helper.c
> index be059a3..215d8af 100644
> --- a/target/mips/msa_helper.c
> +++ b/target/mips/msa_helper.c
> @@ -1737,6 +1737,24 @@ void helper_msa_ilvev_df(CPUMIPSState *env, uint32_t df, uint32_t wd,
>  
>      switch (df) {
>      case DF_BYTE:
> +#if defined(TARGET_WORDS_BIGENDIAN)

The commit message talks about the endianness of the host, whereas this check
is for the endianness of the target.


> +        pwd->b[8]  = pws->b[9];
> +        pwd->b[9]  = pwt->b[9];
> +        pwd->b[10] = pws->b[11];
> +        pwd->b[11] = pwt->b[11];
> +        pwd->b[12] = pws->b[13];
> +        pwd->b[13] = pwt->b[13];
> +        pwd->b[14] = pws->b[15];
> +        pwd->b[15] = pwt->b[15];
> +        pwd->b[0]  = pws->b[1];
> +        pwd->b[1]  = pwt->b[1];
> +        pwd->b[2]  = pws->b[3];
> +        pwd->b[3]  = pwt->b[3];
> +        pwd->b[4]  = pws->b[5];
> +        pwd->b[5]  = pwt->b[5];
> +        pwd->b[6]  = pws->b[7];
> +        pwd->b[7]  = pwt->b[7];
> +#else
>          pwd->b[15] = pws->b[14];
>          pwd->b[14] = pwt->b[14];
>          pwd->b[13] = pws->b[12];

FWIW, avoiding this sort of duplication is why other targets define helper
macros like

PPC:
#define VsrB(i) u8[15 - (i)]
etc

ARM, S390:
/* Note that vector data is stored in host-endian 64-bit chunks,
   so addressing units smaller than that needs a host-endian fixup.  */
#ifdef HOST_WORDS_BIGENDIAN
#define H1(x)  ((x) ^ 7)
etc


r~


  reply	other threads:[~2019-06-26 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 13:45 [Qemu-devel] [PATCH v2 0/4] target/mips: Fix some issues of MSA emulation on big endian hosts Aleksandar Markovic
2019-06-20 13:45 ` [Qemu-devel] [PATCH v2 1/4] target/mips: Fix emulation of ILVEV.<B|H|W> on big endian host Aleksandar Markovic
2019-06-26 16:02   ` Richard Henderson [this message]
2019-06-20 13:45 ` [Qemu-devel] [PATCH v2 2/4] target/mips: Fix emulation of ILVOD.<B|H|W> " Aleksandar Markovic
2019-06-20 13:45 ` [Qemu-devel] [PATCH v2 3/4] target/mips: Fix emulation of ILVL.<B|H|W> " Aleksandar Markovic
2019-06-20 13:45 ` [Qemu-devel] [PATCH v2 4/4] target/mips: Fix emulation of ILVR.<B|H|W> " Aleksandar Markovic

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=31b602e7-bf33-ec29-d6e3-6a61abefa866@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.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).