From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Qemu Development <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Qemu ARM tcg problem
Date: Fri, 25 Sep 2009 16:50:30 +0200 [thread overview]
Message-ID: <761ea48b0909250750l3616981av91902de913512050@mail.gmail.com> (raw)
In-Reply-To: <4ABCD30F.5090402@mlbassoc.com>
On Fri, Sep 25, 2009 at 4:26 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> Laurent,
>
> If I build with --enable-debug, I get an assertion on this line
> tcg/tcg.c: 983 assert(oarg < def->nb_oargs);
>
> This happens because of this definition
> tcg/arm/tcg-target.c: 1593 { INDEX_op_div2_i32, { "r", "r", "r", "1",
> "2" } },
>
> I'm not sure I totally understand these tables, but the assertion
> says that they may not be correct.
>
> Any clues??
This is buggy for sure. Anyway given the associated generated
code also is buggy, my only advice for your needs is to remove
op_div2 and op_divu2 from arm_op_defs. For you that'll be OK
since the i386 front-end doesn't generated these ops.
For the real fix, we'll see if anyone ever really needs it :-)
Laurent
prev parent reply other threads:[~2009-09-25 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 14:26 [Qemu-devel] Qemu ARM tcg problem Gary Thomas
2009-09-25 14:50 ` Laurent Desnogues [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=761ea48b0909250750l3616981av91902de913512050@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=gary@mlbassoc.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).