From: Richard Biener <richard.guenther@gmail.com>
To: "Li, Pan2" <pan2.li@intel.com>
Cc: "richard.sandiford@arm.com" <richard.sandiford@arm.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>,
"kito.cheng@gmail.com" <kito.cheng@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4] DSE: Allow vector type for get_stored_val when read < store
Date: Wed, 22 Nov 2023 09:02:22 +0100 [thread overview]
Message-ID: <CAFiYyc3KBUhm=+RZW6Jv+Xk6PQFe3ssdDncZB_2OjNOsrt7-XQ@mail.gmail.com> (raw)
In-Reply-To: <MW5PR11MB5908028D64E84AB8FCE74ACAA9BAA@MW5PR11MB5908.namprd11.prod.outlook.com>
On Wed, Nov 22, 2023 at 3:30 AM Li, Pan2 <pan2.li@intel.com> wrote:
>
> Hi Richard S,
>
> Thanks a lot for reviewing and comments. May I know is there any concern or further comments for landing this patch to GCC-14?
It looks like Jeff approved the patch?
Richard.
> Pan
>
> -----Original Message-----
> From: Li, Pan2
> Sent: Wednesday, November 15, 2023 8:25 AM
> To: gcc-patches@gcc.gnu.org
> Cc: juzhe.zhong@rivai.ai; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng@gmail.com; richard.guenther@gmail.com; richard.sandiford@arm.com; Jeff Law <jeffreyalaw@gmail.com>
> Subject: RE: [PATCH v4] DSE: Allow vector type for get_stored_val when read < store
>
> Sorry for disturbing, looks I have a typo for Richard S's email address, cc the right email address for awareness.
>
> Pan
>
> -----Original Message-----
> From: Li, Pan2
> Sent: Wednesday, November 15, 2023 8:18 AM
> To: Jeff Law <jeffreyalaw@gmail.com>; gcc-patches@gcc.gnu.org
> Cc: juzhe.zhong@rivai.ai; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng@gmail.com; richard.guenther@gmail.com; richard.sandiford@arm.com2
> Subject: RE: [PATCH v4] DSE: Allow vector type for get_stored_val when read < store
>
> > I wouldn't try to handle that case unless we had actual evidence it was
> > useful to do so. Just wanted to point out that unlike pseudos we can
> > have multiple modes referencing the same memory location.
>
> Got the point here, thanks Jeff for emphasizing this, 😉.
>
> Pan
>
> -----Original Message-----
> From: Jeff Law <jeffreyalaw@gmail.com>
> Sent: Tuesday, November 14, 2023 4:12 AM
> To: Li, Pan2 <pan2.li@intel.com>; gcc-patches@gcc.gnu.org
> Cc: juzhe.zhong@rivai.ai; Wang, Yanzhang <yanzhang.wang@intel.com>; kito.cheng@gmail.com; richard.guenther@gmail.com; richard.sandiford@arm.com2
> Subject: Re: [PATCH v4] DSE: Allow vector type for get_stored_val when read < store
>
>
>
> On 11/12/23 20:22, pan2.li@intel.com wrote:
> > From: Pan Li <pan2.li@intel.com>
> >
> > Update in v4:
> > * Merge upstream and removed some independent changes.
> >
> > Update in v3:
> > * Take known_le instead of known_lt for vector size.
> > * Return NULL_RTX when gap is not equal 0 and not constant.
> >
> > 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 risc-v regression test.
> > * The x86 bootstrap and regression test.
> > * The aarch64 regression test.
> >
> > PR target/111720
> >
> > gcc/ChangeLog:
> >
> > * dse.cc (get_stored_val): Allow vector mode if read size is
> > less than or equal to stored size.
> >
> > 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.
> OK for the trunk.
>
>
> >
>
> > + else if (VECTOR_MODE_P (read_mode) && VECTOR_MODE_P (store_mode)
> > + && known_le (GET_MODE_BITSIZE (read_mode), GET_MODE_BITSIZE (store_mode))
> > + && targetm.modes_tieable_p (read_mode, store_mode))
> > + read_reg = gen_lowpart (read_mode, copy_rtx (store_info->rhs));
> > else
> > read_reg = extract_low_bits (read_mode, store_mode,
> > copy_rtx (store_info->rhs));
> It may not matter, especially for RV, but we could possibly have a
> mixture of scalar and vector modes in the RTL. Say a vector store
> followed by a scalar read or vice-versa.
>
> I wouldn't try to handle that case unless we had actual evidence it was
> useful to do so. Just wanted to point out that unlike pseudos we can
> have multiple modes referencing the same memory location.
>
> Jeff
next prev parent reply other threads:[~2023-11-22 8:06 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
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 [this message]
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='CAFiYyc3KBUhm=+RZW6Jv+Xk6PQFe3ssdDncZB_2OjNOsrt7-XQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.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).