QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org,
	"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: Re: [PATCH 0/4] Bump min compiler versions again
Date: Thu, 10 Sep 2026 19:24:19 +0100	[thread overview]
Message-ID: <aqL10x_fBt5ONHTr@redhat.com> (raw)
In-Reply-To: <8df75343-61c8-4af9-901b-0e388a029e1b@linaro.org>

On Thu, Sep 10, 2026 at 08:04:10AM -1000, Richard Henderson wrote:
> On 9/3/26 00:35, Daniel P. Berrangé wrote:
> > We could bump to 12.x and force NetBSD users into use of
> > the non-default versions, but the last patch took the view
> > that we can just warn that use of old GCC versions takes
> > you outside the security policy.  If people prefer the
> > former though, I can respin.
> 
> In patch 3's commit message you mention that NetBSD has clang 21.  I think
> I'd be happier just rejecting gcc 10 and letting NetBSD compile with clang
> instead.  If someone really wants to build with gcc on NetBSD, they can take
> the extra step of using the pkg version.

NB, that would mean rejecting their "system" compiler since IIUC
they use GCC for that.  Having said that, this will resolve itself
with newer NetBSD, and NetBSD users are rare enough that this is
likely not a major inconvenience.

With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



      reply	other threads:[~2026-09-10 18:24 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 ` [PATCH 4/4] meson: warn on GCC < 12.0 due to lack of -ftrivial-auto-var-init=zero Daniel P. Berrangé
2026-09-03 11:28   ` 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é [this message]

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=aqL10x_fBt5ONHTr@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 \
    --cc=richard.henderson@linaro.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