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/54346] combine permutations Date: Tue, 11 Oct 2022 06:12:30 +0000 [thread overview] Message-ID: <bug-54346-4-jkOQYM8jT2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54346-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54346 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:b88adba751da635c6f0c353c5bc51bbe2ecf4c89 commit r13-3212-gb88adba751da635c6f0c353c5bc51bbe2ecf4c89 Author: Liwei Xu <liwei.xu@intel.com> Date: Fri Sep 23 13:46:02 2022 +0800 Optimize nested permutation to single VEC_PERM_EXPR [PR54346] This patch implemented the optimization in PR 54346, which Merges c = VEC_PERM_EXPR <a, b, VCST0>; d = VEC_PERM_EXPR <c, c, VCST1>; to d = VEC_PERM_EXPR <a, b, NEW_VCST>; Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,} tree-ssa/forwprop-19.c fail to pass but I'm not sure whether it is ok to removed it. gcc/ChangeLog: PR tree-optimization/54346 * match.pd: Merge the index of VCST then generates the new vec_perm. gcc/testsuite/ChangeLog: * gcc.dg/pr54346.c: New test. Co-authored-by: liuhongt <hongtao.liu@intel.com>
next prev parent reply other threads:[~2022-10-11 6:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-21 14:02 [Bug tree-optimization/54346] New: " glisse at gcc dot gnu.org 2021-08-25 7:26 ` [Bug tree-optimization/54346] " pinskia at gcc dot gnu.org 2021-08-25 9:02 ` pinskia at gcc dot gnu.org 2022-06-07 9:10 ` crazylht at gmail dot com 2022-10-11 6:12 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-11 6:21 ` glisse at gcc dot gnu.org 2022-10-11 6:36 ` crazylht at gmail dot com 2022-10-21 7:17 ` cvs-commit at gcc dot gnu.org 2022-10-25 5:53 ` crazylht at gmail dot com
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-54346-4-jkOQYM8jT2@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).