All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH RFC] meson: require int128 type
Date: Thu, 8 May 2025 10:43:25 -0400	[thread overview]
Message-ID: <20250508104300-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA-ideWjVhKjK6xTcSFoKPY3C_9BJ0jp-UE-7qCkGGt8FQ@mail.gmail.com>

On Thu, May 08, 2025 at 01:30:25PM +0100, Peter Maydell wrote:
> On Thu, 8 May 2025 at 13:21, Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > compilers that QEMU requires support int128
> > (though arithmetic might be more challenging).
> > As virtio wants to use int128 with bitwise opts only,
> > make it simple by failing configure if not there.
> 
> IIRC the problem is not the compiler version but whether
> or not it's targeting a 32-bit host: compilers will
> implement an int128 based on 2 64-bit registers, but
> not one based on 4 32-bit registers. Did you check this
> on all our supported host platforms ?
> 
> (We've deprecated 32-bit host support, but not dropped
> it yet, I think.)
> 
> thanks
> -- PMM

Thanks for the feedback, indeed I did not. Will check some
config.



      reply	other threads:[~2025-05-08 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 12:20 [PATCH RFC] meson: require int128 type Michael S. Tsirkin
2025-05-08 12:30 ` Peter Maydell
2025-05-08 14:43   ` Michael S. Tsirkin [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=20250508104300-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --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.