From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] vhost build fix for i386
Date: Mon, 11 Jul 2011 14:31:40 +0100 [thread overview]
Message-ID: <CAJSP0QXPJWRBLPikS1rvPRWpm3CspjwVTToJMoYNf08qZ2QS-Q@mail.gmail.com> (raw)
In-Reply-To: <1310389063-16382-1-git-send-email-wolfgang.mauerer@siemens.com>
On Mon, Jul 11, 2011 at 1:57 PM, Wolfgang Mauerer
<wolfgang.mauerer@siemens.com> wrote:
> vhost.c uses __sync_fetch_and_and(), which is only
> available for -march=i486 and above (see
> https://bugzilla.redhat.com/show_bug.cgi?id=624279).
Seems reasonable. I am happy to add it to the trivial-patches tree
but will wait another day to let others who are better gcc wizards
consider it.
Stefan
next prev parent reply other threads:[~2011-07-11 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 12:57 [Qemu-trivial] [PATCH] vhost build fix for i386 Wolfgang Mauerer
2011-07-11 13:31 ` Stefan Hajnoczi [this message]
2011-07-25 10:17 ` Stefan Hajnoczi
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=CAJSP0QXPJWRBLPikS1rvPRWpm3CspjwVTToJMoYNf08qZ2QS-Q@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=wolfgang.mauerer@siemens.com \
/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).