public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Nils-Christian Kempke <nckempke@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/testsuite: disable charset.exp for intel compilers
Date: Tue, 31 May 2022 14:45:43 +0000 (GMT)	[thread overview]
Message-ID: <20220531144543.CDCAC395A021@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=87364601b87da148b9c4b96aa164e329794c2959

commit 87364601b87da148b9c4b96aa164e329794c2959
Author: Nils-Christian Kempke <nils-christian.kempke@intel.com>
Date:   Tue May 31 16:43:44 2022 +0200

    gdb/testsuite: disable charset.exp for intel compilers
    
    The test specifically tests for the Fortran CHARACTER(KIND=4) which is
    not available in ifx/ifort.
    
    Since the other characters are also printed elsewhere, we disable this
    test for the unsupported compilers.

Diff:
---
 gdb/testsuite/gdb.fortran/charset.exp | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gdb/testsuite/gdb.fortran/charset.exp b/gdb/testsuite/gdb.fortran/charset.exp
index 5e4ba592cc1..ae3e34ce1c7 100644
--- a/gdb/testsuite/gdb.fortran/charset.exp
+++ b/gdb/testsuite/gdb.fortran/charset.exp
@@ -21,6 +21,11 @@ if { [skip_fortran_tests] } { return -1 }
 standard_testfile .f90
 load_lib fortran.exp
 
+# Ifx, and ifort do not support kind=4 for CHARACTER.
+if { [test_compiler_info {ifx-*} f90] || [test_compiler_info {ifort-*} f90] } {
+    return -1
+}
+
 if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} {debug additional_flags=-fbackslash f90}] } {
     return -1
 }


                 reply	other threads:[~2022-05-31 14:45 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=20220531144543.CDCAC395A021@sourceware.org \
    --to=nckempke@sourceware.org \
    --cc=gdb-cvs@sourceware.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).