From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: peter.maydell@linaro.org, pbonzini@redhat.com,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2] configure: Force the C standard to gnu99
Date: Wed, 9 Jan 2019 15:51:33 +0100 [thread overview]
Message-ID: <21c94e77-ad1d-3ce2-72cd-fc86f6d619fc@redhat.com> (raw)
In-Reply-To: <20190109143122.GR3998@redhat.com>
On 2019-01-09 15:31, Daniel P. Berrangé wrote:
> On Wed, Jan 09, 2019 at 03:24:29PM +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 is
>> GCC v4.8, our best option is "gnu99" right now ("gnu17" is not available
>> there yet, and "gnu11" is marked as "experimental").
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> v2: Use gnu99 instead of gnu11
>>
>> configure | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
>> diff --git a/configure b/configure
>> index b9f34af..721ade7 100755
>> --- a/configure
>> +++ b/configure
>> @@ -105,7 +105,8 @@ update_cxxflags() {
>> for arg in $QEMU_CFLAGS; do
>> case $arg in
>> -Wstrict-prototypes|-Wmissing-prototypes|-Wnested-externs|\
>> - -Wold-style-declaration|-Wold-style-definition|-Wredundant-decls)
>> + -Wold-style-declaration|-Wold-style-definition|-Wredundant-decls|\
>> + -std=gnu99)
>
> IIUC this is to drop -std=gnu99 from CXXFLAGS, so C++ code (only the
> guest-agent on Win32 IIUC) will use the compiler default still.
We also use it for the capstone disassembler and disas/libvixl.
> We could consider also setting a suitable -std for CXXFLAGS too in future
> though...
Shall I send a v3 with "-std=gnu++98" (which seems to be the only usable
option right now), or shall we wait until we really hit a problem with
the C++ code?
Thomas
next prev parent reply other threads:[~2019-01-09 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 14:24 [Qemu-devel] [PATCH v2] configure: Force the C standard to gnu99 Thomas Huth
2019-01-09 14:31 ` Daniel P. Berrangé
2019-01-09 14:51 ` Thomas Huth [this message]
2019-01-09 14:58 ` Daniel P. Berrangé
2019-01-09 15:06 ` 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=21c94e77-ad1d-3ce2-72cd-fc86f6d619fc@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).