From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, Levy <admin@levyhsu.com>
Cc: Liwei Xu <liwei.xu@intel.com>,
gcc-patches@gcc.gnu.org, wilson@tuliptree.org
Subject: Re: [PATCH] Optimize nested permutation to single VEC_PERM_EXPR [PR54346]
Date: Thu, 13 Oct 2022 16:15:36 +0800 [thread overview]
Message-ID: <b1f7a658-d330-9661-376a-3927434490d9@loongson.cn> (raw)
In-Reply-To: <26e1323e4a0395fbd1bc71b8f7a3f016fa6df54b.camel@xry111.site>
在 2022/10/13 下午2:44, Xi Ruoyao 写道:
> On Thu, 2022-10-13 at 14:15 +0800, Levy wrote:
>> Hi RuoYao
>>
>> It’s probably because loongarch64 doesn’t support
>> can_vec_perm_const_p(result_mode, op_mode, sel2, false)
>>
>> I’m not sure whether if loongarch will support it or should I just
>> limit the test target for pr54346.c?
> I'm not sure if we can add TARGET_VECTORIZE_VEC_PERM_CONST when we don't
> actually support vector. (LoongArch has SIMD instructions but the
> support in GCC won't be added in a very recent future.)
>
If what I understand is correct, I think this might be a better solution.
/* { dg-do compile } */
+/* { dg-require-effective-target vect_perm } */
/* { dg-options "-O -fdump-tree-dse1" } */
next prev parent reply other threads:[~2022-10-13 8:15 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
2022-10-13 6:15 ` Levy
2022-10-13 6:44 ` Xi Ruoyao
2022-10-13 8:15 ` Lulu Cheng [this message]
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=b1f7a658-d330-9661-376a-3927434490d9@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=admin@levyhsu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=liwei.xu@intel.com \
--cc=wilson@tuliptree.org \
--cc=xry111@xry111.site \
/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).