From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 3/4] tests/tcg: add alternative cross-compilers for fedora
Date: Fri, 25 Sep 2026 17:00:52 +0100 [thread overview]
Message-ID: <araatB_g6Lw63iZB@redhat.com> (raw)
In-Reply-To: <3e61ce09-b929-4716-95ab-84bf01bef497@oss.qualcomm.com>
On Fri, Sep 25, 2026 at 08:57:08AM -0700, Pierrick Bouvier wrote:
> On 9/25/2026 8:54 AM, Daniel P. Berrangé wrote:
> > On Fri, Sep 25, 2026 at 08:20:44AM -0700, Pierrick Bouvier wrote:
> >> On 9/25/2026 2:40 AM, Daniel P. Berrangé wrote:
> >>> On Thu, Sep 24, 2026 at 09:39:41PM +0000, Pierrick Bouvier wrote:
> >>>> This allows to pick host compiler automatically on fedora, as those
> >>>> binaries are installed with 'gcc' package.
> >>>>
> >>>> This covers all host arch supported to this day:
> >>>> https://fedoraproject.org/wiki/Architectures
> >>>> - x86_64
> >>>> - aarch64
> >>>> - ppc64le
> >>>> - riscv64
> >>>> - s390x
> >>>> Note: QEMU and Fedora don't support 32-bit hosts anymore.
> >>>
> >>> Regardless of what installation arches Fedora targets, it
> >>> ships cross compilers for pretty much everything. In F44
> >>> I see the following GCC available:
> >>>
> >>> gcc-aarch64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-alpha-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-arc-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-arm-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-avr32-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-bfin-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-c6x-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-frv-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-h8300-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-hppa-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-hppa64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-ia64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-loongarch64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-m68k-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-microblaze-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-mips64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-mn10300-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-openrisc-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-powerpc64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-powerpc64le-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-ppc64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-ppc64le-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-riscv32-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-riscv64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-s390x-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-sparc64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-x86_64-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>> gcc-xtensa-linux-gnu.x86_64 16.2.1-1.fc44 updates
> >>>
> >>>
> >>
> >> We want to detect host compiler here (redhat-* variants), as mentioned
> >> in commit description. It addresses original request from Paolo. Cross
> >> compilers above are already detected with current cc field.
> >
> > Oh, I see what you mean. Itis dealing with the naming difference
> > between 'redhat-linux-gnu' and just 'linux-gnu' in the compilers
> > for the native vs cross arch RPMs.
> >
>
> Right.
> I'm not super familiar with Fedora, is there any fundamental difference
> between this toolchain and linux-gnu variant, in terms of ABI or
> anything else? Or is it just a distinction for "Our toolchain with
> additional patches" vs upstream one?
Most of the downstream patches are common to both the native
and cross GCC RPMs. I'm not aware of significant differences
between the two that would matter for QEMU's needs.
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 :|
next prev parent reply other threads:[~2026-09-25 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 21:39 [PATCH 0/4] tests/tcg/meson.build: detect additional cross compilers Pierrick Bouvier
2026-09-24 21:39 ` [PATCH 1/4] tests/tcg/meson.build: report correct cc in summary Pierrick Bouvier
2026-09-25 16:02 ` Daniel P. Berrangé
2026-09-24 21:39 ` [PATCH 2/4] tests/tcg/meson.build: introduce cc_alt (alternative cross compiler) Pierrick Bouvier
2026-09-25 9:38 ` Daniel P. Berrangé
2026-09-25 15:17 ` Pierrick Bouvier
2026-09-25 15:52 ` Daniel P. Berrangé
2026-09-25 16:03 ` Daniel P. Berrangé
2026-09-24 21:39 ` [PATCH 3/4] tests/tcg: add alternative cross-compilers for fedora Pierrick Bouvier
2026-09-25 9:40 ` Daniel P. Berrangé
2026-09-25 15:20 ` Pierrick Bouvier
2026-09-25 15:54 ` Daniel P. Berrangé
2026-09-25 15:57 ` Pierrick Bouvier
2026-09-25 16:00 ` Daniel P. Berrangé [this message]
2026-09-25 16:03 ` Daniel P. Berrangé
2026-09-24 21:39 ` [PATCH 4/4] tests/tcg: add alternative cross-compilers for macos (homebrew) Pierrick Bouvier
2026-09-25 16:04 ` Daniel P. Berrangé
2026-09-25 22:17 ` [PATCH 0/4] tests/tcg/meson.build: detect additional cross compilers Pierrick Bouvier
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=araatB_g6Lw63iZB@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@oss.qualcomm.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 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.