qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Shivaprasad G Bhat <sbhat@linux.ibm.com>,
	philmd@linaro.org, richard.henderson@linaro.org,
	lucas.araujo@eldorado.org.br, qemu-ppc@nongnu.org, clg@kaod.org,
	david@gibson.dropbear.id.au, groug@kaod.org
Cc: john_platts@hotmail.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] tcg: ppc64: Fix mask generation for vextractdm
Date: Thu, 4 May 2023 08:06:11 -0300	[thread overview]
Message-ID: <d0c218dd-4148-9439-876e-5998a8ac6c15@gmail.com> (raw)
In-Reply-To: <168319291781.1159309.7376486961333644798.stgit@ltc-boston1.aus.stglabs.ibm.com>

Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,


Daniel

On 5/4/23 06:35, Shivaprasad G Bhat wrote:
> While debugging gitlab issue[1] 1536, I happen to try the
> vextract[X]m instructions on the real hardware. The test
> used in [1] is failing for vextractdm.
> 
> On debugging it is seen, in function do_extractm() the
> mask is calculated as dup_const(1 << (element_width - 1)).
> '1' being signed int works fine for MO_8,16,32. For MO_64,
> on PPC64 host this ends up becoming 0 on compilation. The
> vextractdm uses MO_64, and it ends up having mask as 0.
> 
> The first patch here fixes that by explicitly using
> 1ULL instead of signed int 1 like its used everywhere else.
> Second patch introduces the test case from [1] into qemu
> tcg/ppc64 along with fixes/tweaks to make it work for both
> big and little-endian targets.
> 
> References:
> [1] : https://gitlab.com/qemu-project/qemu/-/issues/1536
> 
> ---
> Changelog:
> Since v1 : https://lists.gnu.org/archive/html/qemu-devel/2023-04/msg01958.html
>   - Added "Resolves: " to first patch description
>   - Rebased to top of the tree. I see with d044b7c33a5, Alex has limited the
>     scope of plugin tests to just the MULTIARCH_TESTS. So, removed the plugin
>     tests for the test case added in the second patch.
>   - Changed the test case to use the HOST_BIG_ENDIAN from compiler.h
> 
> Shivaprasad G Bhat (2):
>        tcg: ppc64: Fix mask generation for vextractdm
>        tests: tcg: ppc64: Add tests for Vector Extract Mask Instructions
> 
> 
>   target/ppc/translate/vmx-impl.c.inc |  2 +-
>   tests/tcg/ppc64/Makefile.target     |  6 +++-
>   tests/tcg/ppc64/vector.c            | 51 +++++++++++++++++++++++++++++
>   3 files changed, 57 insertions(+), 2 deletions(-)
>   create mode 100644 tests/tcg/ppc64/vector.c
> 
> --
> Signature
> 


      parent reply	other threads:[~2023-05-04 11:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  9:35 [PATCH v2 0/2] tcg: ppc64: Fix mask generation for vextractdm Shivaprasad G Bhat
2023-05-04  9:35 ` [PATCH v2 1/2] " Shivaprasad G Bhat
2023-05-04  6:20   ` Cédric Le Goater
2023-05-04  9:36 ` [PATCH v2 2/2] tests: tcg: ppc64: Add tests for Vector Extract Mask Instructions Shivaprasad G Bhat
2023-05-04  6:22   ` Cédric Le Goater
2023-05-04 11:06 ` Daniel Henrique Barboza [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=d0c218dd-4148-9439-876e-5998a8ac6c15@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=john_platts@hotmail.com \
    --cc=lucas.araujo@eldorado.org.br \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sbhat@linux.ibm.com \
    /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).