From: Richard Henderson <rth@twiddle.net>
To: Aurelien Jarno <aurelien@aurel32.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] target-mips: Use new qemu_ld/st opcodes
Date: Wed, 11 Dec 2013 11:12:59 -0800 [thread overview]
Message-ID: <52A8B93B.8070305@twiddle.net> (raw)
In-Reply-To: <1386770856-6304-2-git-send-email-aurelien@aurel32.net>
On 12/11/2013 06:07 AM, Aurelien Jarno wrote:
> - tcg_gen_qemu_st64(t1, t0, ctx->mem_idx);
> + tcg_gen_qemu_st_tl(t1, t0, ctx->mem_idx, MO_TE | MO_64);
MO_TEQ?
> - tcg_gen_qemu_st32(t1, t0, ctx->mem_idx);
> + tcg_gen_qemu_st_tl(t1, t0, ctx->mem_idx, MO_TE | MO_32);
> opn = "sw";
> break;
> case OPC_SH:
> - tcg_gen_qemu_st16(t1, t0, ctx->mem_idx);
> + tcg_gen_qemu_st_tl(t1, t0, ctx->mem_idx, MO_TE | MO_16);
> opn = "sh";
> break;
FWIW, I've been using the unsigned variants for stores, e.g. MO_TEUL.
> @@ -1869,7 +1869,7 @@ static void gen_flt_ldst (DisasContext *ctx, uint32_t opc, int ft,
> {
> TCGv_i32 fp0 = tcg_temp_new_i32();
>
> - tcg_gen_qemu_ld32s(t0, t0, ctx->mem_idx);
> + tcg_gen_qemu_ld_tl(t0, t0, ctx->mem_idx, MO_TESL);
> tcg_gen_trunc_tl_i32(fp0, t0);
> gen_store_fpr32(fp0, ft);
> tcg_temp_free_i32(fp0);
Since you've changed some of the extensions, notice that you can load directly
into fp0 now and avoid the truncates too.
r~
next prev parent reply other threads:[~2013-12-11 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 14:07 [Qemu-devel] [PATCH 1/2] tcg: add TCGMemOp short constants for single byte loads Aurelien Jarno
2013-12-11 14:07 ` [Qemu-devel] [PATCH 2/2] target-mips: Use new qemu_ld/st opcodes Aurelien Jarno
2013-12-11 19:12 ` Richard Henderson [this message]
2013-12-11 19:07 ` [Qemu-devel] [PATCH 1/2] tcg: add TCGMemOp short constants for single byte loads Richard Henderson
2013-12-12 13:33 ` Aurelien Jarno
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=52A8B93B.8070305@twiddle.net \
--to=rth@twiddle.net \
--cc=aurelien@aurel32.net \
--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).