From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 03/10] target/arm: Convert Neon VSHR 2-reg-shift insns to decodetree
Date: Fri, 15 May 2020 15:48:51 -0700 [thread overview]
Message-ID: <bb092cca-f5cf-f0fa-40ff-56b405e5035b@linaro.org> (raw)
In-Reply-To: <20200515142056.21346-4-peter.maydell@linaro.org>
On 5/15/20 7:20 AM, Peter Maydell wrote:
> +VSHR_S_2sh 1111 001 0 1 . ...... .... 0000 1 . . 1 .... \
> + @2reg_shift size=3 shift=%neon_rshift_i6
> +VSHR_S_2sh 1111 001 0 1 . 1 ..... .... 0000 0 . . 1 .... \
> + @2reg_shift size=2 shift=%neon_rshift_i5
> +VSHR_S_2sh 1111 001 0 1 . 01 .... .... 0000 0 . . 1 .... \
> + @2reg_shift size=1 shift=%neon_rshift_i4
> +VSHR_S_2sh 1111 001 0 1 . 001 ... .... 0000 0 . . 1 .... \
> + @2reg_shift size=0 shift=%neon_rshift_i3
It would be worth creating new @formats for each of these, since there are 9
uses of each, between this patch and the next.
E.g.
@2reg_shr_b .... .... ..00 1... .... .... . q:1 0. .... \
&2reg_shift vm=%vm_dp vd=%vd_dp size=0 \
shift=%neon_rshift_i3
@2reg_shr_h .... .... ..01 .... .... .... . q:1 0. .... \
&2reg_shift vm=%vm_dp vd=%vd_dp size=1 \
shift=%neon_rshift_i4
@2reg_shr_s .... .... ..1. .... .... .... . q:1 0. .... \
&2reg_shift vm=%vm_dp vd=%vd_dp size=2 \
shift=%neon_rshift_i5
@2reg_shr_d .... .... .... .... .... .... . q:1 1. .... \
&2reg_shift vm=%vm_dp vd=%vd_dp size=2 \
shift=%neon_rshift_i6
r~
next prev parent reply other threads:[~2020-05-15 22:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 14:20 [PATCH 00/10] target/arm: Convert 2-reg-shift and 1-reg-imm Neon insns to decodetree Peter Maydell
2020-05-15 14:20 ` [PATCH 01/10] target/arm: Remove unused GEN_NEON_INTEGER_OP macro Peter Maydell
2020-05-15 22:07 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 02/10] target/arm: Convert Neon VSHL and VSLI 2-reg-shift insn to decodetree Peter Maydell
2020-05-15 22:16 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 03/10] target/arm: Convert Neon VSHR 2-reg-shift insns " Peter Maydell
2020-05-15 22:33 ` Richard Henderson
2020-05-15 22:48 ` Richard Henderson [this message]
2020-05-15 14:20 ` [PATCH 04/10] target/arm: Convert Neon VSRA, VSRI, VRSHR, VRSRA " Peter Maydell
2020-05-15 22:50 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 05/10] target/arm: Convert VQSHLU, VQSHL " Peter Maydell
2020-05-15 22:55 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 06/10] target/arm: Convert Neon narrowing shifts with op==8 " Peter Maydell
2020-05-16 2:01 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 07/10] target/arm: Convert Neon narrowing shifts with op==9 " Peter Maydell
2020-05-16 2:05 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 08/10] target/arm: Convert Neon VSHLL, VMOVL " Peter Maydell
2020-05-16 2:18 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 09/10] target/arm: Convert VCVT fixed-point ops " Peter Maydell
2020-05-16 2:27 ` Richard Henderson
2020-05-15 14:20 ` [PATCH 10/10] target/arm: Convert Neon one-register-and-immediate insns " Peter Maydell
2020-05-16 2:50 ` Richard Henderson
2020-05-22 14:31 ` Peter Maydell
2020-05-15 21:32 ` [PATCH 00/10] target/arm: Convert 2-reg-shift and 1-reg-imm Neon " no-reply
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=bb092cca-f5cf-f0fa-40ff-56b405e5035b@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).