All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu fpu/softfloat-specialize.h fpu/softfloat.c...
Date: Wed, 21 Nov 2007 11:40:13 +0100	[thread overview]
Message-ID: <47440B0D.1050601@aurel32.net> (raw)
In-Reply-To: <4743F1AA.2020904@aurel32.net>

Aurelien Jarno a écrit :
> Blue Swirl a écrit :
>> On 11/18/07, Paul Brook <paul@nowt.org> wrote:
>>> CVSROOT:        /sources/qemu
>>> Module name:    qemu
>>> Changes by:     Paul Brook <pbrook>     07/11/18 14:33:24
>>>
>>> Modified files:
>>>         fpu            : softfloat-specialize.h softfloat.c softfloat.h
>>>         target-arm/nwfpe: double_cpdo.c single_cpdo.c
>>>         target-m68k    : helper.c op.c
>>>         target-mips    : op_helper.c
>>>
>>> Log message:
>>>         Add strict checking mode for softfp code.
>> This commit has broken sparc-softmmu, for example Aurora 1.0 normally prints:
>> Running anaconda - please wait...
> 
> There are also FPU regressions for mips-softmmu, but I haven't found
> time to find the commit that has broken it, I just know it has been
> broken over the week-end.
> 
> More later...

I am now able to confirm this very same commit has also broken the FPU
on mips-softmmu, but I still don't know what is wrong in this commit.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

  reply	other threads:[~2007-11-21 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 14:33 [Qemu-devel] qemu fpu/softfloat-specialize.h fpu/softfloat.c Paul Brook
2007-11-20 20:17 ` Blue Swirl
2007-11-20 20:42   ` Paul Brook
2007-11-21  8:51   ` Aurelien Jarno
2007-11-21 10:40     ` Aurelien Jarno [this message]
2007-11-21 15:10       ` Aurelien Jarno
2007-11-21 15:32         ` Paul Brook
2007-11-21 15:55           ` Eduardo Felipe
2007-11-21 18:58             ` Blue Swirl
2007-11-22  0:48           ` Thiemo Seufer

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=47440B0D.1050601@aurel32.net \
    --to=aurelien@aurel32.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.