qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Weiwei Li <liweiwei@iscas.ac.cn>,
	palmer@dabbelt.com, alistair.francis@wdc.com,
	bin.meng@windriver.com, qemu-riscv@nongnu.org,
	qemu-devel@nongnu.org
Cc: wangjunqiang@iscas.ac.cn, lazyparser@gmail.com, ardxwe@gmail.com
Subject: Re: [PATCH v2 3/6] target/riscv: add support for zfinx
Date: Sat, 1 Jan 2022 11:48:54 -0800	[thread overview]
Message-ID: <120dea96-eade-bcd6-eea0-0017b165f1ca@linaro.org> (raw)
In-Reply-To: <7096a296-f1c2-44e7-d084-1c473b50a711@iscas.ac.cn>

On 12/31/21 10:05 PM, Weiwei Li wrote:
> 在 2022/1/1 上午4:06, Richard Henderson 写道:
>> On 12/30/21 7:23 PM, Weiwei Li wrote:
>>> +    if (reg_num != 0) {
>>> +        switch (get_ol(ctx)) {
>>
>> Oh, you should be using get_xl here and elsewhere in this patch, not get_ol.
> 
> Sorry. I don't know the difference between get_xl and  get_ol. From gpr register 
> read/write function, It seems get_ol is used in register read, and get_xl is used in 
> register write.
> 
> However, "ctx->ol= ctx->xl;" is executed before translate instruction.

ol is the operation length; xl is the register length.

In this case, the operation length doesn't matter -- we're interested in distinguishing 
RV32 and RV64, because that's where the change in semantics comes from.


r~


  reply	other threads:[~2022-01-01 19:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31  3:23 [PATCH v2 0/6] support subsets of Float-Point in Integer Registers extensions Weiwei Li
2021-12-31  3:23 ` [PATCH v2 1/6] target/riscv: add cfg properties for zfinx, zdinx and zhinx{min} Weiwei Li
2021-12-31  6:28   ` Bin Meng
2021-12-31  3:23 ` [PATCH v2 2/6] target/riscv: hardwire mstatus.FS to zero when enable zfinx Weiwei Li
2021-12-31 19:56   ` Richard Henderson
2022-01-01  5:55     ` Weiwei Li
2022-01-01 19:46       ` Richard Henderson
2022-01-02  5:53         ` Weiwei Li
2021-12-31  3:23 ` [PATCH v2 3/6] target/riscv: add support for zfinx Weiwei Li
2021-12-31 20:03   ` Richard Henderson
2021-12-31 20:06   ` Richard Henderson
2022-01-01  6:05     ` Weiwei Li
2022-01-01 19:48       ` Richard Henderson [this message]
2022-01-02  5:56         ` Weiwei Li
2021-12-31  3:23 ` [PATCH v2 4/6] target/riscv: add support for zdinx Weiwei Li
2021-12-31 20:07   ` Richard Henderson
2022-01-01  6:06     ` Weiwei Li
2021-12-31  3:23 ` [PATCH v2 5/6] target/riscv: add support for zhinx/zhinxmin Weiwei Li
2021-12-31 20:08   ` Richard Henderson
2021-12-31  3:23 ` [PATCH v2 6/6] target/riscv: expose zfinx, zdinx, zhinx{min} properties Weiwei Li

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=120dea96-eade-bcd6-eea0-0017b165f1ca@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=ardxwe@gmail.com \
    --cc=bin.meng@windriver.com \
    --cc=lazyparser@gmail.com \
    --cc=liweiwei@iscas.ac.cn \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=wangjunqiang@iscas.ac.cn \
    /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).