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-5108] rs6000/test: Make ppc-fortran.exp only available for PowerPC target
Date: Wed, 11 Jan 2023 13:00:34 +0000 (GMT)	[thread overview]
Message-ID: <20230111130034.D7A733858032@sourceware.org> (raw)

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

commit r13-5108-gde99049f6fe5341024d4d939ac50d063280f90db
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Jan 11 06:59:24 2023 -0600

    rs6000/test: Make ppc-fortran.exp only available for PowerPC target
    
    When testing one patch which adds a fortran test case into
    test bucket powerpc/ppc-fortran/, I found one unexpected
    failure on a non-PowerPC target.  It's due to that
    ppc-fortran.exp does not exit early if the testing target
    isn't a PowerPC target.  This patch is to make it exit
    immediately if the testing target isn't a PowerPC target.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/powerpc/ppc-fortran/ppc-fortran.exp: Exit immediately if
            the testing target isn't a PowerPC target.

Diff:
---
 gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp b/gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp
index bd7ad95ad0d..ded643b56bf 100644
--- a/gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp
+++ b/gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp
@@ -16,6 +16,11 @@
 
 # GCC testsuite that uses the `dg.exp' driver.
 
+# Exit immediately if this isn't a PowerPC target.
+if { ![istarget powerpc*-*-*] && ![istarget rs6000-*-*] } then {
+  return
+}
+
 # Load support procs.
 load_lib gfortran-dg.exp

                 reply	other threads:[~2023-01-11 13:00 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=20230111130034.D7A733858032@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).