public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Li, Pan2" <pan2.li@intel.com>
To: Richard Biener <rguenther@suse.de>, Juzhe-Zhong <juzhe.zhong@rivai.ai>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH V2] test: Fix bb-slp-33.c for RVV
Date: Wed, 8 Nov 2023 07:21:58 +0000	[thread overview]
Message-ID: <MW5PR11MB5908C97C4643C44637786764A9A8A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2311080657570.8772@jbgna.fhfr.qr>

Committed, thanks Richard.

Pan

-----Original Message-----
From: Richard Biener <rguenther@suse.de> 
Sent: Wednesday, November 8, 2023 2:58 PM
To: Juzhe-Zhong <juzhe.zhong@rivai.ai>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH V2] test: Fix bb-slp-33.c for RVV

On Tue, 7 Nov 2023, Juzhe-Zhong wrote:

> gcc/testsuite/ChangeLog:

OK.

> 	* gcc.dg/vect/bb-slp-33.c: Rewrite the condition.
> 
> ---
>  gcc/testsuite/gcc.dg/vect/bb-slp-33.c | 35 ++++++++++++++++++++-------
>  1 file changed, 26 insertions(+), 9 deletions(-)
> 
> diff --git a/gcc/testsuite/gcc.dg/vect/bb-slp-33.c b/gcc/testsuite/gcc.dg/vect/bb-slp-33.c
> index bbb13ef798e..74af8dd27ae 100644
> --- a/gcc/testsuite/gcc.dg/vect/bb-slp-33.c
> +++ b/gcc/testsuite/gcc.dg/vect/bb-slp-33.c
> @@ -32,16 +32,33 @@ int main()
>    a[4] = 7;
>    check_vect ();
>    test(a, b);
> -  if (a[0] != 1
> -      || a[1] != 2
> -      || a[2] != 3
> -      || a[3] != 4
> -      || a[4] != 7
> -      || a[5] != 0
> -      || a[6] != 0
> -      || a[7] != 0
> -      || a[8] != 0)
> +  if (a[0] != 1)
>      abort ();
> +  __asm__ volatile ("");
> +  if (a[1] != 2)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[2] != 3)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[3] != 4)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[4] != 7)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[5] != 0)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[6] != 0)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[7] != 0)
> +    abort ();
> +  __asm__ volatile ("");
> +  if (a[8] != 0)
> +    abort ();
> +  __asm__ volatile ("");
>    return 0;
>  }
>  
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)

      reply	other threads:[~2023-11-08  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 15:13 Juzhe-Zhong
2023-11-08  6:58 ` Richard Biener
2023-11-08  7:21   ` Li, Pan2 [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=MW5PR11MB5908C97C4643C44637786764A9A8A@MW5PR11MB5908.namprd11.prod.outlook.com \
    --to=pan2.li@intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=rguenther@suse.de \
    /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).