From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH] meson: disable libatomic with GCC >= 16
Date: Thu, 8 Jan 2026 15:27:32 +0000 [thread overview]
Message-ID: <aV_M5KbihAMR48zn@redhat.com> (raw)
In-Reply-To: <56548949-8afd-4bcc-b539-bfb1a28c3987@redhat.com>
On Thu, Jan 08, 2026 at 04:15:38PM +0100, Paolo Bonzini wrote:
> On 1/8/26 15:14, Daniel P. Berrangé wrote:
> > Historically it was required to ask for libatomic explicitly with
> > -latomic, but with GCC >= 16 apps will get linked to libatomic
> > whether they ask for it or not.
> >
> > This invalidates QEMU's check for atomic op support for int128
> > which explicitly does NOT want to use the libatomic impl. As a
> > result with GCC >= 16, QEMU is now getting linked to libatomic
> > and is activating CONFIG_ATOMIC128. This in turn exposes a bug
> > in GCC's libatomic.a static buld which is incompatible with the
> > use of -static-pie leading to build failures like:
> >
> > /usr/bin/ld: /usr/lib/gcc/x86_64-redhat-linux/16/libatomic.a(cas_16_.o): relocation R_X86_64_32 against hidden symbol `libat_compare_exchange_16_i1' can not be used when making a PIE object
> > /usr/bin/ld: failed to set dynamic section sizes: bad value
> > collect2: error: ld returned 1 exit status
> >
> > The newly introduced -fno-link-libatomic flag can be used to
> > disable the new automatic linking of libatomic. Setting this in
> > qemu_isa_flags early on ensures that the check for CONFIG_ATOMIC128
> > still works correctly.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > meson.build | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/meson.build b/meson.build
> > index db87358d62..56df08c10e 100644
> > --- a/meson.build
> > +++ b/meson.build
> > @@ -445,6 +445,15 @@ if host_arch in ['i386', 'x86_64']
> > endif
> > endif
> > +# GCC >= 16 automatically tries to link libatomic for all programs.
> > +#
> > +# QEMU explicitly does NOT want to use libatomic for int128 types.
> > +#
> > +# Later checks assume we won't get atomic ops for int128 without
> > +# explicitly asking for -latomic, so we must disable GCC's new
> > +# automatic linking with the new -fno-link-libatomic flag
> > +qemu_isa_flags += cc.get_supported_arguments('-fno-link-libatomic')
> > +
> > qemu_common_flags = qemu_isa_flags + qemu_common_flags
> > if get_option('prefer_static')
>
> Great. :/ Is there a bug reported for the -static-pie issue?
GCC maintainers tell me that -static-pie is unsupported for anything
except libgcc.a / libstdc++.a:
https://bugzilla.redhat.com/show_bug.cgi?id=2427891#c10
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2026-01-08 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 14:14 [PATCH] meson: disable libatomic with GCC >= 16 Daniel P. Berrangé
2026-01-08 15:15 ` Paolo Bonzini
2026-01-08 15:27 ` Daniel P. Berrangé [this message]
2026-01-11 0:21 ` 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=aV_M5KbihAMR48zn@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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 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.