From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Kyle Evans" <kevans@freebsd.org>, "Warner Losh" <imp@bsdimp.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>
Subject: [PATCH v2 0/5] Bump min compiler versions again
Date: Tue, 15 Sep 2026 09:52:08 +0100 [thread overview]
Message-ID: <20260915085213.139944-1-berrange@redhat.com> (raw)
With the security policy we want to rely on usage of
the -ftrivial-auto-var-init=zero flag to declare
bugs "not a CVE" if they rely on uninitialized stack
variables.
This arg is only supported by CLang 17 or GCC 12 though,
both of which are beyond our current min versions.
This series bumps both CLang and GCC to enable this.
The GCC bump is technically something we shouldn't do per
our platform support matrix, as the system compiler in our
targetted releases of NetBSD, remains GCC 10.4
This series considers it reasonable to bend the rules
slightly, as NetBSD does have new enough CLang, and also
ships newer GCC as non-system compilers.
Also historically the macOS XCode versions reported by
clang did not appear to align with upstream CLang versions
so we checked versions separately for macOS.
With this set of patches we happen to end up on 17.0 for
both upstream CLang and macOS Clang, and this makes me
wonder if we can rely on aligned versions going forward ?
Latest XCode 26.6 apparently reports clang 21.0.0 which
appears to be a match for a modern llvm release.
Daniel P. Berrangé (5):
tests/vm: drop redundant ';' at end of each shell command
meson: simplify clang version checks
meson: bump min XCode CLang to 17.0
meson: bump min upstream CLang to 17.0
meson: bump min GCC to 12.0
meson.build | 12 ++++++------
tests/vm/netbsd | 17 +++++++++++------
2 files changed, 17 insertions(+), 12 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-15 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:52 Daniel P. Berrangé [this message]
2026-09-15 8:52 ` [PATCH v2 1/5] tests/vm: drop redundant '; ' at end of each shell command Daniel P. Berrangé via qemu development
2026-09-15 8:52 ` [PATCH v2 2/5] meson: simplify clang version checks Daniel P. Berrangé
2026-09-15 8:52 ` [PATCH v2 3/5] meson: bump min XCode CLang to 17.0 Daniel P. Berrangé
2026-09-15 8:52 ` [PATCH v2 4/5] meson: bump min upstream " Daniel P. Berrangé
2026-09-15 8:52 ` [PATCH v2 5/5] meson: bump min GCC to 12.0 Daniel P. Berrangé
2026-09-15 14:53 ` [PATCH v2 0/5] Bump min compiler versions again 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=20260915085213.139944-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.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 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.