All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@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 12:25:43 +0100	[thread overview]
Message-ID: <ac1072de-07a9-3630-bf97-fd04c9f2de8a@redhat.com> (raw)
In-Reply-To: <20190109105818.GG3998@redhat.com>

On 2019-01-09 11:58, Daniel P. Berrangé wrote:
> 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".

gnu11 has the big advantage that it also fixes the problem with
duplicated typedefs that are reported by older versions of Clang.

Are you sure about the experimental character in 4.x? I just looked at
https://gcc.gnu.org/onlinedocs/gcc-4.8.5/gcc/Standards.html and it says:

"A fourth version of the C standard, known as C11, was published in 2011
as ISO/IEC 9899:2011. GCC has limited incomplete support for parts of
this standard, enabled with -std=c11 or -std=iso9899:2011."

It does not say anything about "experimental" there. The word
"experimental" is only used for the C++ support, but we hardly have C++
code in QEMU -- if you worry about that, I could simply drop the
"-std=gnu++11" part from my patch?

 Thomas

  reply	other threads:[~2019-01-09 11:25 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é
2019-01-09 11:25   ` Thomas Huth [this message]
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=ac1072de-07a9-3630-bf97-fd04c9f2de8a@redhat.com \
    --to=thuth@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 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.