public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6542] testsuite: Adjust two bfp test cases with has_arch_ppc64 [PR108729]
Date: Wed,  8 Mar 2023 06:59:56 +0000 (GMT)	[thread overview]
Message-ID: <20230308065956.A67AE385086A@sourceware.org> (raw)

https://gcc.gnu.org/g:bab3b6a9c3bde32903815826f96abc18e62bff6e

commit r13-6542-gbab3b6a9c3bde32903815826f96abc18e62bff6e
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Mar 8 00:56:32 2023 -0600

    testsuite: Adjust two bfp test cases with has_arch_ppc64 [PR108729]
    
    Two test cases scalar-test-data-class-12.c and vec-test-data-class-9.c
    fail on Power9 BE testing at -m32, they adopts a built-in function
    scalar_insert_exp which requires powerpc64 support.  This patch
    is to make them to check has_arch_ppc64 effective target requirement.
    
            PR testsuite/108729
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/powerpc/bfp/scalar-test-data-class-12.c: Adjust with
            has_arch_ppc64 effective target.
            * gcc.target/powerpc/bfp/vec-test-data-class-9.c: Likewise.

Diff:
---
 gcc/testsuite/gcc.target/powerpc/bfp/scalar-test-data-class-12.c | 1 +
 gcc/testsuite/gcc.target/powerpc/bfp/vec-test-data-class-9.c     | 1 +
 2 files changed, 2 insertions(+)

diff --git a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-test-data-class-12.c b/gcc/testsuite/gcc.target/powerpc/bfp/scalar-test-data-class-12.c
index f7f41419810..08f2720e5b4 100644
--- a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-test-data-class-12.c
+++ b/gcc/testsuite/gcc.target/powerpc/bfp/scalar-test-data-class-12.c
@@ -1,4 +1,5 @@
 /* { dg-do run { target { powerpc*-*-* } } } */
+/* { dg-require-effective-target has_arch_ppc64 } */
 /* { dg-require-effective-target p9vector_hw } */
 /* { dg-options "-mdejagnu-cpu=power9" } */
 
diff --git a/gcc/testsuite/gcc.target/powerpc/bfp/vec-test-data-class-9.c b/gcc/testsuite/gcc.target/powerpc/bfp/vec-test-data-class-9.c
index aeb64fbf122..c803617b5d3 100644
--- a/gcc/testsuite/gcc.target/powerpc/bfp/vec-test-data-class-9.c
+++ b/gcc/testsuite/gcc.target/powerpc/bfp/vec-test-data-class-9.c
@@ -1,4 +1,5 @@
 /* { dg-do run { target { powerpc*-*-* } } } */
+/* { dg-require-effective-target has_arch_ppc64 } */
 /* { dg-require-effective-target p9vector_hw } */
 /* { dg-options "-mdejagnu-cpu=power9" } */

                 reply	other threads:[~2023-03-08  6:59 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=20230308065956.A67AE385086A@sourceware.org \
    --to=linkw@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).