From: malc <av1474@comtv.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5382] hw/apic.c: use bsr and bsf on x86_64
Date: Thu, 2 Oct 2008 22:00:44 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0810022158240.2161@linmac.oyster.ru> (raw)
In-Reply-To: <E1Kl9WC-0002Ic-87@cvs.savannah.gnu.org>
On Wed, 1 Oct 2008, Aurelien Jarno wrote:
> Revision: 5382
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5382
> Author: aurel32
> Date: 2008-10-01 21:45:59 +0000 (Wed, 01 Oct 2008)
>
> Log Message:
> -----------
> hw/apic.c: use bsr and bsf on x86_64
>
> (C.W. Betts)
>
> Modified Paths:
> --------------
> trunk/hw/apic.c
I think this should just be changed to __builtin_ffs or clz and the
requirement to return 0 on 0 dropped (since all the users do check
for 0 anyway).
[..snip..]
--
mailto:av1474@comtv.ru
prev parent reply other threads:[~2008-10-02 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 21:46 [Qemu-devel] [5382] hw/apic.c: use bsr and bsf on x86_64 Aurelien Jarno
2008-10-02 18:00 ` malc [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=Pine.LNX.4.64.0810022158240.2161@linmac.oyster.ru \
--to=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).