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 0/2] tcg: ppc64: Fix mask generation for vextractdm
Date: Wed, 3 May 2023 11:31:30 -0300 [thread overview]
Message-ID: <f45b4655-394b-8843-e735-288f513ad023@gmail.com> (raw)
In-Reply-To: <168141244011.3026479.13697197743885252330.stgit@ltc-boston1.aus.stglabs.ibm.com>
Shiva,
I just queued patch 1 adding this line in the commit msg:
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1536
This was mentioned by Cedric in patch 2. Also, speaking of patch 2, take a look
on Cedric's review and see if it's applicable or not.
I plan to send a ppc pull request at the end of the week.
Thanks,
Daniel
On 4/13/23 16:00, 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.
>
> Let me know if both patches should be squashed into single
> patch. Checkpatch flagged me to avoid use of __BYTE_ORDER__
> in the test file(second patch), however I see it being
> used in multiarch/sha1.c also this being arch specific
> test, I think it is appropriate to use it here. Let me
> know if otherwise.
>
> References:
> [1] : https://gitlab.com/qemu-project/qemu/-/issues/1536
>
> ---
>
> 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 | 50 +++++++++++++++++++++++++++++
> 3 files changed, 56 insertions(+), 2 deletions(-)
> create mode 100644 tests/tcg/ppc64/vector.c
>
> --
> Signature
>
prev parent reply other threads:[~2023-05-03 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:00 [PATCH 0/2] tcg: ppc64: Fix mask generation for vextractdm Shivaprasad G Bhat
2023-04-13 19:01 ` [PATCH 1/2] " Shivaprasad G Bhat
2023-05-02 9:03 ` Alex Bennée
2023-05-02 10:50 ` Richard Henderson
2023-05-02 14:02 ` Lucas Mateus Martins Araujo e Castro
2023-04-13 19:01 ` [PATCH 2/2] tests: tcg: ppc64: Add tests for Vector Extract Mask Instructions Shivaprasad G Bhat
2023-05-02 7:05 ` Cédric Le Goater
2023-05-04 5:17 ` Shivaprasad G Bhat
2023-05-02 15:05 ` Lucas Mateus Martins Araujo e Castro
2023-05-03 14:31 ` 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=f45b4655-394b-8843-e735-288f513ad023@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).