public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove some dead code in gdb.fortran/info-types.exp
Date: Fri, 27 Jan 2023 01:29:05 +0000 (GMT)	[thread overview]
Message-ID: <20230127012905.8D2CE3858D20@sourceware.org> (raw)

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

commit e1a772ad89bc1103182168b46513900aa035a81e
Author: Tom Tromey <tom@tromey.com>
Date:   Wed Jan 25 09:37:25 2023 -0700

    Remove some dead code in gdb.fortran/info-types.exp
    
    An early "return" in this test case prevents a test from running.
    This seems to have been intentional and has been in place since:
    
    commit d57cbee932f86df06251498daa93154046dc77c0
    Author: Andrew Burgess <andrew.burgess@embecosm.com>
    Date:   Tue Dec 3 13:18:43 2019 +0000
    
        gdb/testsuite/fortran: Fix info-modules/info-types for gfortran 8+
    
    This patch removes the dead code.

Diff:
---
 gdb/testsuite/gdb.fortran/info-types.exp | 17 -----------------
 1 file changed, 17 deletions(-)

diff --git a/gdb/testsuite/gdb.fortran/info-types.exp b/gdb/testsuite/gdb.fortran/info-types.exp
index 98fb812dd8b..8cd9a2ae6cb 100644
--- a/gdb/testsuite/gdb.fortran/info-types.exp
+++ b/gdb/testsuite/gdb.fortran/info-types.exp
@@ -61,20 +61,3 @@ if { [test_compiler_info {gfortran-*} f90] } {
     setup_xfail *-*-* gcc/105454
     GDBInfoSymbols::check_entry "${srcfile}" "41" "Type s1;"
 }
-
-return 0
-
-gdb_test "info types" \
-    [multi_line \
-	 "All defined types:" \
-	 "" \
-	 "File .*:" \
-	 "\[\t \]+${character1}" \
-	 "\[\t \]+${integer4}" \
-	 "(\[\t \]+${integer8}" \
-	 ")?\[\t \]+${logical4}" \
-	 "(35:\[\t \]+Type __vtype_mod1_M1t1;" \
-	 ")?$decimal:\[\t \]+Type m1t1;" \
-	 "\[\t \]+${real4}" \
-	 "41:\[\t \]+Type s1;(" \
-	 ".*)?"]

                 reply	other threads:[~2023-01-27  1:29 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=20230127012905.8D2CE3858D20@sourceware.org \
    --to=tromey@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).