From: Jeff Law <jeffreyalaw@gmail.com>
To: pan2.li@intel.com, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, yanzhang.wang@intel.com,
kito.cheng@gmail.com, richard.guenther@gmail.com,
richard.sandiford@arm.com
Subject: Re: [PATCH v2] DSE: Allow vector type for get_stored_val when read < store
Date: Thu, 9 Nov 2023 09:16:12 -0700 [thread overview]
Message-ID: <7b7ad19b-7212-4dca-b58d-5d77f8f10dbe@gmail.com> (raw)
In-Reply-To: <20231109060858.3067686-1-pan2.li@intel.com>
On 11/8/23 23:08, pan2.li@intel.com wrote:
> From: Pan Li <pan2.li@intel.com>
>
> Update in v2:
> * Move vector type support to get_stored_val.
>
> Original log:
>
> This patch would like to allow the vector mode in the
> get_stored_val in the DSE. It is valid for the read
> rtx if and only if the read bitsize is less than the
> stored bitsize.
>
> Given below example code with
> --param=riscv-autovec-preference=fixed-vlmax.
>
> vuint8m1_t test () {
> uint8_t arr[32] = {
> 1, 2, 7, 1, 3, 4, 5, 3, 1, 0, 1, 2, 4, 4, 9, 9,
> 1, 2, 7, 1, 3, 4, 5, 3, 1, 0, 1, 2, 4, 4, 9, 9,
> };
>
> return __riscv_vle8_v_u8m1(arr, 32);
> }
>
> Before this patch:
> test:
> lui a5,%hi(.LANCHOR0)
> addi sp,sp,-32
> addi a5,a5,%lo(.LANCHOR0)
> li a3,32
> vl2re64.v v2,0(a5)
> vsetvli zero,a3,e8,m1,ta,ma
> vs2r.v v2,0(sp) <== Unnecessary store to stack
> vle8.v v1,0(sp) <== Ditto
> vs1r.v v1,0(a0)
> addi sp,sp,32
> jr ra
>
> After this patch:
> test:
> lui a5,%hi(.LANCHOR0)
> addi a5,a5,%lo(.LANCHOR0)
> li a4,32
> addi sp,sp,-32
> vsetvli zero,a4,e8,m1,ta,ma
> vle8.v v1,0(a5)
> vs1r.v v1,0(a0)
> addi sp,sp,32
> jr ra
>
> Below tests are passed within this patch:
>
> * The x86 bootstrap and regression test.
> * The aarch64 regression test.
> * The risc-v regression test.
>
> PR target/111720
>
> gcc/ChangeLog:
>
> * dse.cc (get_stored_val): Allow vector mode if the read
> bitsize is less than stored bitsize.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/pr111720-0.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-1.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-10.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-2.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-3.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-4.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-5.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-6.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-7.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-8.c: New test.
> * gcc.target/riscv/rvv/base/pr111720-9.c: New test.
We're always getting the lowpart here AFAICT and it appears that all the
right thing should happen if gen_lowpart_common fails (it returns NULL,
which bubbles up and is the right return value from get_stored_val if it
can't be optimized).
Did you want to use known_le so that you'd pick up the case when the two
modes are the same size? Or was known_lt the test you really wanted
(and if so, why).
OK using known_lt, or known_le. If you decide to change to known_le,
you'll need to bootstrap & regression test again on x86.
jeff
next prev parent reply other threads:[~2023-11-09 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 3:14 [PATCH v1] EXPMED: Allow vector mode for DSE extract_low_bits [PR111720] pan2.li
2023-11-02 8:19 ` Richard Biener
2023-11-02 12:17 ` Li, Pan2
2023-11-09 6:08 ` [PATCH v2] DSE: Allow vector type for get_stored_val when read < store pan2.li
2023-11-09 16:16 ` Jeff Law [this message]
2023-11-11 15:23 ` Richard Sandiford
2023-11-12 2:30 ` Li, Pan2
2023-11-13 3:25 ` Li, Pan2
2023-11-12 12:27 ` [PATCH v3] " pan2.li
2023-11-13 3:22 ` [PATCH v4] " pan2.li
2023-11-13 20:11 ` Jeff Law
2023-11-15 0:18 ` Li, Pan2
2023-11-15 0:24 ` Li, Pan2
2023-11-22 2:30 ` Li, Pan2
2023-11-22 8:02 ` Richard Biener
2023-11-22 11:38 ` Li, Pan2
2023-11-22 18:39 ` Richard Sandiford
2023-11-23 1:20 ` Li, Pan2
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=7b7ad19b-7212-4dca-b58d-5d77f8f10dbe@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.com \
--cc=yanzhang.wang@intel.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).