From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mips 64 emulation not compiling
Date: Sat, 27 Oct 2007 16:01:40 +0300 [thread overview]
Message-ID: <f43fc5580710270601haf985dem6bc7d92f40cf3082@mail.gmail.com> (raw)
In-Reply-To: <1193487891.16781.280.camel@rapid>
On 10/27/07, J. Mayer <l_indien@magic.fr> wrote:
> I also got optimized versions of bit population count which could also
> be shared:
> static always_inline int ctpop32 (uint32_t val)
> {
> int i;
>
> for (i = 0; val != 0; i++)
> val = val ^ (val - 1);
>
> return i;
> }
>
> If you prefer, I can add those shared functions (ctz32, ctz64, cto32,
> cto64, ctpop32, ctpop64) later, as they do not seem as widely used as
> clxxx functions.
This would be interesting for Sparc64. Could you compare your version
to do_popc() in target-sparc/op_helper.c?
next prev parent reply other threads:[~2007-10-27 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 10:41 [Qemu-devel] Mips 64 emulation not compiling J. Mayer
2007-10-27 11:19 ` Thiemo Seufer
2007-10-27 12:24 ` J. Mayer
2007-10-27 13:01 ` Blue Swirl [this message]
2007-10-27 13:22 ` J. Mayer
2007-10-27 13:27 ` Christian "Eddie" Dost
2007-10-27 14:12 ` J. Mayer
2007-10-27 13:08 ` Thiemo Seufer
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=f43fc5580710270601haf985dem6bc7d92f40cf3082@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).