qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Julian Brown <julian@codesourcery.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Correct value of ARM Cortex-A8 MVFR1 register.
Date: Tue, 13 Dec 2016 12:35:19 +0000	[thread overview]
Message-ID: <CAFEAcA9DFG3NqTAtAXd3W7y70Mdn9jH5Y9yXFdtgbRKa7p_qow@mail.gmail.com> (raw)
In-Reply-To: <1481130858-31767-1-git-send-email-julian@codesourcery.com>

On 7 December 2016 at 17:14, Julian Brown <julian@codesourcery.com> wrote:
> The value of the MVFR1 (Media and VFP Feature Register 1) register for
> the Cortex-A8 appears to be incorrect (according to the TRM, DDI0344K),
> with the "full denormal arithmetic" and "propagation of NaN" fields
> holding both 0 instead of both 1.
>
> I had a go tracing the history of the use of this value, and it seems
> it's always just been wrong in QEMU: maybe it was derived from early
> documentation, or guessed based on the use of a "VFP Lite" implementation
> in the Cortex-A8.
>
> Depending on the startup/early-boot code in use, this can manifest as
> failure to perform denormal arithmetic properly: in our case, selecting
> a Cortex-A8 CPU when using QEMU as an instruction-set simulator for
> bare-metal GCC testing caused tests using denormal arithmetic to
> fail. Problems might be masked (or not occur) when using a full OS kernel
> with suitable trap handlers (I'm not sure).
>
> Signed-off-by: Julian Brown <julian@codesourcery.com>

Applied to target-arm.next for 2.9, thanks.

-- PMM

      reply	other threads:[~2016-12-13 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 17:14 [Qemu-devel] [PATCH] Correct value of ARM Cortex-A8 MVFR1 register Julian Brown
2016-12-13 12:35 ` Peter Maydell [this message]

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=CAFEAcA9DFG3NqTAtAXd3W7y70Mdn9jH5Y9yXFdtgbRKa7p_qow@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=julian@codesourcery.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).