From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
"Matheus K. Ferst" <matheus.ferst@eldorado.org.br>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Greg Kurz" <groug@kaod.org>, qemu-ppc <qemu-ppc@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH for-6.2 v2 2/2] target/ppc: fix vector registers access in gdbstub for little-endian
Date: Thu, 19 Aug 2021 13:03:48 -1000 [thread overview]
Message-ID: <270f1d40-f377-1f89-4a93-fb5774edb967@linaro.org> (raw)
In-Reply-To: <CAFEAcA89aPw5chrrzaV155Why0vjhN+BUQ7nfhz1_4EgcziBZw@mail.gmail.com>
On 8/19/21 2:42 AM, Peter Maydell wrote:
> Maybe we should fix this by making the 'struct Int128' field order
> depend on HOST_WORDS_BIGENDIAN...
Yes, I think so.
At some point I had a notion of supporting Int128 natively in TCG, at least as far as data
movement and the host function call abi.
r~
next prev parent reply other threads:[~2021-08-19 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 11:06 [PATCH for-6.2 v2 0/2] target/ppc: Fix vector registers access in gdbstub for little-endian matheus.ferst
2021-08-18 11:06 ` [PATCH for-6.2 v2 1/2] include/qemu/int128.h: introduce bswap128s matheus.ferst
2021-08-18 12:23 ` Philippe Mathieu-Daudé
2021-08-19 12:33 ` Peter Maydell
2021-08-18 11:06 ` [PATCH for-6.2 v2 2/2] target/ppc: fix vector registers access in gdbstub for little-endian matheus.ferst
2021-08-19 12:42 ` Peter Maydell
2021-08-19 12:47 ` Luis Fernando Fujita Pires
2021-08-19 19:39 ` Matheus K. Ferst
2021-08-19 23:03 ` Richard Henderson [this message]
2021-08-19 12:57 ` Peter Maydell
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=270f1d40-f377-1f89-4a93-fb5774edb967@linaro.org \
--to=richard.henderson@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=matheus.ferst@eldorado.org.br \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.