From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
pbonzini@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] configure: Force the C standard to gnu11
Date: Wed, 9 Jan 2019 10:58:18 +0000 [thread overview]
Message-ID: <20190109105818.GG3998@redhat.com> (raw)
In-Reply-To: <1546857926-5958-1-git-send-email-thuth@redhat.com>
On Mon, Jan 07, 2019 at 11:45:26AM +0100, Thomas Huth wrote:
> Different versions of GCC and Clang use different versions of the C standard.
> This repeatedly caused problems already, e.g. with duplicated typedefs:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg05829.html
>
> or with for-loop variable initializers:
>
> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg00237.html
>
> To avoid these problems, we should enforce the C language version to the
> same level for all compilers. Since our minimum compiler versions are
> GCC v4.8 and Clang v3.4 now, and both basically support "gnu11" already,
> this seems to be a good choice.
In 4.x gnu11 is marked as experimental. I'm not really comfortable
using experimental features - even if its warning free there's a risk
it would silently mis-compile something.
gnu99 is ok with 4.x - it is merely "incomplete".
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> configure | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 79375af..07f8105 100755
> --- a/configure
> +++ b/configure
> @@ -107,6 +107,9 @@ update_cxxflags() {
> -Wstrict-prototypes|-Wmissing-prototypes|-Wnested-externs|\
> -Wold-style-declaration|-Wold-style-definition|-Wredundant-decls)
> ;;
> + -std=gnu11)
> + QEMU_CXXFLAGS=${QEMU_CXXFLAGS:+$QEMU_CXXFLAGS }-std=gnu++11
> + ;;
> *)
> QEMU_CXXFLAGS=${QEMU_CXXFLAGS:+$QEMU_CXXFLAGS }$arg
> ;;
> @@ -585,7 +588,7 @@ ARFLAGS="${ARFLAGS-rv}"
> # left shift of signed integers is well defined and has the expected
> # 2s-complement style results. (Both clang and gcc agree that it
> # provides these semantics.)
> -QEMU_CFLAGS="-fno-strict-aliasing -fno-common -fwrapv $QEMU_CFLAGS"
> +QEMU_CFLAGS="-fno-strict-aliasing -fno-common -fwrapv -std=gnu11 $QEMU_CFLAGS"
> QEMU_CFLAGS="-Wall -Wundef -Wwrite-strings -Wmissing-prototypes $QEMU_CFLAGS"
> QEMU_CFLAGS="-Wstrict-prototypes -Wredundant-decls $QEMU_CFLAGS"
> QEMU_CFLAGS="-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE $QEMU_CFLAGS"
> --
> 1.8.3.1
>
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:[~2019-01-09 10:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:45 [Qemu-devel] [PATCH] configure: Force the C standard to gnu11 Thomas Huth
2019-01-09 10:58 ` Daniel P. Berrangé [this message]
2019-01-09 11:25 ` Thomas Huth
2019-01-09 11:44 ` Daniel P. Berrangé
2019-01-09 12:52 ` Thomas Huth
2019-01-09 12:58 ` Daniel P. Berrangé
2019-01-09 13:20 ` Thomas Huth
2019-01-09 13:27 ` Daniel P. Berrangé
2019-01-09 13:54 ` Thomas Huth
2019-01-09 13:10 ` Markus Armbruster
2019-01-09 13:17 ` Thomas Huth
2019-01-09 14:20 ` Markus Armbruster
2019-01-09 14:27 ` Thomas Huth
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=20190109105818.GG3998@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 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).