From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Mateja Marjanovic <mateja.marjanovic@rt-rk.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH] target/mips/translate: Simplify PCPYH using deposit/extract
Date: Tue, 24 Nov 2020 09:40:42 -0800 [thread overview]
Message-ID: <0106c670-e2cd-0bed-f76f-5a5990f410a7@linaro.org> (raw)
In-Reply-To: <0a1587a0-708b-b537-3065-e9a7a845b326@linaro.org>
On 11/24/20 9:28 AM, Richard Henderson wrote:
>> + tcg_gen_extract_i64(t0, cpu_gpr[a->rt], 0, 16);
>> + tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rd], t0, 0, 16);
>> + tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rd], t0, 16, 16);
>> + tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rd], t0, 32, 16);
>> + tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rd], t0, 48, 16);
>
> Actually, this would be better as
>
> tcg_gen_ext16u_i64(t0, cpu_gpr[rt]);
> tcg_gen_muli_i64(cpu_gpr[a->rd], t0, dup_const(1, MO_16));
Hmm, while that's fine for 64-bit hosts (and ideal for x86_64), it's not ideal
for the 32-bit hosts we have left.
This can also be done with
// replicate lower 16 bits, garbage in upper 32.
tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rt],
cpu_gpr[a->rt], 16, 48);
// replicate lower 32 bits
tcg_gen_deposit_i64(cpu_gpr[a->rd], cpu_gpr[a->rd],
cpu_gpr[a->rd], 32, 32);
r~
prev parent reply other threads:[~2020-11-24 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 10:38 [PATCH] target/mips/translate: Simplify PCPYH using deposit/extract Philippe Mathieu-Daudé
2020-11-24 17:28 ` Richard Henderson
2020-11-24 17:40 ` 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=0106c670-e2cd-0bed-f76f-5a5990f410a7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=mateja.marjanovic@rt-rk.com \
--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).