OpenRISC floating point support + fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | or1k: Initial support for FPUgcc/ gcc/ gcc/ +1 more | +131 | 0 replies | |
| 2/3 | or1k: Allow volatile memory for sign/zero extend loadsgcc/ gcc/ | +19 | 0 replies | |
| 3/3 | or1k: only force reg for immediatesgcc/ | +6 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [OpenRISC] [PATCH 0/3] OpenRISC floating point support + fixes
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(-)
Signature · 1 line
2.19.1