From: "Anton Salikhmetov" <salikhmetov@gmail.com>
To: qemu-devel@nongnu.org
Cc: rob1weld@aol.com
Subject: Re: [Qemu-devel] tcg problem running SPARC program on x86
Date: Sat, 18 Oct 2008 18:16:00 +0600 [thread overview]
Message-ID: <4df4ef0c0810180516u2a1e2eccr2de61663b460edb2@mail.gmail.com> (raw)
In-Reply-To: <90edad820810180440w375f4370w1b2c22115a2afad5@mail.gmail.com>
> From: <rob1weld@aol.com>
> Date: 2008/10/13
> Subject: Re: [Qemu-devel] tcg problem running SPARC program on x86
> To: qemu-devel@nongnu.org
>
>
> When I run the current trunk (revision 5478) with
> "/usr/local/bin/qemu-system-mips -cpu 24Kc -M malta ..." I get a
> similar error (calls tcg_abort() ) to the one described by Vince:
>
>
> /build/qemu/trunk/tcg/tcg.c:1484: tcg fatal error
> Aborted
>
>
> If I use exactly the same command but use the "Lenny Debian
> GNU/Linux's repository version" of qemu-system-mips (version 0.9.1-6)
> the error does not occur. Thus, this error is occurring on the MIPS
> platform (host x86) as well as the SPARC.
>
> Rob
I'm having the same error when using qemu-system-mips (-M malta). By
bisection, the revisions 5252 and 5253 were found (5252 is working
fine, while 5253 is not). All the revisions after 5253 have the same
problem with "tcg fatal error" for me. By the way, the only file
target-mips/translate.c is changing while updating the source code
from 5252 to 5253. Hope it helps to close the bug.
Anton
>
> On 8/19/08, Blue Swirl <blauwirbel@xxxxxxxxx> wrote:
>>
>> On 8/18/08, Vince Weaver <vince@xxxxxxxxxxxxxxx> wrote:
>> > Hello
>> >
>> > I'm continuing on my quest to get the SPEC2000 benchmarks running
>
> under
>>
>> > sparc32-linux-user (so far 8 out of 48 work).
>> >
>> > Many of the benchmarks die early on with the following error:
>> >
>> > /fusion/research4/vince/qemu/svn/tcg/tcg.c:1455: tcg fatal
>
> error
>>
>> >
>> > This error is caused when tcg_reg_alloc_mov() is called but
>
> ts->val_type
>>
>> > is equal to 0 (which is TEMP_VAL_DEAD). So maybe the optimizer is
>> > optimizing away something that it shouldn't?
>> >
>> > This happens in a block with multiple calls to the SPARC "mulscc"
>> > instruction which is a complicated instruction, so maybe this is
>
> finding an
>>
>> > obscure corner case.
>> >
>> > I've attached a very small sample program that exhibits the bug
>
> when run
>>
>> > with ./sparc32-linux-user/qemu-sparc32plus
>>
>>
>> Okay, I can finally reproduce this. Strangely it does not occur if -d
>> flag is used and "op" is one of the log items. I have to check if
>> older reports where I could not reproduce the bug were suffering from
>> the same problem.
>>
>> But I haven't found any fix yet.
>
> I have isolated the problem to andi op. The attached patch makes the
> bug go away by disabling the offending andi, but it's of course not a
> real fix. Why andi fails with op flag enabled, I have no idea.
>
next prev parent reply other threads:[~2008-10-18 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 20:24 [Qemu-devel] tcg problem running SPARC program on x86 rob1weld
[not found] ` <90edad820810180440w375f4370w1b2c22115a2afad5@mail.gmail.com>
2008-10-18 12:16 ` Anton Salikhmetov [this message]
2008-10-19 16:18 ` rob1weld
2008-10-19 17:44 ` Thiemo Seufer
2008-10-24 10:33 ` Anton Salikhmetov
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 19:46 Vince Weaver
2008-08-19 16:37 ` Blue Swirl
2008-08-23 6:43 ` Blue Swirl
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=4df4ef0c0810180516u2a1e2eccr2de61663b460edb2@mail.gmail.com \
--to=salikhmetov@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rob1weld@aol.com \
/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).