From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH for-4.0] compiler.h: Add an explicit check for the compiler version
Date: Fri, 30 Nov 2018 13:46:42 +0100 [thread overview]
Message-ID: <eb933208-6ee6-7f2a-dc14-bffbfa76cfad@redhat.com> (raw)
In-Reply-To: <2acf4de2-d826-c2a4-c826-8c966b5cce9e@redhat.com>
On 30/11/18 13:30, Thomas Huth wrote:
> Do we really want to artificially limit our support here without any
> further reasons? If the users want to compile QEMU on an older system,
> and one of the libraries does not quite match anymore, it's often easy
> enough to recompile a newer version of the library to get things going
> again. Recompiling a whole compiler is way more cumbersome, though...
>
> OTOH, we could get rid of some more #if QEMU_GNUC_PREREQ spots in the
> source code if we bump the minimum version to 4.8 ... so that might be a
> real reason to increase the minimum.
Of all of them, I think, if we bump to 4.7?
Older 4.6 and 4.7 version have the PR55489 bug that we're checking for
in configure, too ("we should be able to delete this at the end of 2013"
:)). Bumping to 4.8 would let us remove TRANSLATE_OPT_CFLAGS for good.
Paolo
>> We would need an explicit check for clang, however, instead of
>> relying on it claiming gcc 4.2 support - that's a way inaccurate
>> claim anyway so detecting a specific clang version would be
>> better regardless IMHO
>
> Fine for me if we bump the minimum Clang version to 3.4 ... then we
> could get rid of the the CONFIG_INT128 hacks that we have in various
> parts of the code.
>
> Thomas
>
next prev parent reply other threads:[~2018-11-30 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 10:43 [Qemu-devel] [PATCH for-4.0] compiler.h: Add an explicit check for the compiler version Thomas Huth
2018-11-30 10:46 ` Paolo Bonzini
2018-11-30 11:15 ` Daniel P. Berrangé
2018-11-30 12:30 ` Thomas Huth
2018-11-30 12:46 ` Paolo Bonzini [this message]
2018-11-30 12:52 ` Thomas Huth
2018-11-30 14:47 ` Daniel P. Berrangé
2018-11-30 13:04 ` Daniel P. Berrangé
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=eb933208-6ee6-7f2a-dc14-bffbfa76cfad@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).