From: Xi Ruoyao <xry111@xry111.site>
To: Liwei Xu <liwei.xu@intel.com>, gcc-patches@gcc.gnu.org
Cc: wilson@tuliptree.org, admin@levyhsu.com,
Lulu Cheng <chenglulu@loongson.cn>
Subject: Re: [PATCH] Optimize nested permutation to single VEC_PERM_EXPR [PR54346]
Date: Wed, 12 Oct 2022 21:51:47 +0800 [thread overview]
Message-ID: <b5c5991daf6571cc78da23b6a6b6735071cb6d24.camel@xry111.site> (raw)
In-Reply-To: <20220926065604.783193-1-liwei.xu@intel.com>
On Mon, 2022-09-26 at 14:56 +0800, Liwei Xu via Gcc-patches wrote:
> 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.
I'm getting:
FAIL: gcc.dg/pr54346.c scan-tree-dump dse1 "VEC_PERM_EXPR.*{ 3, 6, 0, 0 }"
FAIL: gcc.dg/pr54346.c scan-tree-dump-times dse1 "VEC_PERM_EXPR" 1
on loongarch64-linux-gnu. Not sure why.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-10-12 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 6:56 Liwei Xu
2022-09-26 8:21 ` Richard Biener
2022-09-30 9:17 ` Richard Sandiford
2022-09-30 9:36 ` Xu, Liwei
2022-10-12 13:51 ` Xi Ruoyao [this message]
2022-10-13 6:15 ` Levy
2022-10-13 6:44 ` Xi Ruoyao
2022-10-13 8:15 ` Lulu Cheng
2022-10-13 11:10 ` Richard Biener
2022-10-14 1:09 ` Xu, Liwei
2022-10-14 1:49 ` Lulu Cheng
2022-10-14 6:18 ` Richard Biener
2022-10-14 6:34 ` Xu, Liwei
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=b5c5991daf6571cc78da23b6a6b6735071cb6d24.camel@xry111.site \
--to=xry111@xry111.site \
--cc=admin@levyhsu.com \
--cc=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=liwei.xu@intel.com \
--cc=wilson@tuliptree.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: 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).