From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fh9VI-0003tt-H0 for qemu-devel@nongnu.org; Fri, 19 May 2006 14:15:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fh9VH-0003tQ-Gf for qemu-devel@nongnu.org; Fri, 19 May 2006 14:15:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fh9VH-0003tN-Bg for qemu-devel@nongnu.org; Fri, 19 May 2006 14:15:11 -0400 Received: from [212.8.0.13] (helo=rosi.naasa.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fh9Ye-0000J3-0o for qemu-devel@nongnu.org; Fri, 19 May 2006 14:18:40 -0400 From: Joerg Platte Subject: Re: [Qemu-devel] fpu problems with qemu-system-sparc Date: Fri, 19 May 2006 20:14:59 +0200 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Disposition: inline Message-Id: <200605192015.00235.lists@naasa.net> Content-Transfer-Encoding: quoted-printable Reply-To: jplatte@naasa.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, Blue Swirl Am Donnerstag, 18. Mai 2006 19:53 schrieb Blue Swirl: > >I've checked a lot of the executed instructions in qemu and cannot fin= d > > 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=20 debbugging output. The crash is more or less reproducible and the program= =20 crashes after 2-3 FPU disabled traps somewhere inside the libc init routi= nes.=20 The FPU instructions cannot be the problem, because I disabled the trap i= n=20 qemu and nothing crashed. Bit the trap is implemented like any other trap= and=20 all other traps seem to work. Since the crash is only reproducible in, le= ts=20 say 95% of all tests, it looks like a timing problem. Unfortunately, I ha= ve=20 no idea about qemu's timer simulation. What else can I check? regards, J=F6rg