public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107412] Miss to fold LEN_{LOAD,STORE} when the specified length equal to vector length Date: Mon, 07 Nov 2022 08:17:08 +0000 [thread overview] Message-ID: <bug-107412-4-68lEM9Y6lO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107412 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:8408120fecc56385b316dafec1bdfe3aac61fc05 commit r13-3716-g8408120fecc56385b316dafec1bdfe3aac61fc05 Author: Kewen Lin <linkw@linux.ibm.com> Date: Mon Nov 7 02:07:27 2022 -0600 vect: Fold LEN_{LOAD,STORE} if it's for the whole vector [PR107412] As the test case in PR107412 shows, we can fold IFN .LEN_{LOAD, STORE} into normal vector load/store if the given length is known to be equal to the length of the whole vector. It would help to improve overall cycles as normally the latency of vector access with length in bytes is bigger than normal vector access, and it also saves the preparation for length if constant length can not be encoded into instruction (such as on power). PR tree-optimization/107412 gcc/ChangeLog: * gimple-fold.cc (gimple_fold_mask_load_store_mem_ref): Rename to ... (gimple_fold_partial_load_store_mem_ref): ... this, add one parameter mask_p indicating it's for mask or length, and add some handlings for IFN LEN_{LOAD,STORE}. (gimple_fold_mask_load): Rename to ... (gimple_fold_partial_load): ... this, add one parameter mask_p. (gimple_fold_mask_store): Rename to ... (gimple_fold_partial_store): ... this, add one parameter mask_p. (gimple_fold_call): Add the handlings for IFN LEN_{LOAD,STORE}, and adjust calls on gimple_fold_mask_load_store_mem_ref to gimple_fold_partial_load_store_mem_ref. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr107412.c: New test. * gcc.target/powerpc/p9-vec-length-epil-8.c: Adjust scan times for folded LEN_LOAD.
next prev parent reply other threads:[~2022-11-07 8:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-26 9:13 [Bug tree-optimization/107412] New: " linkw at gcc dot gnu.org 2022-10-26 9:15 ` [Bug tree-optimization/107412] " linkw at gcc dot gnu.org 2022-10-27 22:03 ` segher at gcc dot gnu.org 2022-10-31 6:39 ` linkw at gcc dot gnu.org 2022-11-07 8:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-11-07 8:25 ` linkw at gcc dot gnu.org 2022-11-07 8:25 ` linkw at gcc dot gnu.org 2022-12-05 5:28 ` cvs-commit at gcc dot gnu.org
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=bug-107412-4-68lEM9Y6lO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).