qemu-riscv.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
	qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
	bmeng@tinylab.org, liwei1518@gmail.com,
	zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
	max.chou@sifive.com
Subject: Re: [PATCH v4 3/6] target/riscv: remove 'over' brconds from vector trans
Date: Tue, 20 Feb 2024 13:54:34 -1000	[thread overview]
Message-ID: <db20705c-7f29-43df-8c99-96dc573149dc@linaro.org> (raw)
In-Reply-To: <20240220222510.209448-4-dbarboza@ventanamicro.com>

On 2/20/24 12:25, Daniel Henrique Barboza wrote:
>   target/riscv/insn_trans/trans_rvv.c.inc  | 117 -----------------------
>   target/riscv/insn_trans/trans_rvvk.c.inc |  18 ----
>   2 files changed, 135 deletions(-)

There are additional instances in trans_rvbf16.c.inc, including extra useless checks for 
vl == 0.


r~


  reply	other threads:[~2024-02-20 23:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 22:25 [PATCH v4 0/6] riscv: set vstart_eq_zero on mark_vs_dirty Daniel Henrique Barboza
2024-02-20 22:25 ` [PATCH v4 1/6] trans_rvv.c.inc: mark_vs_dirty() before loads and stores Daniel Henrique Barboza
2024-02-20 23:49   ` Richard Henderson
2024-02-20 22:25 ` [PATCH v4 2/6] trans_rvv.c.inc: remove 'is_store' bool from load/store fns Daniel Henrique Barboza
2024-02-20 23:50   ` Richard Henderson
2024-02-20 22:25 ` [PATCH v4 3/6] target/riscv: remove 'over' brconds from vector trans Daniel Henrique Barboza
2024-02-20 23:54   ` Richard Henderson [this message]
2024-02-20 22:25 ` [PATCH v4 4/6] target/riscv/vector_helper.c: set vstart = 0 in GEN_VEXT_VSLIDEUP_VX() Daniel Henrique Barboza
2024-02-20 22:25 ` [PATCH v4 5/6] trans_rvv.c.inc: remove redundant mark_vs_dirty() calls Daniel Henrique Barboza
2024-02-20 22:25 ` [PATCH v4 6/6] target/riscv: Clear vstart_qe_zero flag Daniel Henrique Barboza

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=db20705c-7f29-43df-8c99-96dc573149dc@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng@tinylab.org \
    --cc=dbarboza@ventanamicro.com \
    --cc=liwei1518@gmail.com \
    --cc=max.chou@sifive.com \
    --cc=palmer@rivosinc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=zhiwei_liu@linux.alibaba.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 read-only IMAP folder(s) and NNTP newsgroup(s).