public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-6993] testsuite: Fix up gomp/simd-{2,3}.c tests [PR98243]
Date: Sat, 30 Jan 2021 09:54:47 +0000 (GMT)	[thread overview]
Message-ID: <20210130095447.07F843857C7B@sourceware.org> (raw)

https://gcc.gnu.org/g:25f303e9a27a0d799f9979446d9f11ed62b8d648

commit r11-6993-g25f303e9a27a0d799f9979446d9f11ed62b8d648
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Jan 30 10:52:57 2021 +0100

    testsuite: Fix up gomp/simd-{2,3}.c tests [PR98243]
    
    The test (intentionally) is not gcc.dg/vect/, as it needs -fopenmp and uses
    OpenMP directives other than simd and therefore can't rely on default
    VECTFLAGS and so I think can't safely use vect_int effective target
    either.  So, I'm just making sure it is vectorized on x86 and on aarch64 (the
    latter as an example of a target that doesn't need any extra options to get
    the vectorization).
    
    2021-01-30  Jakub Jelinek  <jakub@redhat.com>
    
            PR testsuite/98243
            * gcc.dg/gomp/simd-2.c: Add -msse2 on x86.  Restrict
            scan-tree-dump-times to x86 and aarch64 targets.
            * gcc.dg/gomp/simd-3.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.dg/gomp/simd-2.c | 3 ++-
 gcc/testsuite/gcc.dg/gomp/simd-3.c | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/gomp/simd-2.c b/gcc/testsuite/gcc.dg/gomp/simd-2.c
index 7ac3eb4444a..85acb980f10 100644
--- a/gcc/testsuite/gcc.dg/gomp/simd-2.c
+++ b/gcc/testsuite/gcc.dg/gomp/simd-2.c
@@ -1,7 +1,8 @@
 /* { dg-do compile } */
 /* { dg-options "-O2 -fopenmp -fdump-tree-vect-details" } */
+/* { dg-additional-options "-msse2" { target { i?86-*-* x86_64-*-* } } } */
 /* { dg-additional-options "-mavx" { target avx } } */
-/* { dg-final { scan-tree-dump-times "vectorized \[1-9]\[0-9]* loops in function" 5 "vect" } } */
+/* { dg-final { scan-tree-dump-times "vectorized \[1-9]\[0-9]* loops in function" 5 "vect" { target i?86-*-* x86_64-*-* aarch64-*-* } } } */
 
 int a[10000][128];
 
diff --git a/gcc/testsuite/gcc.dg/gomp/simd-3.c b/gcc/testsuite/gcc.dg/gomp/simd-3.c
index 13e1346da03..86fee858673 100644
--- a/gcc/testsuite/gcc.dg/gomp/simd-3.c
+++ b/gcc/testsuite/gcc.dg/gomp/simd-3.c
@@ -1,7 +1,8 @@
 /* { dg-do compile } */
 /* { dg-options "-O2 -fopenmp -fdump-tree-vect-details" } */
+/* { dg-additional-options "-msse2" { target { i?86-*-* x86_64-*-* } } } */
 /* { dg-additional-options "-mavx" { target avx } } */
-/* { dg-final { scan-tree-dump-times "vectorized \[1-9]\[0-9]* loops in function" 5 "vect" } } */
+/* { dg-final { scan-tree-dump-times "vectorized \[1-9]\[0-9]* loops in function" 5 "vect" { target i?86-*-* x86_64-*-* aarch64-*-* } } } */
 
 int a[1024][1024];


                 reply	other threads:[~2021-01-30  9:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210130095447.07F843857C7B@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).