qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <christophe.lyon@st.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/2] ARM: fix Neon vrecpe instruction.
Date: Wed, 16 Feb 2011 15:51:21 +0100	[thread overview]
Message-ID: <1297867883-18390-1-git-send-email-christophe.lyon@st.com> (raw)

From: Christophe Lyon <christophe.lyon@st.com>

These 2 patches fix the ARM Neon vrecpe instruction by matching the
algorithm descibed in the ARM ARM.

With these patches, qemu passes my ARM/Neon tests.

Patch #1 modifies softfloat by exporting float32_nan and
float32_infinity. For consistency, I have also moved all the
target-dependent definitions of floatXX_default_nan to softfloat.h (ie
the 16, 64, x80 and 128 bits versions in addition to the 32 bits
ones).

Patch #2 uses these newly exported values and uses the vrecpe
algorithm described in the ARM ARM.

Christophe Lyon (2):
  softfloat: export float32_nan and float32_infinity.
  target-arm: fix support for vrecpe.

 fpu/softfloat-specialize.h |   68 -----------------------------------
 fpu/softfloat.h            |   71 +++++++++++++++++++++++++++++++++++++
 target-arm/helper.c        |   84 +++++++++++++++++++++++++++++++++++++------
 3 files changed, 143 insertions(+), 80 deletions(-)

-- 
1.7.2.3

             reply	other threads:[~2011-02-16 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 14:51 christophe.lyon [this message]
2011-02-16 14:51 ` [Qemu-devel] [PATCH 1/2] softfloat: export float32_nan and float32_infinity christophe.lyon
2011-02-16 16:54   ` Peter Maydell
2011-02-16 16:58     ` Christophe Lyon
2011-02-16 14:51 ` [Qemu-devel] [PATCH 2/2] target-arm: fix support for vrecpe christophe.lyon
2011-02-16 16:47   ` Peter Maydell

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=1297867883-18390-1-git-send-email-christophe.lyon@st.com \
    --to=christophe.lyon@st.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).