From: Richard Henderson <richard.henderson@linaro.org>
To: Chinmay Rath <rathc@linux.ibm.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, npiggin@gmail.com, danielhb413@gmail.com,
harshpb@linux.ibm.com
Subject: Re: [PATCH 3/3] target/ppc: Move VMX integer max/min instructions to decodetree.
Date: Mon, 29 Apr 2024 05:49:53 -0700 [thread overview]
Message-ID: <3ff36bf9-1318-4408-8afc-2067351f058d@linaro.org> (raw)
In-Reply-To: <20240429051317.289426-4-rathc@linux.ibm.com>
On 4/28/24 22:13, Chinmay Rath wrote:
> Moving the following instructions to decodetree specification :
>
> v{max, min}{u, s}{b, h, w, d} : VX-form
>
> The changes were verified by validating that the tcg ops generated by those
> instructions remain the same, which were captured with the '-d in_asm,op' flag.
>
> Signed-off-by: Chinmay Rath<rathc@linux.ibm.com>
> ---
> target/ppc/insn32.decode | 22 +++++++++++++++++
> target/ppc/translate/vmx-impl.c.inc | 37 ++++++++++++++++-------------
> target/ppc/translate/vmx-ops.c.inc | 16 -------------
> 3 files changed, 43 insertions(+), 32 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-04-29 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 5:13 [PATCH 0/3] target/ppc: Moving VMX insns to decodetree Chinmay Rath
2024-04-29 5:13 ` [PATCH 1/3] target/ppc: Move VMX storage access instructions " Chinmay Rath
2024-04-29 12:48 ` Richard Henderson
2024-04-29 5:13 ` [PATCH 2/3] target/ppc: Move VMX integer logical " Chinmay Rath
2024-04-29 12:48 ` Richard Henderson
2024-04-29 5:13 ` [PATCH 3/3] target/ppc: Move VMX integer max/min " Chinmay Rath
2024-04-29 12:49 ` Richard Henderson [this message]
2024-05-18 9:05 ` [PATCH 0/3] target/ppc: Moving VMX insns " Nicholas Piggin
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=3ff36bf9-1318-4408-8afc-2067351f058d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@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).