qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: mdroth <mdroth@linux.vnet.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] make check breakage on 32 bit hosts
Date: Sun, 26 May 2013 22:24:38 -0500	[thread overview]
Message-ID: <20130527032438.GC4599@vm> (raw)
In-Reply-To: <20130526152648.GA4599@vm>

On Sun, May 26, 2013 at 10:26:48AM -0500, mdroth wrote:
> On Sun, May 26, 2013 at 12:00:57PM +0000, Blue Swirl wrote:
> > I get this on i386 chroot for make check:
> > 
> > GTESTER tests/test-qmp-output-visitor
> > **
> > ERROR:/src/qemu/tests/test-qmp-output-visitor.c:595:check_native_list:
> > assertion failed: (tmp)
> > GTester: last random seed: R02S559792e7c8d0762d9a2ee153fba8896c
> > **
> 
> Tests case looks correct, problem seems to be that we cast list node to
> GenericList, which expects the 'value' field to be a pointer type. With
> native lists types these are in some cases non-pointer types, like
> intList, where 'value' is an int64_t. On 32-bit archs this cast leads to
> use uses incorrect offset when trying to traverse the list.
> 
> Don't see a way to fix this outside of making the code generators do
> a bit of massaging for these cases rather than a cast. Looking at it
> now, but might not be able to send a patch till later.

Patch sent:

http://article.gmane.org/gmane.comp.emulators.qemu/213202

Teaching code generators to be smarter didn't work out so well
since visitor implementations allocate storage of list types based
on GenericList, so ended up relying on padding to 64-bit instead.

      reply	other threads:[~2013-05-27  3:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-26 12:00 [Qemu-devel] make check breakage on 32 bit hosts Blue Swirl
2013-05-26 15:26 ` mdroth
2013-05-27  3:24   ` mdroth [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=20130527032438.GC4599@vm \
    --to=mdroth@linux.vnet.ibm.com \
    --cc=blauwirbel@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).