From: Richard Henderson <rth@twiddle.net>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TCG sar UB (fwd)
Date: Tue, 06 Sep 2011 20:18:55 +0530 [thread overview]
Message-ID: <4E6632D7.6070008@twiddle.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1109040632250.1599@linmac>
On 09/04/2011 08:03 AM, malc wrote:
> On Sun, 4 Sep 2011, Richard Henderson wrote:
>
>> On 09/03/2011 03:47 PM, malc wrote:
>>> Doesn't make much sense to me, guest clearly asked for 0 and not -1,
>>> besides -1 violates TCG's sar constraints and PPC obliges by emiting
>>> illegal instruction in this case.
>>
>> The shift that the guest asked for was completely folded away.
>>
>> The -1 comes from gen_shift_rm_T1 in the computation of the new
>> flags value. This could instead be moved inside the test for != 0,
>> which is the only place that value is actually used anyway.
>>
>> Try this. Lightly tested.
>
> Now i either get hosts illegal instruction or (with logging enabled) a
> guest kenrnel panic.
Hum. Well, it's possible I made some silly mistake in the patch.
You now know where to look for the problem.
That said, it seems easier for you in the PPC port to mask the
immediate operand so that you don't produce an illegal instruction.
It doesn't really matter what value that insn produces, as the
result won't be used.
r~
next prev parent reply other threads:[~2011-09-06 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LNX.2.00.1109031417430.1511@linmac>
2011-09-04 2:27 ` [Qemu-devel] TCG sar UB (fwd) Richard Henderson
2011-09-04 2:33 ` malc
2011-09-06 14:48 ` Richard Henderson [this message]
2011-09-06 15:20 ` malc
2011-09-07 5:19 ` Richard Henderson
2011-09-07 16:04 ` malc
2011-09-08 8:23 ` [Qemu-devel] [PATCH] target-i386: Compute all flag data inside %cl != 0 test Richard Henderson
2011-09-08 14:12 ` malc
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=4E6632D7.6070008@twiddle.net \
--to=rth@twiddle.net \
--cc=av1474@comtv.ru \
--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).