Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Skip gdb.{base, tui}/tailcall-msym.exp on cygwin
Date: Sat, 19 Sep 2026 20:09:53 +0200	[thread overview]
Message-ID: <20260919180953.1369329-1-tdevries@suse.de> (raw)

I ran test-case gdb.tui/tailcall-msym.exp on cygwin.

The test-case adds some stuff to the .s file, which doesn't compile on cygwin.

Fix this by skipping the test-case on cygwin.

Likewise for gdb.base/tailcall-msym.exp.
---
 gdb/testsuite/gdb.base/tailcall-msym.exp | 3 +++
 gdb/testsuite/gdb.tui/tailcall-msym.exp  | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/gdb/testsuite/gdb.base/tailcall-msym.exp b/gdb/testsuite/gdb.base/tailcall-msym.exp
index 9ffaa7f17c1..1f27c7f2816 100644
--- a/gdb/testsuite/gdb.base/tailcall-msym.exp
+++ b/gdb/testsuite/gdb.base/tailcall-msym.exp
@@ -23,6 +23,9 @@
 # and to create a fake function symbol that sits immediately after the
 # tail call function.
 
+# The dummy function doesn't compile on cygwin.
+require {!istarget *-*-cygwin*}
+
 standard_testfile
 
 # Compile with debug info first so we can find the instruction boundaries.
diff --git a/gdb/testsuite/gdb.tui/tailcall-msym.exp b/gdb/testsuite/gdb.tui/tailcall-msym.exp
index 1e13414f760..1497b93f0f3 100644
--- a/gdb/testsuite/gdb.tui/tailcall-msym.exp
+++ b/gdb/testsuite/gdb.tui/tailcall-msym.exp
@@ -22,6 +22,9 @@
 # Still, I wanted the test to live in gdb.tui/ as this really is testing
 # TUI specific code.
 
+# The dummy function doesn't compile on cygwin.
+require {!istarget *-*-cygwin*}
+
 tuiterm_env
 
 standard_testfile

base-commit: 12b6047b2d48888f284795c5d9807a2c7e3c0c67
-- 
2.51.0


                 reply	other threads:[~2026-09-19 18:10 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=20260919180953.1369329-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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