From: "Christian \"Eddie\" Dost" <ecd@brainaid.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Mips 64 emulation not compiling
Date: Sat, 27 Oct 2007 15:27:01 +0200 [thread overview]
Message-ID: <47233CA5.3070509@brainaid.de> (raw)
In-Reply-To: <f43fc5580710270601haf985dem6bc7d92f40cf3082@mail.gmail.com>
The sparc64 popc works in O(lg(n)), the "optimized" code below work in
O(n). Could be better to generalize the sparc64 code, like this:
static always_inline int ctpop32 (uint32_t val)
{
uint32_t i;
i = (val & 0x55555555) + ((val >> 1) & 0x55555555);
i = (i & 0x33333333) + ((i >> 2) & 0x33333333);
i = (i & 0x0f0f0f0f) + ((i >> 4) & 0x0f0f0f0f);
i = (i & 0x00ff00ff) + ((i >> 8) & 0x00ff00ff);
i = (i & 0x0000ffff) + ((i >> 16) & 0x0000ffff);
return i;
}
For the 64 bit version see target-sparc/op_helper.c
Best regards,
Eddie
Blue Swirl wrote:
> 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?
>
>
--
___________________________________________________brainaid_____________
Eddie C. Dost Rue de la Chapelle 51 phone +32 87 788817
B-4850 Moresnet fax +32 87 788818
ecd@brainaid.de Belgium cell +49 172 9312808
next prev parent reply other threads:[~2007-10-27 13:27 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
2007-10-27 13:22 ` J. Mayer
2007-10-27 13:27 ` Christian "Eddie" Dost [this message]
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=47233CA5.3070509@brainaid.de \
--to=ecd@brainaid.de \
--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).