From: Richard Henderson <richard.henderson@linaro.org>
To: Chinmay Rath <rathc@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Cc: npiggin@gmail.com, danielhb413@gmail.com, clg@kaod.org,
harshpb@linux.ibm.com, sbhat@linux.ibm.com
Subject: Re: [PATCH v2] target/ppc: Move add and subf type fixed-point arithmetic instructions to decodetree
Date: Wed, 14 Feb 2024 09:09:39 -1000 [thread overview]
Message-ID: <41539522-c05a-4c67-95f5-0ecd69fbcd8d@linaro.org> (raw)
In-Reply-To: <20240214094027.895376-1-rathc@linux.ibm.com>
On 2/13/24 23:40, Chinmay Rath wrote:
> This patch moves the below instructions to decodetree specification:
>
> {add, subf}[c,e,me,ze][o][.] : XO-form
> addic[.], subfic : D-form
> addex : Z23-form
>
> This patch introduces XO form instructions into decode tree specification, for
> which all the four variations([o][.]) have been handled with a single pattern.
> 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>
> ---
> Changes v1 -> v2 :
> Reused X format for ADDEX instead of creating a new Z23_tab_cy
> format. (Richard)
> Added necessary instruction flag checks for ADDEX. (self-review)
> ---
> target/ppc/insn32.decode | 26 ++++
> target/ppc/translate.c | 136 ---------------------
> target/ppc/translate/fixedpoint-impl.c.inc | 70 +++++++++++
> 3 files changed, 96 insertions(+), 136 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-02-14 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 9:40 [PATCH v2] target/ppc: Move add and subf type fixed-point arithmetic instructions to decodetree Chinmay Rath
2024-02-14 19:09 ` Richard Henderson [this message]
2024-02-19 4:22 ` Harsh Prateek Bora
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=41539522-c05a-4c67-95f5-0ecd69fbcd8d@linaro.org \
--to=richard.henderson@linaro.org \
--cc=clg@kaod.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 \
--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).