public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
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,
	schwab@linux-m68k.org, ci_notify@linaro.org
Subject: Re: [pushed][PATCH v2] LoongArch: testsuite:Fix fail in gen-vect-{2,25}.c file.
Date: Thu, 18 Jan 2024 15:30:17 +0800	[thread overview]
Message-ID: <4414f77a-dcca-ba94-f379-2159e9660fea@loongson.cn> (raw)
In-Reply-To: <20240113072834.32021-1-chenxiaolong@loongson.cn>

Pushed to r14-8204.

在 2024/1/13 下午3:28, chenxiaolong 写道:
> 1.Added  dg-do compile on LoongArch.
>    When binutils does not support vector instruction sets, an error occurs
> because the assembler does not recognize vector instructions.
>
> 2.Added "-mlsx" option for vectorization on LoongArch.
>
> gcc/testsuite/ChangeLog:
>
> 	* gcc.dg/tree-ssa/gen-vect-2.c: Added detection of compilation
> 	behavior and "-mlsx" option on LoongArch.
> 	* gcc.dg/tree-ssa/gen-vect-25.c: Dito.
> ---
>   gcc/testsuite/gcc.dg/tree-ssa/gen-vect-2.c  | 2 ++
>   gcc/testsuite/gcc.dg/tree-ssa/gen-vect-25.c | 2 ++
>   2 files changed, 4 insertions(+)
>
> diff --git a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-2.c b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-2.c
> index b84f3184427..a35999a172a 100644
> --- a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-2.c
> +++ b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-2.c
> @@ -1,6 +1,8 @@
>   /* { dg-do run { target vect_cmdline_needed } } */
> +/* { dg-do compile { target { loongarch_sx && {! loongarch_sx_hw } } } } */
>   /* { dg-options "-O2 -fno-tree-loop-distribute-patterns -ftree-vectorize -fdump-tree-vect-details -fvect-cost-model=dynamic" } */
>   /* { dg-additional-options "-mno-sse" { target { i?86-*-* x86_64-*-* } } } */
> +/* { dg-additional-options "-mlsx" { target { loongarch*-*-* } } } */
>   
>   #include <stdlib.h>
>   
> diff --git a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-25.c b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-25.c
> index 18fe1aa1502..9f14a54c413 100644
> --- a/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-25.c
> +++ b/gcc/testsuite/gcc.dg/tree-ssa/gen-vect-25.c
> @@ -1,6 +1,8 @@
>   /* { dg-do run { target vect_cmdline_needed } } */
> +/* { dg-do compile { target { loongarch_sx && {! loongarch_sx_hw } } } } */
>   /* { dg-options "-O2 -ftree-vectorize -fdump-tree-vect-details -fvect-cost-model=dynamic" } */
>   /* { dg-options "-O2 -ftree-vectorize -fdump-tree-vect-details -fvect-cost-model=dynamic -mno-sse" { target { i?86-*-* x86_64-*-* } } } */
> +/* { dg-additional-options "-mlsx" { target { loongarch*-*-* } } } */
>   
>   #include <stdlib.h>
>   


      reply	other threads:[~2024-01-18  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13  7:28 [PATCH " chenxiaolong
2024-01-18  7:30 ` 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=4414f77a-dcca-ba94-f379-2159e9660fea@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=chenxiaolong@loongson.cn \
    --cc=ci_notify@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=schwab@linux-m68k.org \
    --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).