From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 0/3] OpenRISC floating point support + fixes
Date: Thu, 11 Apr 2019 06:27:44 +0900 [thread overview]
Message-ID: <20190410212747.18377-1-shorne@gmail.com> (raw)
Hello,
This is a set of patches to bring FPU support to the OpenRISC backend. The
backend also add support for 64-bit floating point operations on 32-bit cores
using register pairs, see orfpx64a32 [0].
This depends on binutils patches which have also been submitted per review. [1]
The toolchain has been tested using the gcc and binutils testsuites as well as
floating point test suites running on sim and an fpga soft core or1k_marocchino.
[2]
There is also an unrelated, but trivial patch to fix a code quality issue with
volatile memory loads.
This whole patch series can be found on my github repo [3] as well.
-Stafford
[0] https://openrisc.io/proposals/orfpx64a32
[1] git at github.com:stffrdhrn/binutils-gdb.git orfpx64a32-2
[2] https://github.com/openrisc/or1k_marocchino
[3] git at github.com:stffrdhrn/gcc.git or1k-fpu-1a
Stafford Horne (3):
or1k: Initial support for FPU
or1k: Allow volatile memory for sign/zero extend loads
or1k: only force reg for immediates
gcc/config.gcc | 1 +
gcc/config/or1k/or1k.c | 10 ++--
gcc/config/or1k/or1k.md | 109 ++++++++++++++++++++++++++++++++--
gcc/config/or1k/or1k.opt | 15 ++++-
gcc/config/or1k/predicates.md | 16 +++++
gcc/doc/invoke.texi | 15 +++++
6 files changed, 156 insertions(+), 10 deletions(-)
--
2.19.1
next reply other threads:[~2019-04-10 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 21:27 Stafford Horne [this message]
2019-04-10 21:27 ` [OpenRISC] [PATCH 1/3] or1k: Initial support for FPU Stafford Horne
2019-04-10 21:27 ` [OpenRISC] [PATCH 2/3] or1k: Allow volatile memory for sign/zero extend loads Stafford Horne
2019-04-10 21:27 ` [OpenRISC] [PATCH 3/3] or1k: only force reg for immediates Stafford Horne
2019-04-12 15:28 ` [OpenRISC] [PATCH 0/3] OpenRISC floating point support + fixes Jeff Law
2019-04-12 20:05 ` Stafford Horne
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=20190410212747.18377-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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