From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: peter.maydell@linaro.org, Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] configure: Fix atomic64 test for --enable-werror on macOS
Date: Thu, 16 Jul 2020 15:25:18 +0100 [thread overview]
Message-ID: <20200716142518.GU227735@redhat.com> (raw)
In-Reply-To: <20200716131101.18462-1-thuth@redhat.com>
On Thu, Jul 16, 2020 at 03:11:01PM +0200, Thomas Huth wrote:
> When using --enable-werror for the macOS builders in the Cirrus-CI,
> the atomic64 test is currently failing, and config.log shows a bunch
> of error messages like this:
>
> config-temp/qemu-conf.c:6:7: error: implicit declaration of function
> '__atomic_load_8' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
> y = __atomic_load_8(&x, 0);
> ^
> config-temp/qemu-conf.c:6:7: error: this function declaration is not a
> prototype [-Werror,-Wstrict-prototypes]
>
> Suppress the warnings to make it pass.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> Not sure whether this is the best way to fix this issue ... thus marked
> as RFC.
> Even though the compiler warns here, the program links apparently just
> fine afterwards and CONFIG_ATOMIC64=y gets set in the config-host.mak
> file on macOS, so the 64-bit atomic operations seem to be available...
> Any macOS users here who could shed some light on this?
The error message refers to c99, but QEMU code standard is gnu99.
It doesn't look like we set std=gnu99 when running configure
tests though, and I wonder if that is relevant in this case,
given that the atomic_load* stuff is all compiler built-in.
eg does -std=gnu99 have any impact on the warnings ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-07-16 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 13:11 [RFC PATCH] configure: Fix atomic64 test for --enable-werror on macOS Thomas Huth
2020-07-16 14:07 ` no-reply
2020-07-16 14:15 ` Christian Schoenebeck
2020-07-16 14:30 ` Thomas Huth
2020-07-16 14:25 ` Daniel P. Berrangé [this message]
2020-07-16 14:29 ` Thomas Huth
2020-07-16 14:53 ` Christian Schoenebeck
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=20200716142518.GU227735@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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 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.