public inbox for
help / color / mirror / Atom feed
From: Tom de Vries <>
Subject: [binutils-gdb] [gdb/testsuite] Remove duplicate of supports_gnuc
Date: Mon, 18 Jul 2022 10:48:42 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=9a14143c59f9aa7c68a032cd53f0106d5a31a040

commit 9a14143c59f9aa7c68a032cd53f0106d5a31a040
Author: Tom de Vries <>
Date:   Mon Jul 18 12:48:39 2022 +0200

    [gdb/testsuite] Remove duplicate of supports_gnuc
    In commit 9d9dd861e98 ("[gdb/testsuite] Fix regression in
    step-indirect-call-thunk.exp with gcc 7") I accidentally committed a duplicate
    of supports_gnuc, which caused:
    DUPLICATE: gdb.base/gdb-caching-proc.exp: supports_gnuc: consistency
    Fix this by removing the duplicate.
    Tested on x86_64-linux.

 gdb/testsuite/lib/gdb.exp | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index ef68c3ce9fb..a8f25b5f0dd 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -8529,17 +8529,6 @@ gdb_caching_proc supports_gnuc {
     return [gdb_simple_compile $me $src object ""]
-# Return 1 if compiler supports __GNUC__, otherwise return 0.
-gdb_caching_proc supports_gnuc {
-    set me "supports_gnuc"
-    set src {
-	#ifndef __GNUC__
-	#error "No gnuc"
-	#endif
-    }
-    return [gdb_simple_compile $me $src object ""]
 # Return 1 if target supports mpx, otherwise return 0.
 gdb_caching_proc have_mpx {
     global srcdir

                 reply	other threads:[~2022-07-18 10:48 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).