From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Cooper Qu <cooper.qu@linux.alibaba.com>,
Lifang Xia <lifang_xia@linux.alibaba.com>,
Yunhai Shang <yunhai@linux.alibaba.com>,
Zhiwei Liu <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH 11/11] riscv: thead: Add support for the XTheadFMemIdx ISA extension
Date: Wed, 28 Jun 2023 14:39:26 +0200 [thread overview]
Message-ID: <CAEg0e7gghZcWVzh6A+SFAkRwpqK-V-0bgUQA1U3xJvS6wzNo6g@mail.gmail.com> (raw)
In-Reply-To: <c7a69048-61d2-81d8-2eb6-1051063c9420@gmail.com>
On Sat, Jun 10, 2023 at 7:54 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 4/28/23 00:23, Christoph Muellner wrote:
> > From: Christoph Müllner <christoph.muellner@vrull.eu>
> >
> > The XTheadFMemIdx ISA extension provides additional load and store
> > instructions for floating-point registers with new addressing modes.
> >
> > The following memory accesses types are supported:
> > * ftype = [w,d] (single-precision, double-precision)
> >
> > The following addressing modes are supported:
> > * register offset with additional immediate offset (4 instructions):
> > flr<type>, fsr<type>
> > * zero-extended register offset with additional immediate offset
> > (4 instructions): flur<type>, fsur<type>
> >
> > These addressing modes are also part of the similar XTheadMemIdx
> > ISA extension support, whose code is reused and extended to support
> > floating-point registers.
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv.cc (riscv_index_reg_class): Also allow
> > for XTheadFMemIdx.
> > (riscv_regno_ok_for_index_p): Likewise.
> > * config/riscv/thead-peephole.md (TARGET_64BIT):
> > Generalize peepholes for XTheadFMemIdx.
> > * config/riscv/thead.cc (is_fmemidx_mode): New function.
> > (th_memidx_classify_address_index): Add support for
> > XTheadFMemIdx.
> > (th_fmemidx_output_index): New function.
> > (th_output_move): Add support for XTheadFMemIdx.
> > * config/riscv/thead.md (*th_fmemidx_movsf_hardfloat): New INSN.
> > (*th_fmemidx_movdf_hardfloat_rv64): Likewise.
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.target/riscv/xtheadmemidx-helpers.h: Add helpers for
> > XTheadMemFIdx.
> > * gcc.target/riscv/xtheadfmemidx-index-update.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-index-xtheadbb-update.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-index-xtheadbb.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-index.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-uindex-update.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-uindex-xtheadbb-update.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-uindex-xtheadbb.c: New test.
> > * gcc.target/riscv/xtheadfmemidx-uindex.c: New test.
> Same core questions/comments as in patch #10 of this series.
The basic support for this extension is already merged.
The documentation can be found here:
https://github.com/T-head-Semi/thead-extension-spec/tree/master
The extension's name and a link to the documentation has also been
registered here:
https://github.com/riscv-non-isa/riscv-toolchain-conventions#list-of-vendor-extensions
The XTheadFMemIdx extension is part of the T-Head C906 and C910 SoCs.
The C906 was launched in October 2021.
Thanks,
Christoph
>
> jeff
>
next prev parent reply other threads:[~2023-06-28 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 6:23 [PATCH 10/11] riscv: thead: Add support for the XTheadMemIdx " Christoph Muellner
2023-04-28 6:23 ` [PATCH 11/11] riscv: thead: Add support for the XTheadFMemIdx " Christoph Muellner
2023-06-10 17:54 ` Jeff Law
2023-06-28 12:39 ` Christoph Müllner [this message]
2023-06-10 17:53 ` [PATCH 10/11] riscv: thead: Add support for the XTheadMemIdx " Jeff Law
2023-06-28 12:39 ` Christoph Müllner
2023-06-28 18:23 ` Jeff Law
2023-06-29 7:39 ` Christoph Müllner
2023-06-29 14:09 ` Jeff Law
2023-07-06 6:48 ` Christoph Müllner
2023-07-06 15:28 ` Jeff Law
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=CAEg0e7gghZcWVzh6A+SFAkRwpqK-V-0bgUQA1U3xJvS6wzNo6g@mail.gmail.com \
--to=christoph.muellner@vrull.eu \
--cc=andrew@sifive.com \
--cc=cooper.qu@linux.alibaba.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=lifang_xia@linux.alibaba.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=yunhai@linux.alibaba.com \
--cc=zhiwei_liu@linux.alibaba.com \
/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).