From: Richard Henderson <rth@twiddle.net>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-m68k: add rol/ror/roxl/roxr instructions
Date: Wed, 9 Nov 2016 20:39:24 +0100 [thread overview]
Message-ID: <a762c9d1-e8f1-73b7-c52f-f837d217911b@twiddle.net> (raw)
In-Reply-To: <c530a2ff-ffdc-2e39-2957-261db4046ebf@twiddle.net>
On 11/09/2016 07:47 PM, Richard Henderson wrote:
> On 11/09/2016 06:30 PM, Laurent Vivier wrote:
>> + /* create [src:X:..] */
>> +
>> + tcg_gen_deposit_i32(t0, QREG_CC_X, src, 1, size);
>> + tcg_gen_shli_i32(t0, t0, 31 - size);
>> +
>> + /* rotate */
>> +
>> + tcg_gen_rotl_i32(t0, t0, shift);
>> +
>> + /* result is [src:..:src:X] */
>> +
>> + tcg_gen_andi_i32(X, t0, 1);
>> + tcg_gen_shri_i32(t0, t0, 1);
>
> I don't see how this is supposed to work. If you form [src:x:...], and rotate
> by 0, then X gets garbage. Of course, you're actually forming [0:src:x]. But
> for a rol of 2, the lsb of src gets 0's instead of the msb of src.
>
> If you want to use a 32-bit rotate here, you have to (1) reduce the rotate by
> modulo size + 1 and (2) form [src:...:src:x]. E.g.
>
> tcg_gen_deposit_i32(t0, Q_REG_CC_X, src, 32 - size, size);
> tcg_gen_deposit_i32(t0, t0, src, 1, size);
Feh, actually that only works for rot8, since you need 2*size+1 bits available
for this. Why not just use shifts. Something like
int shl = shift % 17;
int shr = shl ^ (size - 1);
int shx = shl ? shl - 1 : 16;
res32 = (data << shl) | (data >> shr) | (x << shx);
x = (res32 >> 16) & 1;
r~
next prev parent reply other threads:[~2016-11-09 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 17:30 [Qemu-devel] [PATCH] target-m68k: add rol/ror/roxl/roxr instructions Laurent Vivier
2016-11-09 18:47 ` Richard Henderson
2016-11-09 19:39 ` Richard Henderson [this message]
2016-11-09 20:22 ` Laurent Vivier
2016-11-10 13:05 ` 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=a762c9d1-e8f1-73b7-c52f-f837d217911b@twiddle.net \
--to=rth@twiddle.net \
--cc=laurent@vivier.eu \
--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).