From: "Daniel P. Berrangé" <berrange@redhat.com>
To: David Michael <fedora.dm0@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] configure: map x32 to cpu_family x86_64 for meson
Date: Wed, 9 Jun 2021 13:45:37 +0100 [thread overview]
Message-ID: <YMC38baIdFTL/q+f@redhat.com> (raw)
In-Reply-To: <878s3jrzm0.fsf@gmail.com>
On Wed, Jun 09, 2021 at 08:28:39AM -0400, David Michael wrote:
> The meson.build file defines supported_cpus which does not contain
> x32, and x32 is not one of meson's stable built-in values:
> https://mesonbuild.com/Reference-tables.html#cpu-families
>
> Signed-off-by: David Michael <fedora.dm0@gmail.com>
> ---
>
> Hi,
>
> QEMU fails to build for x32 due to that cpu_family not being defined in
> supported_cpus. Can something like this be applied?
>
> Alternatively, maybe it could be added to supported_cpus and accepted
> everywhere that matches x86 in meson.build, but upstream meson does not
> define a CPU type for x32.
"supported_cpus" serves two distinct purposes in meson.build
- Identifies whether TCG supports the target
- Identifies whether QEMU maintainers consider the target supported
The change proposed below makes x32 be treated the same as x86_64.
Maybe that's right for the question of TCG support, but I'm less
sure it is right from POV of QEMU maintainers expectations around
the x32 target status. AFAIK, we don't have any CI for x32 and
IIUC no maintainers are actively testing it manually, so it ought
to be in the unsupported category.
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index 8dcb9965b2..4478f3889a 100755
> --- a/configure
> +++ b/configure
> @@ -6384,7 +6384,7 @@ if test "$skip_meson" = no; then
> i386)
> echo "cpu_family = 'x86'" >> $cross
> ;;
> - x86_64)
> + x86_64|x32)
> echo "cpu_family = 'x86_64'" >> $cross
> ;;
> ppc64le)
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:[~2021-06-09 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 12:28 [PATCH] configure: map x32 to cpu_family x86_64 for meson David Michael
2021-06-09 12:45 ` Daniel P. Berrangé [this message]
2021-06-09 13:00 ` David Michael
2021-06-09 13:30 ` Peter Maydell
2021-06-09 13:48 ` Daniel P. Berrangé
2021-06-11 17:09 ` Paolo Bonzini
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=YMC38baIdFTL/q+f@redhat.com \
--to=berrange@redhat.com \
--cc=fedora.dm0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).