From: Jeff Law <jeffreyalaw@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>, gcc-patches@gcc.gnu.org
Cc: Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Lehua Ding <lehua.ding@rivai.ai>,
Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Subject: Re: [PATCH] RISC-V: Fix error combine of pred_mov pattern
Date: Fri, 23 Feb 2024 00:39:00 -0700 [thread overview]
Message-ID: <cfdc3d17-59f4-450c-94d4-20557678f1ad@gmail.com> (raw)
In-Reply-To: <or4je3pxz5.fsf@lxoliva.fsfla.org>
On 2/19/24 21:21, Alexandre Oliva wrote:
> This backport is the second of two required for the pr111935 testcase,
> already backported to gcc-13, to pass on riscv64-elf and riscv32-elf.
> The V_VLS mode iterator, used in the original patch, is not available in
> gcc-13, and I thought that would be too much to backport (and maybe so
> are these two patches, WDYT?), so I changed it to V, to match the
> preexisting gcc-13 pattern. Comments also needed manual adjustment.
> Regstrapped on x86_64-linux-gnu, along with other backports, and tested
> manually on riscv64-elf. Ok to install?
>
> From: Lehua Ding <lehua.ding@rivai.ai>
>
> This patch fix PR110943 which will produce some error code. This is because
> the error combine of some pred_mov pattern. Consider this code:
>
> ```
>
> void foo9 (void *base, void *out, size_t vl)
> {
> int64_t scalar = *(int64_t*)(base + 100);
> vint64m2_t v = __riscv_vmv_v_x_i64m2 (0, 1);
> *(vint64m2_t*)out = v;
> }
> ```
>
> RTL before combine pass:
>
> ```
> (insn 11 10 12 2 (set (reg/v:RVVM2DI 134 [ v ])
> (if_then_else:RVVM2DI (unspec:RVVMF32BI [
> (const_vector:RVVMF32BI repeat [
> (const_int 1 [0x1])
> ])
> (const_int 1 [0x1])
> (const_int 2 [0x2]) repeated x2
> (const_int 0 [0])
> (reg:SI 66 vl)
> (reg:SI 67 vtype)
> ] UNSPEC_VPREDICATE)
> (const_vector:RVVM2DI repeat [
> (const_int 0 [0])
> ])
> (unspec:RVVM2DI [
> (reg:SI 0 zero)
> ] UNSPEC_VUNDEF))) "/app/example.c":6:20 1089 {pred_movrvvm2di})
> (insn 14 13 0 2 (set (mem:RVVM2DI (reg/v/f:DI 136 [ out ]) [1 MEM[(vint64m2_t *)out_4(D)]+0 S[32, 32] A128])
> (reg/v:RVVM2DI 134 [ v ])) "/app/example.c":7:23 717 {*movrvvm2di_whole})
> ```
>
> RTL after combine pass:
> ```
> (insn 14 13 0 2 (set (mem:RVVM2DI (reg:DI 138) [1 MEM[(vint64m2_t *)out_4(D)]+0 S[32, 32] A128])
> (if_then_else:RVVM2DI (unspec:RVVMF32BI [
> (const_vector:RVVMF32BI repeat [
> (const_int 1 [0x1])
> ])
> (const_int 1 [0x1])
> (const_int 2 [0x2]) repeated x2
> (const_int 0 [0])
> (reg:SI 66 vl)
> (reg:SI 67 vtype)
> ] UNSPEC_VPREDICATE)
> (const_vector:RVVM2DI repeat [
> (const_int 0 [0])
> ])
> (unspec:RVVM2DI [
> (reg:SI 0 zero)
> ] UNSPEC_VUNDEF))) "/app/example.c":7:23 1089 {pred_movrvvm2di})
> ```
>
> This combine change the semantics of insn 14. I split @pred_mov pattern and
> restrict the conditon of @pred_mov.
>
> PR target/110943
>
> gcc/ChangeLog:
>
> * config/riscv/predicates.md (vector_const_int_or_double_0_operand):
> New predicate.
> * config/riscv/riscv-vector-builtins.cc (function_expander::function_expander):
> force_reg mem target operand.
> * config/riscv/vector.md (@pred_mov<mode>): Wrapper.
> (*pred_mov<mode>): Remove imm -> reg pattern.
> (*pred_broadcast<mode>_imm): Add imm -> reg pattern.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/pr110943.c: New test.
I'd leave this alone as well. I just don't see much value in the backports.
jeff
next prev parent reply other threads:[~2024-02-23 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 4:21 Alexandre Oliva
2024-02-23 7:39 ` Jeff Law [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 3:54 Lehua Ding
2023-08-10 12:29 ` Lehua Ding
2023-08-11 15:57 ` Jeff Law
2023-08-11 16:30 ` Lehua Ding
2023-08-11 16:40 ` Lehua Ding
2023-08-28 21:34 ` Jeff Law
2023-08-18 10:30 ` Lehua Ding
2023-08-08 11:57 Lehua Ding
2023-08-08 16:10 ` 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=cfdc3d17-59f4-450c-94d4-20557678f1ad@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jim.wilson.gcc@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=lehua.ding@rivai.ai \
--cc=oliva@adacore.com \
--cc=palmer@dabbelt.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).