qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, lucas.araujo@eldorado.org.br
Subject: Re: target/ppc: Move VMX int add/sub saturate insns to decodetree.
Date: Sun, 12 May 2024 12:29:13 +0200	[thread overview]
Message-ID: <b85e90da-cf99-431c-8a64-80cbba21ea89@linaro.org> (raw)
In-Reply-To: <20240512093847.18099-1-rathc@linux.ibm.com>

On 5/12/24 11:38, Chinmay Rath wrote:
> 1. vsubsbs and bcdtrunc :
> 
> In this pair, bcdtrunc has the insn flag check PPC2_ISA300 in the
> vmx-impl file, within the GEN_VXFORM_DUAL macro, which does this flag
> check.
> However it also has this flag check in the vmx-ops file.
> Hence I have retained the same in the new entry in the vmx-ops file.
> This is consistent with the behaviour in done in the following commit :
> https://github.com/qemu/qemu/commit/b132be53a4ba6a0a40d5643d791822f958a36e53
> So even though the flag check is removed from the vmx-impl file, it is
> retained in the vmx-ops file. All good here.
> 
> 2. vadduhs and vmul10euq :
> 
> In this pair, vmul10euq has the insn flag check PPC2_ISA300 in the
> vmx-impl file, check done within the GEN_VXFORM_DUAL macro.
> However the same flag was NOT originally present in the
> vmx-ops file, so I have NOT included in its new entry in the vmx-ops
> file. I have done this, following the behaviour done in the following
> commit :
> https://github.com/qemu/qemu/commit/c85929b2ddf6bbad737635c9b85213007ec043af
> So this flag check for vmul10euq is excluded now. Is this not a problem ?
> I feel that this leads to the flag check being skipped now, however this
> behaviour was followed in the above mentioned commit.

This second link is for VAVG* and VABSD*.

Yes you are correct that this second case was done incorrectly. Thankfully the mistake was 
fixed in the very next commit, when VABSD* was converted to decodetree as well.


r~


  parent reply	other threads:[~2024-05-12 10:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  9:38 target/ppc: Move VMX int add/sub saturate insns to decodetree Chinmay Rath
2024-05-12  9:38 ` [PATCH 1/1] target/ppc: Move VMX integer " Chinmay Rath
2024-05-12 11:38   ` Richard Henderson
2024-05-16 16:23     ` Chinmay Rath
2024-05-12 10:29 ` Richard Henderson [this message]
2024-05-16 16:19   ` target/ppc: Move VMX int " Chinmay Rath

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=b85e90da-cf99-431c-8a64-80cbba21ea89@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=danielhb413@gmail.com \
    --cc=harshpb@linux.ibm.com \
    --cc=lucas.araujo@eldorado.org.br \
    --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).