From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Ed Maste <emaste@freebsd.org>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Li-Wen Hsu <lwhsu@freebsd.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 1/3] configure: Fix atomic64 test for --enable-werror on macOS
Date: Mon, 27 Jul 2020 14:14:21 +0100 [thread overview]
Message-ID: <878sf53xsi.fsf@linaro.org> (raw)
In-Reply-To: <20200724143220.32751-2-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> 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]
>
> Seems like these __atomic_*_8 functions are available in one of the
> libraries there, so that the test links and passes there when not
> using --enable-werror. But there does not seem to be a valid prototype
> for them in any of the header files, so that the test fails when using
> --enable-werror.
>
> Fix it by using the "official" built-in functions instead (see e.g.
> https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html).
> We are not using the *_8 variants in QEMU anyway.
>
> Suggested-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
This also fixes the failure to set CONFIG_ATOMIC64 for clang (9 and
others) which didn't fail on my box but was certainly missing.
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Tested-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
next prev parent reply other threads:[~2020-07-27 13:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 14:32 [PATCH 0/3] Improve FreeBSD and macOS jobs in the Cirrus-CI Thomas Huth
2020-07-24 14:32 ` [PATCH 1/3] configure: Fix atomic64 test for --enable-werror on macOS Thomas Huth
2020-07-24 15:01 ` Christian Schoenebeck
2020-07-27 13:14 ` Alex Bennée [this message]
2020-07-24 14:32 ` [PATCH 2/3] cirrus.yml: Compile macOS and FreeBSD with -Werror Thomas Huth
2020-07-24 14:46 ` Daniel P. Berrangé
2020-07-24 16:46 ` Philippe Mathieu-Daudé
2020-07-24 16:49 ` Daniel P. Berrangé
2020-07-27 5:44 ` Thomas Huth
2020-07-27 8:30 ` Peter Maydell
2020-07-27 8:45 ` Thomas Huth
2020-07-24 16:50 ` Peter Maydell
2020-07-24 17:21 ` Christian Schoenebeck
2020-07-27 10:57 ` Daniel P. Berrangé
2020-07-28 6:43 ` Thomas Huth
2020-07-28 10:02 ` Daniel P. Berrangé
2020-07-24 15:01 ` Peter Maydell
2020-07-26 16:14 ` Ed Maste
2020-07-26 17:19 ` Christian Schoenebeck
2020-07-27 15:14 ` Thomas Huth
2020-07-24 14:32 ` [PATCH 3/3] cirrus.yml: Update the macOS jobs to Catalina Thomas Huth
2020-07-26 16:18 ` Ed Maste
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=878sf53xsi.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--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 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).