From: Gary Benson <gbenson@redhat.com>
To: gdb-patches@sourceware.org
Subject: [OB PATCH] Add skip_fortran_tests to two Fortran testcases
Date: Tue, 27 Oct 2020 16:56:44 +0000 [thread overview]
Message-ID: <1603817804-20755-1-git-send-email-gbenson@redhat.com> (raw)
Hi all,
This commit adds missing skip_fortran_tests checks to two Fortran
testcases that did not have it. It also fixes a copy-paste error
in a comment.
Pushed as obvious.
Cheers,
Gary
---
gdb/testsuite/ChangeLog:
* gdb.mi/mi-fortran-modules.exp: Check skip_fortran_tests.
* gdb.mi/mi-vla-fortran.exp: Likewise. Also fix a comment.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.mi/mi-fortran-modules.exp | 2 ++
gdb/testsuite/gdb.mi/mi-vla-fortran.exp | 6 ++++--
3 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.mi/mi-fortran-modules.exp b/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
index de5657d..ae6cbd7 100644
--- a/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
+++ b/gdb/testsuite/gdb.mi/mi-fortran-modules.exp
@@ -15,6 +15,8 @@
# Test -symbol-info-modules, listing Fortran modules.
+if { [skip_fortran_tests] } { return -1 }
+
load_lib fortran.exp
load_lib mi-support.exp
set MIFLAGS "-i=mi"
diff --git a/gdb/testsuite/gdb.mi/mi-vla-fortran.exp b/gdb/testsuite/gdb.mi/mi-vla-fortran.exp
index e862725..a62ec0f 100644
--- a/gdb/testsuite/gdb.mi/mi-vla-fortran.exp
+++ b/gdb/testsuite/gdb.mi/mi-vla-fortran.exp
@@ -13,8 +13,10 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
-# Verify that, using the MI, we can evaluate a simple C Variable Length
-# Array (VLA).
+# Verify that, using the MI, we can evaluate a simple Fortran Variable
+# Length Array (VLA).
+
+if { [skip_fortran_tests] } { return -1 }
load_lib mi-support.exp
load_lib fortran.exp
--
1.8.3.1
reply other threads:[~2020-10-27 16:56 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=1603817804-20755-1-git-send-email-gbenson@redhat.com \
--to=gbenson@redhat.com \
--cc=gdb-patches@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).