From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>,
Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PATCH 0/7] target-m68k: implement 680x0 FPU
Date: Wed, 18 Jan 2017 22:05:14 +0100 [thread overview]
Message-ID: <1484773521-16530-1-git-send-email-laurent@vivier.eu> (raw)
This series modifies the original ColdFire FPU implementation
to use floatx80 instead of float64 internally as this
is the native datatype for 680x0. I didn't keep the float64
type for ColdFire, but if someone thinks it's required I
can update this series in this way.
The series also adds the FPU status and control registers and
several floating point instructions.
The floatx80 datatype used here is not exactly the same as the
one used by 680x0 for its extended precision data type, because
normally the signaling bit of 680x0 NAN is the MSB of the mantissa
minus one and in floatx80 it is the MSB.
We also add the gdb server parts to read the new FPU registers.
A strange thing happens here: while the gdb client running remotely
from a debian etch-m68k has no issue working with 96bit FPU registers
(the 680x0 extended precision data type), new gdbs (from a debian unstable
and gdb for cross-compiled environment) don't expect this FPU registers
size. But it seems like a bug in gdb, not in this implementation.
After this series is applied, qemu-m68k can run a debian etch-m68k
or a debian unstable chroot.
Laurent Vivier (7):
target-m68k: move FPU helpers to fpu_helper.c
target-m68k: define ext_opsize
softfloat: define 680x0 specific values
target-m68k: use floatx80 internally
target-m68k: add fmovem
target-m68k: introduce fscc.
target-m68k: implements more FPU instructions
configure | 2 +-
fpu/softfloat-specialize.h | 30 +-
gdb-xml/m68k-fp.xml | 21 +
target/m68k/Makefile.objs | 2 +-
target/m68k/cpu.c | 13 +-
target/m68k/cpu.h | 75 ++-
target/m68k/fpu_helper.c | 765 +++++++++++++++++++++++++++
target/m68k/helper.c | 165 +++---
target/m68k/helper.h | 57 +-
target/m68k/qregs.def | 4 +-
target/m68k/translate.c | 1244 ++++++++++++++++++++++++++++++++------------
11 files changed, 1930 insertions(+), 448 deletions(-)
create mode 100644 gdb-xml/m68k-fp.xml
create mode 100644 target/m68k/fpu_helper.c
--
2.7.4
next reply other threads:[~2017-01-18 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 21:05 Laurent Vivier [this message]
2017-01-18 21:05 ` [Qemu-devel] [PATCH 1/7] target-m68k: move FPU helpers to fpu_helper.c Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 2/7] target-m68k: define ext_opsize Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 3/7] softfloat: define 680x0 specific values Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 4/7] target-m68k: use floatx80 internally Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 5/7] target-m68k: add fmovem Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 6/7] target-m68k: introduce fscc Laurent Vivier
2017-01-18 21:05 ` [Qemu-devel] [PATCH 7/7] target-m68k: implements more FPU instructions Laurent Vivier
2017-01-18 21:21 ` [Qemu-devel] [PATCH 0/7] target-m68k: implement 680x0 FPU no-reply
2017-01-18 21:42 ` Richard Henderson
2017-01-19 11:27 ` Laurent Vivier
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=1484773521-16530-1-git-send-email-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).