From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH 4/4] meson: warn on GCC < 12.0 due to lack of -ftrivial-auto-var-init=zero
Date: Thu, 3 Sep 2026 11:35:48 +0100 [thread overview]
Message-ID: <20260903103548.2142568-5-berrange@redhat.com> (raw)
In-Reply-To: <20260903103548.2142568-1-berrange@redhat.com>
The security policy for assigning CVEs has an assumption that all
stack variables are zero initialized. Our CLang min version gives
us -ftrivial-auto-var-init=zero, but that is only available in GCC
12 onwards.
Our min GCC is 10.4 but only NetBSD has such an old version.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
meson.build | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/meson.build b/meson.build
index 5315420a41..eeca8d074a 100644
--- a/meson.build
+++ b/meson.build
@@ -327,6 +327,12 @@ endif
foreach lang : all_languages
compiler = meson.get_compiler(lang)
if compiler.get_id() == 'gcc' and compiler.version().version_compare('>=10.4')
+ if not compiler.version().version_compare('>=12.0')
+ warning('GCC < 12.0 does not support -ftrivial-auto-var-init=zero.')
+ warning('This compiler will not satisfy the QEMU security policy ')
+ warning('for assigning CVE which is predicated on zero-initialization ')
+ warning('of stack variables. Update to GCC 12.0 or use CLang >= 17.0 ')
+ endif
# ok
elif compiler.get_id() == 'clang' and compiler.compiles('''
#ifdef __apple_build_version__
--
2.55.0
next prev parent reply other threads:[~2026-09-03 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 10:35 [PATCH 0/4] Bump min compiler versions again Daniel P. Berrangé
2026-09-03 10:35 ` [PATCH 1/4] meson: simplify clang version checks Daniel P. Berrangé
2026-09-03 11:35 ` Marc-André Lureau
2026-09-03 11:37 ` Daniel P. Berrangé
2026-09-03 10:35 ` [PATCH 2/4] meson: bump min XCode CLang to 17.0 Daniel P. Berrangé
2026-09-03 10:41 ` Philippe Mathieu-Daudé
2026-09-03 10:35 ` [PATCH 3/4] meson: bump min upstream " Daniel P. Berrangé
2026-09-03 11:30 ` Marc-André Lureau
2026-09-03 10:35 ` Daniel P. Berrangé [this message]
2026-09-03 11:28 ` [PATCH 4/4] meson: warn on GCC < 12.0 due to lack of -ftrivial-auto-var-init=zero Marc-André Lureau
2026-09-03 16:22 ` [PATCH 0/4] Bump min compiler versions again Pierrick Bouvier
2026-09-10 18:04 ` Richard Henderson
2026-09-10 18:24 ` 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=20260903103548.2142568-5-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@mailo.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.