From: jiawei <jiawei@iscas.ac.cn>
To: gcc-patches@gcc.gnu.org
Cc: palmer@dabbelt.com, jim.wilson.gcc@gmail.com,
kito.cheng@sifive.com, jeremy.bennett@embecosm.com,
tariqandlaura@gmail.com, wuwei2016@iscas.ac.cn,
Jia-Wei Chen <jiawei@iscas.ac.cn>
Subject: [PATCH v3 0/3] RISC-V: Support z[f/d]inx extension
Date: Mon, 23 May 2022 18:04:20 +0800 [thread overview]
Message-ID: <20220523100423.2207532-1-jiawei@iscas.ac.cn> (raw)
From: Jia-Wei Chen <jiawei@iscas.ac.cn>
Zfinx extension[1] had already finished public review. Here is the
implementation patch set that reuse floating point pattern and ban
the use of fpr when use zfinx as a target.
Current works can be find in follow links, will keep update zhinx
and zhinxmin soon after zfh/zfhmin implemented in gcc.
https://github.com/pz9115/riscv-gcc/tree/zfinx-rebase
https://github.com/pz9115/riscv-binutils-gdb/tree/zfinx-rebase
For test you can use qemu or spike that support zfinx extension, the
qemu will go upstream soon and spike is still in review:
https://github.com/plctlab/plct-qemu/tree/plct-zfinx-dev
https://github.com/plctlab/plct-spike/tree/plct-upstream-zfinx
Thanks for Tariq Kurd, Kito Cheng, Jim Willson,
Jeremy Bennett helped us a lot with this work.
[1] https://github.com/riscv/riscv-zfinx/blob/main/zfinx-1.0.0-rc.pdf
Version log:
v2: As Kito Cheng's comment, add Changelog part in patches, update imply
info in riscv-common.c, remove useless check and update annotation in
riscv.c.
v3: Update with new isa-spec version 20191213, make zfinx imply zicsr as
default, fix the lack of fcsr use in zfinx.
jiawei (3):
RISC-V: Minimal support of zfinx extension.
RISC-V: Target support for zfinx extension.
RISC-V: Limit regs use for zfinx extension.
gcc/common/config/riscv/riscv-common.cc | 9 ++++
gcc/config/riscv/arch-canonicalize | 3 ++
gcc/config/riscv/constraints.md | 4 +-
gcc/config/riscv/riscv-builtins.cc | 4 +-
gcc/config/riscv/riscv-c.cc | 2 +-
gcc/config/riscv/riscv-opts.h | 6 +++
gcc/config/riscv/riscv.cc | 14 ++++-
gcc/config/riscv/riscv.md | 72 ++++++++++++-------------
gcc/config/riscv/riscv.opt | 3 ++
9 files changed, 75 insertions(+), 42 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-23 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 10:04 jiawei [this message]
2022-05-23 10:04 ` [PATCH v3 1/3] RISC-V: Minimal support of " jiawei
2022-05-23 10:04 ` [PATCH v3 2/3] RISC-V: Target support for " jiawei
2022-05-23 10:04 ` [PATCH v3 3/3] RISC-V: Limit regs use " jiawei
-- strict thread matches above, loose matches on Subject: below --
2022-05-23 10:02 [PATCH v3 0/3] RISC-V: Support " jiawei
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=20220523100423.2207532-1-jiawei@iscas.ac.cn \
--to=jiawei@iscas.ac.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeremy.bennett@embecosm.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=tariqandlaura@gmail.com \
--cc=wuwei2016@iscas.ac.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).