From: Blue Swirl <blauwirbel@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/5] tcg-sparc improvements
Date: Tue, 12 Jan 2010 20:02:52 +0000 [thread overview]
Message-ID: <f43fc5581001121202h660b8a8eic156e99b6c40f4a0@mail.gmail.com> (raw)
In-Reply-To: <cover.1263237726.git.rth@twiddle.net>
On Mon, Jan 11, 2010 at 7:22 PM, Richard Henderson <rth@twiddle.net> wrote:
> As noticed elsewhere on the list mulu2_i32 is missing. Which led
> me to notice that add2_i32 and sub2_i32 were also missing and also
> led me to notice that division was incorrectly implemented.
>
> My initial implementation of 32-bit division copied the existing practice
> of using the 64-bit division insns for sparcv9, with proper sign/zero
> extensions on the input operands. But that required extra temporaries
> and quickly got ugly. In the end I thought it was clearer to simply use
> the 32-bit division insns unconditionally.
>
> That excercise, however, made me notice that 32-bit extension was not
> special-cased, leading to the final patch.
Thanks, applied all (4/5 with your fix).
prev parent reply other threads:[~2010-01-12 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 19:22 [Qemu-devel] [PATCH 0/5] tcg-sparc improvements Richard Henderson
2010-01-11 17:51 ` [Qemu-devel] [PATCH 1/5] tcg-sparc: Add tcg_out_arithc Richard Henderson
2010-01-11 17:57 ` [Qemu-devel] [PATCH 2/5] tcg-sparc: Implement add2, sub2, mulu2 Richard Henderson
2010-01-11 19:00 ` [Qemu-devel] [PATCH 3/5] tcg-sparc: Do not remove %o[012] from 'r' constraint Richard Henderson
2010-01-11 19:09 ` [Qemu-devel] [PATCH 4/5] tcg-sparc: Implement division properly Richard Henderson
2010-01-11 20:11 ` Richard Henderson
2010-01-11 19:21 ` [Qemu-devel] [PATCH 5/5] tcg-sparc: Implement ext32[su]_i64 Richard Henderson
2010-01-11 20:41 ` [Qemu-devel] [PATCH 0/5] tcg-sparc improvements Palle Lyckegaard
2010-01-12 20:02 ` Blue Swirl [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=f43fc5581001121202h660b8a8eic156e99b6c40f4a0@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).