qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6106] Implement default-NaN mode.
Date: Fri, 19 Dec 2008 15:11:07 +0100	[thread overview]
Message-ID: <761ea48b0812190611g1e3fe5c0ndf6fa23138cf7caf@mail.gmail.com> (raw)
In-Reply-To: <E1LDfnO-0005EK-1k@cvs.savannah.gnu.org>

On Fri, Dec 19, 2008 at 2:53 PM, Paul Brook <paul@nowt.org> wrote:
> Revision: 6106
>          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6106
> Author:   pbrook
> Date:     2008-12-19 13:53:37 +0000 (Fri, 19 Dec 2008)
>
> Log Message:
> -----------
> Implement default-NaN mode.
>
> Signed-off-by: Paul Brook <paul@codesourcery.com>
>
> Modified Paths:
> --------------
>    trunk/fpu/softfloat-specialize.h
>    trunk/fpu/softfloat.h
>    trunk/target-arm/helper.c
[...]
> Modified: trunk/target-arm/helper.c
> ===================================================================
> --- trunk/target-arm/helper.c   2008-12-19 13:37:53 UTC (rev 6105)
> +++ trunk/target-arm/helper.c   2008-12-19 13:53:37 UTC (rev 6106)
> @@ -2334,6 +2334,8 @@
>         }
>         set_float_rounding_mode(i, &env->vfp.fp_status);
>     }
> +    if (changed & (1 << 25))
> +        set_default_nan_mode((val & (1 << 25)) != 0, &env->vfp.fp_status);
>
>     i = vfp_exceptbits_to_host((val >> 8) & 0x1f);
>     set_float_exception_flags(i, &env->vfp.fp_status);

Doesn't this require an update to the way flags are computed in
target-arm/cpu.h/cpu_get_tb_cpu_state?

Also I guess the comment at end of vfp_set_fpscr needs some
update to reflect the handling of DN :-)


Laurent

  reply	other threads:[~2008-12-19 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 13:53 [Qemu-devel] [6106] Implement default-NaN mode Paul Brook
2008-12-19 14:11 ` Laurent Desnogues [this message]
2008-12-19 14:25   ` Paul Brook

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=761ea48b0812190611g1e3fe5c0ndf6fa23138cf7caf@mail.gmail.com \
    --to=laurent.desnogues@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).