From: Richard Henderson <richard.henderson@linaro.org>
To: Stephen Long <steplong@quicinc.com>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, apazos@quicinc.com
Subject: Re: [PATCH] target/arm: Implement SVE2 scatter store insns
Date: Tue, 21 Apr 2020 20:29:57 -0700 [thread overview]
Message-ID: <75ad766b-c687-1b57-03dc-521bed73281a@linaro.org> (raw)
In-Reply-To: <20200420204203.13279-1-steplong@quicinc.com>
On 4/20/20 1:42 PM, Stephen Long wrote:
> +static bool trans_ST1_zprz_sve2(DisasContext *s, arg_ST1_zprz_sve2 *a)
> +{
> + gen_helper_gvec_mem_scatter *fn;
> + bool be = s->be_data == MO_BE;
> + bool mte = s->mte_active[0];
> +
> + if (!dc_isar_feature(aa64_sve2, s) || a->esz < a->msz
> + || (a->msz == 0 && a->scale)) {
> + return false;
> + }
> + if (!sve_access_check(s)) {
> + return true;
> + }
> + switch (a->esz) {
> + case MO_32:
> + fn = scatter_store_fn32[mte][be][a->xs][a->msz];
> + break;
> + case MO_64:
> + fn = scatter_store_fn64[mte][be][a->xs][a->msz];
> + break;
> + default:
> + g_assert_not_reached();
> + }
> + do_mem_zpz(s, a->rd, a->pg, a->rm, a->scale * a->msz,
> + cpu_reg_sp(s, a->rn), a->msz, true, fn);
> + return true;
> +}
I was thinking of something more along the lines of
static bool STNT1_zprz(DisasContext *s, arg_ST1_zprz *a)
{
if (!dc_isar_feature(aa64_sve2, s)) {
return false;
}
return trans_ST1_zprz(s, a);
}
The fields should be identical, and so decodetree should pick the same type for
'a', underneath all of the typedefs.
If decodetree cannot find a common argument set for the two insns, we might
need to help it along, like we do with e.g. &rri_esz. I don't know without
trying if that will be required.
r~
prev parent reply other threads:[~2020-04-22 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 20:42 [PATCH] target/arm: Implement SVE2 scatter store insns Stephen Long
2020-04-22 3:29 ` Richard Henderson [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=75ad766b-c687-1b57-03dc-521bed73281a@linaro.org \
--to=richard.henderson@linaro.org \
--cc=apazos@quicinc.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steplong@quicinc.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).