From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [5465] hw/apic.c: use __builtin funtions instead of assembly code
Date: Sun, 12 Oct 2008 12:21:47 +0200 [thread overview]
Message-ID: <48F1CFBB.2000509@web.de> (raw)
In-Reply-To: <E1KopCv-0001X3-Qp@cvs.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Aurelien Jarno wrote:
> Revision: 5465
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5465
> Author: aurel32
> Date: 2008-10-12 00:53:17 +0000 (Sun, 12 Oct 2008)
>
> Log Message:
> -----------
> hw/apic.c: use __builtin funtions instead of assembly code
>
> Suggested by malc.
>
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>
> Modified Paths:
> --------------
> trunk/hw/apic.c
>
> Modified: trunk/hw/apic.c
> ===================================================================
> --- trunk/hw/apic.c 2008-10-12 00:53:08 UTC (rev 5464)
> +++ trunk/hw/apic.c 2008-10-12 00:53:17 UTC (rev 5465)
> @@ -104,15 +104,14 @@
> static void apic_set_irq(APICState *s, int vector_num, int trigger_mode);
> static void apic_update_irq(APICState *s);
>
> -/* Find first bit starting from msb. Return 0 if value = 0 */
> +/* Find first bit starting from msb */
> static int fls_bit(uint32_t value)
> {
> +#if defined(__GNUC__)
> + return 31 - __builtin_clz(value);
That as well as most (if not all) of the __builtin_* changes are gcc3.4+
stuff. Thus gcc3.3 builds are unfortunately broken now.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-10-12 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 0:53 [Qemu-devel] [5465] hw/apic.c: use __builtin funtions instead of assembly code Aurelien Jarno
2008-10-12 10:21 ` Jan Kiszka [this message]
2008-10-12 11:44 ` [Qemu-devel] " Aurelien Jarno
2008-10-12 19:17 ` [Qemu-devel] " Paul Brook
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=48F1CFBB.2000509@web.de \
--to=jan.kiszka@web.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).