qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] FPU Accuracy  on i386
Date: Fri, 4 Apr 2008 11:51:29 -0500	[thread overview]
Message-ID: <47F65C91.1040807@oarcorp.com> (raw)

Hi,

I hope this is the right mailing list.

I am using the precompiled 0.91 image to do
automated testing of i386-rtems.  In the Ada
validation suite, 17 of the 21 failures appear
to be due to FP calculation accuracy.  Here
is a typical test output for these:

,.,. CXG2002 ACATS 2.5 88-01-01 00:00:00
---- CXG2002 Check the accuracy of the complex modulus function.
   * CXG2002 test 1 -- abs(bigreal + 0i) actual:
                +Inf******************* expected:
                1.18973149535723177E+4932 difference:
                -Inf******************* max_err:
                3.86972841582221554E+4913.
   * CXG2002 test 2 -- abs(0 + bigreal*i) actual:
                +Inf******************* expected:
                1.18973149535723177E+4932 difference:
                -Inf******************* max_err:
                3.86972841582221554E+4913.
   * CXG2002 test 8 -- abs(1 + 1*i) actual:  1.41421356237309515E+00
                expected:  1.41421356237309505E+00 difference:
                -9.67108337857069955E-17 max_err:
                4.59988025005012224E-19.
**** CXG2002 FAILED ****************************.

I am running with the "-cpu 486" option on a 32-bit
x86 host. 

Are there known issues with FPU code in qemu that
I should be aware of?

Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

                 reply	other threads:[~2008-04-04 17:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47F65C91.1040807@oarcorp.com \
    --to=joel.sherrill@oarcorp.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).