From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: Redefinition of typedefs (C11 feature)
Date: Fri, 11 Sep 2020 20:06:10 +0100 [thread overview]
Message-ID: <CAFEAcA-dnKVyUQ3_ZifdDvrpCbKB1zciuu224BbB1WRV0npxzw@mail.gmail.com> (raw)
In-Reply-To: <20200911184919.GV1618070@habkost.net>
On Fri, 11 Sep 2020 at 19:49, Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> I'm wondering: do our supported build host platforms all include
> compilers that are new enough to let us redefine typedefs?
>
> The ability to redefine typedefs is a C11 feature which would be
> very useful for simplifying our QOM boilerplate code. The
> feature is supported by GCC since 2011 (v4.6.0)[1], and by clang
> since 2012 (v3.1)[2].
In configure we mandate either GCC v4.8 or better, or
clang v3.4 or better, or XCode Clang v5.1 or better
(Apple uses a different version numbering setup to upstream).
So you should probably double-check that that xcode clang has
what you want, but it looks like we're good to go otherwise.
thanks
-- PMM
next prev parent reply other threads:[~2020-09-11 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 18:49 Redefinition of typedefs (C11 feature) Eduardo Habkost
2020-09-11 19:06 ` Peter Maydell [this message]
2020-09-11 20:06 ` Moving to C11? (was Re: Redefinition of typedefs (C11 feature)) Eduardo Habkost
2020-09-11 20:10 ` Warner Losh
2020-09-12 8:16 ` Philippe Mathieu-Daudé
2020-09-12 15:04 ` Warner Losh
2020-09-12 6:45 ` Thomas Huth
2020-09-13 2:51 ` Eduardo Habkost
2020-09-14 5:39 ` Thomas Huth
2020-09-14 13:46 ` Eduardo Habkost
2020-09-14 13:50 ` Daniel P. Berrangé
2020-09-14 15:36 ` Thomas Huth
2020-09-14 16:53 ` Eduardo Habkost
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=CAFEAcA-dnKVyUQ3_ZifdDvrpCbKB1zciuu224BbB1WRV0npxzw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).