From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Sean Bruno <sbruno@freebsd.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [FreeBSD] Host build i386 failing to build aarch64 targets
Date: Mon, 21 Mar 2016 11:49:02 +0000 [thread overview]
Message-ID: <87r3f4rqz5.fsf@linaro.org> (raw)
In-Reply-To: <56EFD9C4.4090601@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 21/03/2016 10:35, Peter Maydell wrote:
>> > x86 can actually do 64-bit atomic loads and stores through the FPU, but
>> > I'm not sure about other 32-bit targets?
>>
>> As I say, ppc32 linux is one that can't -- see commit 8a5956ad6392f1155
>> for last time this came up.
>
> Yes, I remember that. Loads and stores are different from RMW
> operations, though.
>
>> Ideally we should put a compile-time assert in the atomic ops that
>> the data being operated on isn't larger than sizeof(void*) so that
>> this is a compile time error on all 32-bit hosts rather than just
>> a small subset of them.
>
> Yes, I will do it if Alex doesn't beat me to it.
I'm working on it now.
- fix build failures on 32bit hosts (Linux/BSD)
- add compile-time assert for sizeof <= sizeof (void*)
Anything else?
>
> Paolo
--
Alex Bennée
next prev parent reply other threads:[~2016-03-21 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 19:20 [Qemu-devel] [FreeBSD] Host build i386 failing to build aarch64 targets Sean Bruno
2016-03-20 20:03 ` Peter Maydell
2016-03-21 9:11 ` Alex Bennée
2016-03-21 14:52 ` Sean Bruno
2016-03-21 15:36 ` Alex Bennée
2016-03-21 15:56 ` Paolo Bonzini
2016-03-22 16:10 ` Sean Bruno
2016-03-22 16:22 ` Alex Bennée
2016-03-28 17:00 ` Sean Bruno
2016-03-31 16:57 ` Sean Bruno
2016-03-21 9:06 ` Paolo Bonzini
2016-03-21 9:35 ` Peter Maydell
2016-03-21 11:23 ` Paolo Bonzini
2016-03-21 11:49 ` Alex Bennée [this message]
2016-04-06 16:11 ` Sean Bruno
2016-04-06 18:51 ` Alex Bennée
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=87r3f4rqz5.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sbruno@freebsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.