From: <jiang.biao2@zte.com.cn>
To: rth@twiddle.net
Cc: qemu-devel@nongnu.org, james.hogan@imgtec.com,
zhong.weidong@zte.com.cn, wang.liang82@zte.com.cn,
shi.zhongbing@zte.com.cn, jinguojie@loongson.cn,
jiang.yong5@zte.com.cn
Subject: Re: [Qemu-devel] [PATCH] tcg/mips: Bugfix for crash when runningprogram with qemu-i386.
Date: Mon, 10 Jul 2017 10:04:39 +0800 (CST) [thread overview]
Message-ID: <201707101004393739204@zte.com.cn> (raw)
>> if (TCG_TARGET_REG_BITS > TARGET_LONG_BITS) {
>> tcg_out_ext32u(s, base, addr_regl)
>> - addr_regl = base
>> + tcg_out_mov(s, TCG_TYPE_PTR, addr_regl, base)
>> }
>> if (guest_base == 0 && data_regl != addr_regl) {
>> base = addr_regl
>
> This is wrong, because you're not allowed to modify the input operands.
>
> Try this, just a few lines lower in the function:
> - tcg_out_movi(s, TCG_TYPE_PTR, base, guest_base)
> - tcg_out_opc_reg(s, ALIAS_PADD, base, base, addr_regl)
> + tcg_out_movi(s, TCG_TYPE_PTR, TCG_TMP0, guest_base)
> + tcg_out_opc_reg(s, ALIAS_PADD, base, TCG_TMP0, addr_regl)
>
Got it, but the real problem is for addr_regl instead of guest_base.
Using your code for reference, I'll use TCG_TMP0 for addr_regl instead
of modifying it, and then send patch of new version later.
>
> and you'll need the same change within tcg_out_qemu_st.
I'll write a test demo to produce crash in tcg_out_qemu_st flow, and send
another patch for that.
> Better would be to reserve a register for the guest_base, like we do for ppc.
> See all of the uses of TCG_GUEST_BASE_REG in tcg/ppc/tcg-target.inc.c.
It uses base(TCG_REG_A0) for temperary use for guest_base in this case.
Thanks a lot.
next reply other threads:[~2017-07-10 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 2:04 jiang.biao2 [this message]
2017-07-10 2:15 ` [Qemu-devel] [PATCH] tcg/mips: Bugfix for crash when runningprogram with qemu-i386 Richard Henderson
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=201707101004393739204@zte.com.cn \
--to=jiang.biao2@zte.com.cn \
--cc=james.hogan@imgtec.com \
--cc=jiang.yong5@zte.com.cn \
--cc=jinguojie@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=shi.zhongbing@zte.com.cn \
--cc=wang.liang82@zte.com.cn \
--cc=zhong.weidong@zte.com.cn \
/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).