From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Markus Armbruster <armbru@redhat.com>,
qemu-ppc@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] configure: Force the C standard to gnu99
Date: Wed, 9 Jan 2019 22:26:27 +0100 [thread overview]
Message-ID: <c965133d-f26d-3dba-81ed-1c87038e9b35@redhat.com> (raw)
In-Reply-To: <f1d83216-d9a8-605b-d87b-be6b96f42557@redhat.com>
On 09/01/19 19:10, Philippe Mathieu-Daudé wrote:
> Using '-std=gnu++98' for g++ v4.8 looks like a good compromise to the
> issues Daniel mentioned (still 'experimental').
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
C++11 has many new features that almost make it an entirely different
language (the main being rvalue references, and type inference with auto
and decltype). If it works for GCC 4.8, I would prefer using that
instead of g++98.
Paolo
next prev parent reply other threads:[~2019-01-09 21:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 16:39 [Qemu-devel] [PATCH v3 0/2] Force the C standard to gnu99 Thomas Huth
2019-01-09 16:39 ` [Qemu-devel] [PATCH 1/2] include/hw/ppc: Fix compilation with clang -std=gnu99 Thomas Huth
2019-01-09 17:13 ` [Qemu-devel] [Qemu-ppc] " Cédric Le Goater
2019-01-09 17:28 ` Daniel P. Berrangé
2019-01-09 17:40 ` Cédric Le Goater
2019-01-09 17:47 ` Greg Kurz
2019-01-10 6:47 ` Thomas Huth
2019-01-09 21:20 ` Paolo Bonzini
2019-01-09 21:25 ` Eric Blake
2019-01-09 21:31 ` Paolo Bonzini
2019-01-10 10:12 ` Daniel P. Berrangé
2019-01-10 12:12 ` Greg Kurz
2019-01-10 6:46 ` Thomas Huth
2019-01-09 17:46 ` Cédric Le Goater
2019-01-09 16:39 ` [Qemu-devel] [PATCH v3 2/2] configure: Force the C standard to gnu99 Thomas Huth
2019-01-09 18:10 ` Philippe Mathieu-Daudé
2019-01-09 21:26 ` Paolo Bonzini [this message]
2019-01-10 6:50 ` Thomas Huth
2019-01-09 21:23 ` Richard Henderson
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=c965133d-f26d-3dba-81ed-1c87038e9b35@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).