qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chinmay Rath <rathc@linux.vnet.ibm.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	Chinmay Rath <rathc@linux.ibm.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org, npiggin@gmail.com
Cc: harshpb@linux.ibm.com, sbhat@linux.ibm.com
Subject: Re: [RFC PATCH] target/ppc: Move add and subf type fixed-point arithmetic instructions to decodetree
Date: Tue, 13 Feb 2024 14:33:24 +0530	[thread overview]
Message-ID: <29d66265-c613-42ef-9a1c-77a295f9bb7c@linux.vnet.ibm.com> (raw)
In-Reply-To: <f07f918e-d7b4-41bd-88eb-ddb2bd96dd73@linaro.org>

Hi Richard,

On 2/13/24 03:51, Richard Henderson wrote:
> On 2/9/24 01:35, Chinmay Rath wrote:
>> +&Z23_tab_cy     rt ra rb cy
>> +@Z23_tab_cy     ...... rt:5 ra:5 rb:5 cy:2 ........ . &Z23_tab_cy
> ...
>> +ADDEX           011111 ..... ..... ..... .. 10101010 -  @Z23_tab_cy
> ...
>> +static bool trans_ADDEX(DisasContext *ctx, arg_Z23_tab_cy *a)
>> +{
>> +    gen_op_arith_add(ctx, cpu_gpr[a->rt], cpu_gpr[a->ra], 
>> cpu_gpr[a->rb],
>> +                     cpu_ov, cpu_ov32, true, true, false, false);
>> +    return true;
>> +}
>
> CY != 0 is reserved.
>
> While you could diagnose this in trans_ADDEX, it seems cleaner to 
> simply match 00 in the CY field until a future ISA defines something 
> else.  All that is required is a comment in the decodetree entry.
>
> # Z23-form, with CY=0; all other values for CY are reserved.
> # This works out the same as X-form.
> ADDEX    011111 ..... ..... ..... 00 10101010 -   @X
>
Thanks for your review comments.

I shall update as suggested in v2.

Regards,

Chinmay

>
> r~


      reply	other threads:[~2024-02-13 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 11:35 [RFC PATCH] target/ppc: Move add and subf type fixed-point arithmetic instructions to decodetree Chinmay Rath
2024-02-12  6:13 ` Harsh Prateek Bora
2024-02-12 22:21 ` Richard Henderson
2024-02-13  9:03   ` Chinmay Rath [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=29d66265-c613-42ef-9a1c-77a295f9bb7c@linux.vnet.ibm.com \
    --to=rathc@linux.vnet.ibm.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=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).