From: chenglulu <chenglulu@loongson.cn>
To: chenxiaolong <chenxiaolong@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn
Subject: Re:[pushed] [PATCH v1] LoongArch: testsuite:Fix FAIL in lasx-xvstelm.c file.
Date: Thu, 4 Jan 2024 14:21:09 +0800 [thread overview]
Message-ID: <51c6131e-309c-daaa-8e34-9946f330d1b8@loongson.cn> (raw)
In-Reply-To: <20231229014515.40945-1-chenxiaolong@loongson.cn>
Pushed to r14-6909.
在 2023/12/29 上午9:45, chenxiaolong 写道:
> After implementing the cost model on the LoongArch architecture, the GCC
> compiler code has this feature turned on by default, which causes the
> lasx-xvstelm.c file test to fail. Through analysis, this test case can
> generate vectorization instructions required for detection only after
> disabling the functionality of the cost model with the "-fno-vect-cost-model"
> compilation option.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/loongarch/vector/lasx/lasx-xvstelm.c:Add compile
> option "-fno-vect-cost-model" to dg-options.
> ---
> gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-xvstelm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-xvstelm.c b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-xvstelm.c
> index 1a7b0e86f8b..4b846204a65 100644
> --- a/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-xvstelm.c
> +++ b/gcc/testsuite/gcc.target/loongarch/vector/lasx/lasx-xvstelm.c
> @@ -1,5 +1,5 @@
> /* { dg-do compile } */
> -/* { dg-options "-O3 -mlasx" } */
> +/* { dg-options "-O3 -mlasx -fno-vect-cost-model" } */
> /* { dg-final { scan-assembler-times "xvstelm.w" 8} } */
>
> #define LEN 256
prev parent reply other threads:[~2024-01-04 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 1:45 chenxiaolong
2024-01-04 6:21 ` chenglulu [this message]
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=51c6131e-309c-daaa-8e34-9946f330d1b8@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=chenxiaolong@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=xry111@xry111.site \
--cc=xuchenghua@loongson.cn \
/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).