On 5/2/26 00:20, Josh Poimboeuf wrote:
On Sun, Feb 01, 2026 at 03:27:46PM +0100, Philippe Mathieu-Daudé wrote:
@@ -221,7 +221,7 @@ static void vmmouse_data(VMMouseState *s, uint32_t *data,
uint32_t size)
static uint32_t vmmouse_ioport_read(void *opaque, uint32_t addr)
{
VMMouseState *s = opaque;
- uint32_t data[6];
+ target_ulong data[6];
Could we use uint64_t instead (also in the callees) and let
the implicit 32-bit truncation when assigning env->regs[] on
32-bit guests?
That would work, is there a reason that would be preferable?
In preparation of the long-term heterogeneous emulation project,
we figured the target_ulong should not be used by hardware models.
We are slowly clearing our code base toward this goal.
