From: Stefan Weil <sw@weilnetz.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Juan Quintela <quintela@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Orit Wasserman <owasserm@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 14/42] migration: prepare to access s->state outside critical sections
Date: Fri, 29 Mar 2013 18:49:37 +0100 [thread overview]
Message-ID: <5155D431.50701@weilnetz.de> (raw)
In-Reply-To: <1202297355.13036709.1364209368956.JavaMail.root@redhat.com>
Am 25.03.2013 12:02, schrieb Paolo Bonzini:
>
> ----- Messaggio originale -----
>> Da: "Gerd Hoffmann" <kraxel@redhat.com>
>> A: "Stefan Hajnoczi" <stefanha@gmail.com>
>> Cc: "Paolo Bonzini" <pbonzini@redhat.com>, "qemu-devel" <qemu-devel@nongnu.org>, "Orit Wasserman"
>> <owasserm@redhat.com>, "Juan Quintela" <quintela@redhat.com>
>> Inviato: Lunedì, 25 marzo 2013 10:52:36
>> Oggetto: Re: [Qemu-devel] [PATCH 14/42] migration: prepare to access s->state outside critical sections
>>
>> Hi,
>>
>>> http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/566/steps/compile/logs/stdio
>>>
>>> The latest RHEL6 mingw gcc is version 4.4 but this buildslave is
>>> RHEL6.1 so perhaps it's an older version that is missing the
>>> atomics builtins?
>> No, it's RHEL-6.4 actually, even though the name suggests otherwise
>> (was a bad idea to include the minor rev in the buildslave name ...).
> Can you check if this fixes it?
>
> diff --git a/configure b/configure
> index 46a7594..a324ca5 100755
> --- a/configure
> +++ b/configure
> @@ -931,9 +931,9 @@ case "$cpu" in
> LDFLAGS="-m64 $LDFLAGS"
> ;;
> i386)
> - QEMU_CFLAGS="-m32 $QEMU_CFLAGS"
> - LDFLAGS="-m32 $LDFLAGS"
> - cc_i386='$(CC) -m32'
> + QEMU_CFLAGS="-m32 -mcpu=i486 $QEMU_CFLAGS"
> + LDFLAGS="-m32 -mcpu=i486 $LDFLAGS"
> + cc_i386='$(CC) -m32 -mcpu=i486'
> ;;
> x86_64)
> QEMU_CFLAGS="-m64 $QEMU_CFLAGS"
>
> Paolo
Hi Stefan, hi Paolo,
cross compilation on Debian Squeeze shows the same error.
It is fixed by setting the correct cpu architecture (-march=i686).
As far as I know, gcc 4.4 defaults to -march=i386 which does
not support the atomic operations.
I have sent a patch today - please try it.
Regards,
Stefan
prev parent reply other threads:[~2013-03-29 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361551008-12430-1-git-send-email-pbonzini@redhat.com>
[not found] ` <1361551008-12430-24-git-send-email-pbonzini@redhat.com>
2013-03-06 1:34 ` [Qemu-devel] [PATCH 23/42] migration: yay, buffering is gone Wenchao Xia
2013-03-06 6:09 ` Paolo Bonzini
[not found] ` <1361551008-12430-15-git-send-email-pbonzini@redhat.com>
2013-03-25 9:44 ` [Qemu-devel] [PATCH 14/42] migration: prepare to access s->state outside critical sections Stefan Hajnoczi
2013-03-25 9:52 ` Gerd Hoffmann
2013-03-25 11:02 ` Paolo Bonzini
2013-03-29 17:49 ` Stefan Weil [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=5155D431.50701@weilnetz.de \
--to=sw@weilnetz.de \
--cc=kraxel@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).