All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Platte <lists@naasa.net>
To: qemu-devel@nongnu.org, Blue Swirl <blueswir1@hotmail.com>
Subject: Re: [Qemu-devel] fpu problems with qemu-system-sparc
Date: Fri, 19 May 2006 20:14:59 +0200	[thread overview]
Message-ID: <200605192015.00235.lists@naasa.net> (raw)
In-Reply-To: <BAY104-F409C661F7860D1EEB46B56FFA60@phx.gbl>

Am Donnerstag, 18. Mai 2006 19:53 schrieb Blue Swirl:
> >I've checked a lot of the executed instructions in qemu and cannot find
> > any problems up to now. Does somebody else has an idea what to check? The
> > test program simply adds two float variables (fadds-instruction) in a
> > loop and this crashes the program reproducible.
>
> Some instructions trap when FPU is disabled, and they shouldn't, like
> stfsr?

I've checked and changed a lot of code inside the kernel and in qemu and added 
debbugging output. The crash is more or less reproducible and the program 
crashes after 2-3 FPU disabled traps somewhere inside the libc init routines. 
The FPU instructions cannot be the problem, because I disabled the trap in 
qemu and nothing crashed. Bit the trap is implemented like any other trap and 
all other traps seem to work. Since the crash is only reproducible in, lets 
say 95% of all tests, it looks like a timing problem. Unfortunately, I have 
no idea about qemu's timer simulation. What else can I check?

regards,
Jörg

  parent reply	other threads:[~2006-05-19 18:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 16:16 [Qemu-devel] fpu problems with qemu-system-sparc Joerg Platte
2006-05-18 17:53 ` Blue Swirl
2006-05-18 19:50   ` Joerg Platte
2006-05-19 18:14   ` Joerg Platte [this message]
2006-05-19 19:14     ` Blue Swirl
2006-05-19 19:38       ` Joerg Platte
2006-05-22 17:51       ` Joerg Platte
2006-05-22 19:12         ` Joerg Platte
2006-05-22 19:31           ` Joerg Platte
2006-05-23  6:26 ` Joerg Platte

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=200605192015.00235.lists@naasa.net \
    --to=lists@naasa.net \
    --cc=blueswir1@hotmail.com \
    --cc=jplatte@naasa.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.