From: Jeff Law <jeffreyalaw@gmail.com>
To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com
Subject: Re: [PATCH] RISC-V: Add duplicate vector support.
Date: Mon, 28 Nov 2022 09:49:27 -0700 [thread overview]
Message-ID: <4e4383b5-a7a0-315b-568d-4931313eaaef@gmail.com> (raw)
In-Reply-To: <20221125160639.43024-1-juzhe.zhong@rivai.ai>
On 11/25/22 09:06, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/constraints.md (Wdm): New constraint.
> * config/riscv/predicates.md (direct_broadcast_operand): New predicate.
> * config/riscv/riscv-protos.h (RVV_VLMAX): New macro.
> (emit_pred_op): Refine function.
> * config/riscv/riscv-selftests.cc (run_const_vector_selftests): New function.
> (run_broadcast_selftests): Ditto.
> (BROADCAST_TEST): New tests.
> (riscv_run_selftests): More tests.
> * config/riscv/riscv-v.cc (emit_pred_move): Refine function.
> (emit_vlmax_vsetvl): Ditto.
> (emit_pred_op): Ditto.
> (expand_const_vector): New function.
> (legitimize_move): Add constant vector support.
> * config/riscv/riscv.cc (riscv_print_operand): New asm print rule for const vector.
> * config/riscv/riscv.h (X0_REGNUM): New macro.
> * config/riscv/vector-iterators.md: New attribute.
> * config/riscv/vector.md (vec_duplicate<mode>): New pattern.
> (@pred_broadcast<mode>): New pattern.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/dup-1.c: New test.
> * gcc.target/riscv/rvv/base/dup-2.c: New test.
I think this should wait for the next stage1 cycle.
jeff
next prev parent reply other threads:[~2022-11-28 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 16:06 juzhe.zhong
2022-11-28 16:49 ` Jeff Law [this message]
2022-11-28 22:54 ` 钟居哲
2022-12-01 16:04 ` Kito Cheng
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=4e4383b5-a7a0-315b-568d-4931313eaaef@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.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).