qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tcg problem running SPARC program on x86
Date: Tue, 19 Aug 2008 19:37:07 +0300	[thread overview]
Message-ID: <f43fc5580808190937v5f6eea90sff6167061dbd4db3@mail.gmail.com> (raw)
In-Reply-To: <20080818153918.U9420@stanley.csl.cornell.edu>

On 8/18/08, Vince Weaver <vince@csl.cornell.edu> 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.

  reply	other threads:[~2008-08-19 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 19:46 [Qemu-devel] tcg problem running SPARC program on x86 Vince Weaver
2008-08-19 16:37 ` Blue Swirl [this message]
2008-08-23  6:43   ` Blue Swirl
  -- strict thread matches above, loose matches on Subject: below --
2008-10-13 20:24 rob1weld
     [not found] ` <90edad820810180440w375f4370w1b2c22115a2afad5@mail.gmail.com>
2008-10-18 12:16   ` Anton Salikhmetov
2008-10-19 16:18     ` rob1weld
2008-10-19 17:44       ` Thiemo Seufer
2008-10-24 10:33       ` Anton Salikhmetov

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=f43fc5580808190937v5f6eea90sff6167061dbd4db3@mail.gmail.com \
    --to=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).